emailsecuritygrade.com

DMARC, DKIM & SPF Checker: How to Verify Your Email Authentication Records

November 19, 2026

If you're responsible for your company's email deliverability, checking your authentication records is step one. A DMARC, DKIM, and SPF checker reads your domain's DNS records and tells you whether they're set up correctly before you start sending.

The key facts are straightforward: you can check all three records from one tool in under 30 seconds, and fixing what you find can be the difference between 98% inbox placement and your email landing in spam.

Key facts

  • A DMARC, DKIM, and SPF checker reads your published DNS records and reports whether they exist, what values they contain, and whether they'll pass authentication — all in one scan.
  • Combined checkers are more useful than single-record lookups because DMARC depends on SPF or DKIM passing with alignment. Checking DMARC alone can miss a broken DKIM record that's quietly failing.
  • Free checkers read DNS records live — they don't require signup, agent installs, or ongoing commitment.
  • A one-time DNS scan cannot tell you whether your emails are passing DMARC in practice. For that you need DMARC aggregate (RUA) reports, which show actual pass/fail data per source IP.
  • The most common fix identified by a checker is an SPF record that's missing a third-party sending service, a DKIM key that's published but doesn't match the signing domain, or a DMARC record stuck on p=none that was never moved to enforcement.

What a combined checker actually shows you

A single scan of your domain through a free SPF, DKIM, and DMARC checker returns three results, and the relationship between them matters more than any single pass/fail:

SPF — The checker reads your SPF TXT record and reports whether it exists, how many DNS lookups it contains (you need 10 or fewer for the record to not be permanently rejected), and whether the -all or ~all enforcement qualifier is set. SPF without -all is an informational record that mailbox providers treat as less strict.

DKIM — DKIM is different from SPF and DMARC because your record lives at a selector subdomain, not at the root of your domain. The checker queries the selector you provide (usually google._domainkey for Google Workspace, default._domainkey for many ESPs, or s1._domainkey for others) and reports whether the public key is published, valid, and correctly formatted. It cannot verify that the private key on your sending server matches the public key in DNS — that requires a send test.

DMARC — The checker reads your _dmarc.yourdomain.com TXT record and reports the policy (p=none, p=quarantine, or p=reject), the alignment mode (aspf and adkim, each r for relaxed or s for strict), the reporting addresses (rua and ruf), and any subdomain policy (sp). A checker that also knows SPF and DKIM can tell you whether your DMARC policy is consistent with the other two records — a common issue is setting p=reject without having DKIM alignment in place, which blocks every forwarded email.

How to run a check

Go to any free SPF, DKIM & DMARC checker — the one at emailsecuritygrade.com checks all three together. Type your domain name (not a full email address, just yourcompany.com), and the tool returns your grade (A through F), a list of what's passing and failing, and a plain-language explanation of any problem it finds.

The scan takes about 5 seconds. It reads your live DNS records and reports what's there. There is no signup, no email verification, and no installation.

What to do with the results

The three outcomes map to three fixes:

Your SPF record is missing a sending service. Your SPF record lists specific IP addresses or include: mechanisms that authorize your email provider to send on your behalf. If you use a transactional email service (SendGrid, Mailgun, Amazon SES) or a marketing platform (HubSpot, Mailchimp, Constant Contact) and their IP isn't covered, SPF will fail for those emails. Fix: add an include: mechanism for each third-party sender, keeping the total under 10 lookups. Use a free SPF checker to validate syntax.

Your DKIM record exists but alignment fails. This is the most subtle problem a combined checker can spot. Your DKIM public key is published, and your sending server signs emails with it — so DKIM authentication passes. But the d= domain in the DKIM signature doesn't match your From: domain. This happens when your email service provider generates the DKIM key but sets the signing domain to their own domain. Fix: generate a custom DKIM key in your ESP's settings that uses your own domain as the signing domain, then publish the matching public key in your DNS.

Your DMARC record is set to p=none with no plan to move to enforcement. A p=none policy is for monitoring only — it tells receiving servers to deliver mail regardless of whether it passes authentication. If you've been running in monitoring for more than two weeks and your aggregate reports show no major authentication issues, you should increase the policy to p=quarantine for at least a portion of your traffic. The checker will confirm the policy level is set correctly.

When you need more than a one-time check

A free DMARC, DKIM, and SPF checker is a snapshot. It tells you whether your DNS records are correctly published right now. It does not tell you:

  • Whether every email you sent in the last 24 hours passed DMARC (that requires RUA aggregate reports)
  • Whether a third party is spoofing your domain (only RUA reports or forensic RUF reports reveal unauthorized senders)
  • Whether your spam complaint rate is under the 0.1% threshold that Gmail uses in its Postmaster Tools

For ongoing monitoring, set up DMARC aggregate reports with an rua email address in your DMARC record. Services that parse those reports can show you exactly which source IPs are passing and failing, at what volume, and what percentage of your total email is authenticated. That data — not a one-time scan — is what tells you whether your deliverability is actually improving.

Check your grade free

Don't guess what's broken — see it. Scan your domain free at emailsecuritygrade.com and get an instant A-F grade on your SPF, DKIM, DMARC, and MX records, with a plain-language fix for anything failing. No signup, no install — it runs in your browser.

If your emails are still landing in spam after fixing the records, a deliverability tool like InboxAlly can train mailbox providers to trust your sending — worth a look once your grade is solid.

Fixed your records? Now fix deliverability.

Correcting SPF, DKIM, and DMARC is step one — but inbox providers don't trust a domain overnight. InboxAlly trains Gmail, Outlook, and Yahoo to trust your sending domain by generating real engagement signals, so your emails stop landing in spam within weeks instead of months. Most users see open rates double in 2–4 weeks.

Start free with InboxAlly →