Email Authentication Checker
SPF, DMARC, DKIM and MX records that decide whether your mail lands in inboxes.
What is an SPF checker?
An SPF checker reads a domain's email authentication records to verify they are published and valid. SPF (Sender Policy Framework) lists which servers may send mail for your domain; DMARC and DKIM complete the trio that decides whether your mail lands in inboxes or spam folders. A DMARC checker confirms the policy that tells receivers what to do with failures, and a DKIM checker verifies the selectors that sign outgoing mail. Missing or broken records are the most common reason legitimate email gets rejected.
How Email Authentication Checker works
Enter a domain and click Check records. Our server queries DNS for the domain's SPF record (the TXT record starting with v=spf1), its DMARC policy (the TXT record at _dmarc), DKIM public keys at common selectors (such as selector1 and google), and its MX records showing where mail is delivered. Each record is displayed with its raw value so you can spot typos, multiple SPF records, or an overly strict DMARC policy.
The check is read-only and takes seconds, yet it answers the question behind most "my emails go to spam" complaints. Because the records are fetched live from DNS, you can fix a typo at your provider, re-run the checker, and confirm the correction propagated — all in one sitting.
Key features
- SPF record lookup with the full published policy text.
- DMARC record check at
_dmarc, including the enforcement policy (p=). - DKIM public key lookup across common selectors used by major providers.
- MX records showing the domain's mail servers.
- Server-side DNS queries with raw record values for precise diagnosis.
Common uses
- Spam folder diagnosis: missing SPF or DMARC is the first thing to check when mail lands in spam.
- New domain setup: confirm all three records publish correctly before sending real mail.
- Provider migration: after switching mail hosts, verify the new SPF include and DKIM selectors are live.
- Spoofing defense: a strict DMARC policy stops attackers sending mail as your domain.
- Client audits: quickly score a domain's email authentication posture before a campaign.
Is it safe to use?
Yes. SPF, DMARC, DKIM and MX records are public DNS data — they must be public for receiving servers to verify your mail. The domain you enter is sent to our server to run the DNS queries and is never stored. The tool only reads records; it cannot alter your domain's email configuration.
Tips
- A domain must have exactly one SPF record — two TXT records starting with
v=spf1will break validation. - Start DMARC at
p=noneto collect reports, then tighten toquarantineandreject. - DKIM selectors differ per provider; add custom selectors in your DNS if the common ones miss.
- Every third-party sender (newsletters, CRM) must be included in SPF or aligned under DMARC.
- After any DNS change, re-check here before sending a campaign — propagation delays catch people out.
Frequently asked questions
What does an SPF checker do?
It fetches your domain's SPF record from DNS and shows the published policy, so you can confirm it exists, contains the right mail servers, and has no syntax errors that would cause receiving servers to reject your mail.
How do DMARC and DKIM relate to SPF?
SPF authorizes sending servers, DKIM cryptographically signs each message, and DMARC ties them together with a policy telling receivers to accept, quarantine or reject mail that fails the checks.
Why is my legitimate email going to spam?
The most common causes are missing or invalid SPF, no DMARC record, a DKIM signature that doesn't verify, or sending from a server not listed in SPF. This checker helps you rule each one out.
Can I have more than one SPF record?
No. DNS allows only one SPF record per domain; multiple v=spf1 records cause a permanent error and mail failures. Merge all includes into a single record.
What is a safe DMARC policy to start with?
Start with p=none and a reporting address. This collects failure reports without affecting delivery, letting you fix issues before enforcing quarantine or reject.
Does this tool change my DNS records?
No. It only reads public DNS data. To add or fix records, edit them at your DNS provider and re-run the checker to confirm the change propagated.
Inspect all record types with our DNS Lookup, and check who registered the domain with our WHOIS Lookup.