Email Deliverability Checker

DNS Lookup shows the raw SPF and DMARC TXT records it finds, alongside every other DNS record type. This tool goes further specifically for email: it also guesses common DKIM selectors (DNS Lookup doesn't check DKIM at all, since there's no fixed record name for it), parses the SPF/DMARC policies to explain what they actually mean, and produces a single deliverability score.

DKIM selectors are chosen by whoever configured mail for the domain, and there's no universal name for them — this check tries the handful of selector names seen most often across major providers (Google Workspace, Microsoft 365, common email services), but a domain using a custom or unusual selector name won't be found this way. A false negative here doesn't necessarily mean DKIM isn't configured.

SPF lists which mail servers are allowed to send email for a domain. DKIM cryptographically signs outgoing mail so receivers can verify it wasn't altered in transit. DMARC ties the two together — it tells receiving servers what to do (nothing, quarantine, or reject) when a message fails SPF or DKIM, and where to send reports about it. All three work together; having only one or two leaves real gaps.

p=none is a monitoring-only mode — it collects reports but doesn't tell receiving servers to do anything about mail that fails authentication. It's a reasonable first step while confirming legitimate mail passes correctly, but the protection DMARC is meant to provide only kicks in once the policy moves to p=quarantine or p=reject.

Not directly — these records govern email authentication, not web indexing. The practical impact is deliverability and anti-spoofing: without them, legitimate email from the domain is more likely to land in spam, and attackers can more easily send convincing phishing email that appears to come from it.