What this checker looks at
Enter a domain and it reads four kinds of DNS records:
- SPF, the TXT record on your domain that lists which servers may send email for you. The checker follows every
include:and counts the DNS lookups, because SPF breaks above 10. - DKIM, the public keys at
selector._domainkey.yourdomain. If you do not enter a selector, it tries the common ones used by Google Workspace, Microsoft 365, Zoho, Brevo, Mailchimp and others. - DMARC, the policy at
_dmarc.yourdomainthat tells receivers what to do with mail that fails. - MX, the servers that receive email for the domain.
Each check gets a pass, a warning or a problem, with a short explanation of what to change.
The problems we see most often
Two SPF records. Only one TXT record starting with v=spf1 is allowed. A second one, often added when a new email service is set up, breaks both. Merge them into one record with all the include: parts.
An include that points nowhere. After moving DNS or changing provider, an include: can point to a name that no longer exists. Receivers then treat the whole SPF record as an error. The checker names the broken include.
More than 10 lookups. Every include:, a, mx and exists costs a DNS lookup, and nested includes count too. Stack up five or six services and you can cross the limit without noticing. Remove services you no longer use.
DKIM records proxied on Cloudflare. If your DKIM records are CNAMEs and the orange cloud is on, the key behind them disappears. Switch every _domainkey record to DNS only.
DMARC stuck at p=none. It is the right place to start, but it protects nothing. Once the reports show only your own services, move to p=quarantine, then p=reject.
No DMARC reports. Without a rua= address you never see who is sending mail as your domain. Add one you actually read, or a free DMARC report service.
How to find your DKIM selector
Open an email sent from your domain in Gmail, click the three dots and choose Show original. In the DKIM-Signature header, look for s=. The value after it is your selector, for example s=google or s=selector1. Enter it in the selector box above to check that exact key.
Reading the result
- 3 of 3 checks pass: receivers can confirm your email is genuine. If messages still land in spam, the content or your sending reputation is the cause, not your DNS.
- SPF or DKIM fails: fix these first. Gmail and Yahoo require at least one of them from every sender, and both from anyone sending in bulk.
- DMARC warns: your mail is delivered, but scammers can still send in your name.
DNS changes can take a few minutes to an hour to be seen everywhere. If you just fixed a record, wait a little and check again. Results here are cached for two minutes.
For the full background on how the three records work together, read our guide to SPF, DKIM and DMARC.
Frequently asked questions
How do I check if my SPF record is correct?
Why does the checker not find my DKIM record?
What DMARC policy should I use?
Is it safe to enter my domain here?
How long do DNS changes take to show up?
Sources
The rules and figures in this tool come from these official sources, last checked November 12, 2026.
- RFC 7208: Sender Policy Framework (SPF) rfc-editor.org
- RFC 6376: DomainKeys Identified Mail (DKIM) rfc-editor.org
- RFC 7489: DMARC rfc-editor.org
- Google: email sender guidelines support.google.com
- Yahoo: sender best practices senders.yahooinc.com