DMARC, SPF and DKIM Checker

New

Check and generate the records that protect your email

  • 100% Free
  • Files stay private
  • Works in your browser
Try it now·DMARC, SPF and DKIM Checker

Check a domain

We read DMARC, SPF and DKIM live from public DNS and explain anything that is missing or weak.

Requiredthe domain you send mail from
Optionalwe try common ones

Records are read live from public DNS, so a change you just published can take time to appear while resolvers refresh their cache. DKIM is only found when the selector is known, so enter yours if the common ones miss it. You can see your selector in the s= tag of the DKIM-Signature header on any message you send.

How it works

  1. Enter your domain

    Type the domain you send mail from, add your DKIM selector if you know it, then press Check records.

  2. Read the results

    We look up your DMARC, SPF and DKIM records from public DNS and mark each one Valid, Needs work or Missing, with notes on any problems.

  3. Generate your records

    Press Generate the fixes, pick a DMARC Policy, list who may send your mail, then Copy the DMARC and SPF records to publish at your DNS provider.

The DMARC, SPF and DKIM Checker is a free online tool that reads the three email authentication records for any domain live from public DNS and tells you whether each one is present, valid, and safely configured. It is built for anyone who sends email from a domain, from marketers to security teams, and it turns cryptic TXT records into plain findings. You enter a domain, optionally add a DKIM selector, and get three graded cards plus a passed-out-of-three score.

At a Glance

DetailSummary
What it doesLooks up and grades a domain's DMARC, SPF, and DKIM DNS records, then flags issues.
InputA domain name (required) and an optional DKIM selector.
OutputThree cards with found and valid badges, the raw record, parsed fields, and advice, plus a summary score.
Runs whereOur server performs the live DNS lookups; the Generate mode builds records in your browser.
PrivacyOnly public DNS records are read. No mailbox access, no sending, no login.
PriceAlways free, no sign-up.
Best forAuditing deliverability and spoofing protection before or after a DNS change.

What Is DMARC, SPF and DKIM Checker?

DMARC, SPF and DKIM Checker is a tool that queries public DNS for the three records that prove your mail is genuine and reports what it finds. SPF (Sender Policy Framework, defined in RFC 7208) is a TXT record starting with v=spf1 that lists which servers may send for your domain. DKIM (DomainKeys Identified Mail, RFC 6376) publishes a public key at selector._domainkey.yourdomain so receivers can verify a cryptographic signature. DMARC (RFC 7489) sits on top at _dmarc.yourdomain and tells receivers what to do when SPF or DKIM fails.

When you submit a domain, our server resolves each record, parses the fields, and checks them against real rules. For SPF it counts DNS lookups against the hard limit of 10 that receivers enforce. For DMARC it reads the policy (none, quarantine, or reject), the reporting addresses (rua and ruf), the subdomain policy (sp), and the percentage (pct). For DKIM it inspects the selector you name or the common ones it knows.

How DMARC, SPF and DKIM Checker Is Different

Most quick checkers just print the raw record and leave you to interpret it. This tool grades each record with a three-color badge, green for valid, amber for found but flawed, and red for missing, and it explains the specific problem in words. It checks all three protocols in one pass and gives a single passed-out-of-three score, so you see the whole authentication picture instead of one record at a time.

AspectThis ToolA Typical Checker
Records coveredDMARC, SPF, and DKIM togetherOften one record per lookup
SPF lookup countCounted against the 10-lookup limitRarely calculated
VerdictGraded badge plus written issuesRaw record only
Record buildingGenerate mode drafts valid recordsCheck only

Who Benefits from This Tool

  • IT and email admins: confirm a new DMARC or SPF change resolved correctly before trusting it in production.
  • Deliverability specialists: catch a missing DKIM signature or a soft SPF fail that sends mail to spam.
  • Security teams: verify a domain is protected against spoofing with a DMARC policy of quarantine or reject.
  • Marketers: check that a new sending platform is authorized in SPF before a campaign goes out.
  • Managed service providers: audit a client domain in seconds instead of running three separate dig commands.
  • Developers: validate transactional email setup for a signup flow or notification service.

Key Features

  • Three records, one check: DMARC, SPF, and DKIM are looked up and graded in a single request.
  • Live DNS reads: records come straight from public DNS, so you see what receivers see right now.
  • SPF lookup counter: the tool tallies included lookups so you know if you are near the 10-lookup ceiling.
  • Plain-language issues: each card lists concrete problems, such as a permissive ~all or a policy stuck at p=none.
  • Optional DKIM selector: supply your provider's selector to check the exact key in use.
  • Generate mode: build a valid DMARC or SPF record in your browser and copy it straight into your DNS panel.

How to Use

  1. Choose the Check tab.
  2. Enter the domain you want to inspect, for example github.com.
  3. Optionally add your DKIM selector if you know it, such as google or s1.
  4. Submit and read the three cards along with the passed-out-of-three summary.
  5. Open the issues list on any amber or red card to see exactly what to fix.
  6. Switch to Generate to draft a corrected record, then copy the host and TXT value into your DNS.

Worked Example

Input: domain example-store.com with DKIM selector google.

Output:

  • DMARC (green, valid): record v=DMARC1; p=quarantine; rua=mailto:dmarc@example-store.com; pct=100; sp=quarantine. Policy quarantine, reports going to a valid mailbox.
  • SPF (amber, found with issues): record v=spf1 include:_spf.google.com include:mailgun.org ~all. Lookups used 4 of 10. Issue noted: ~all is a soft fail, so consider -all once every sender is listed.
  • DKIM (green, valid): selector google, record v=DKIM1; k=rsa; p=MIGfMA0....
  • Summary: 3 of 3 records found, with one advisory on SPF strictness.

Common Use Cases

  • Auditing a domain before moving to a stricter DMARC policy of reject.
  • Confirming a newly added sender, like a CRM or newsletter platform, is inside SPF.
  • Diagnosing why a domain's mail keeps landing in spam.
  • Verifying DKIM after rotating keys with your email provider.
  • Spot-checking a domain you are about to acquire or onboard.

Tips and Best Practices

  • Keep SPF under the 10-lookup limit; nested includes count and can silently break authentication.
  • Start DMARC at p=none with an rua address, read the reports, then move to quarantine and reject.
  • Prefer -all over ~all in SPF once you are confident every legitimate sender is listed.
  • Provide the correct DKIM selector; without it, a valid key can look missing.
  • Set a subdomain policy (sp) so attackers cannot spoof unused subdomains.
  • Re-check after any DNS edit, since changes can take time to propagate.

Limitations and Notes

This tool reads only public DNS records and cannot see inside your mail server, mailbox, or sending logs. DNS changes propagate on their own schedule, so a record you just edited may still show the old value for minutes to hours. DKIM checking depends on knowing the selector; if you leave it blank, the tool tries common selectors but may not find a custom one your provider uses. A valid record here means it parses and follows the rules, not that your overall deliverability is perfect, since reputation and content also matter. The Generate mode drafts records in your browser but does not publish them; you still add them to DNS yourself.

FAQs

SPF, DKIM, and DMARC are three layers of email authentication that work together. SPF lists which servers may send for your domain, DKIM adds a cryptographic signature that receivers verify with a published public key, and DMARC tells receivers what to do when SPF or DKIM fails and where to send reports. A domain is best protected when all three are present and aligned.

DKIM usually shows as missing because the selector was not provided or does not match your provider's key. DKIM keys live at selector._domainkey.yourdomain, and the selector is a label your email provider assigns, such as google, s1, or k1. Enter that exact selector in the optional field and re-run the check to see the key.

The SPF 10-lookup limit is a hard rule in RFC 7208 that caps how many DNS lookups an SPF record may trigger during evaluation. Each include, a, mx, and redirect mechanism can cost a lookup, and nested includes add up fast. If you exceed 10, receivers return a permerror and may fail your mail, which is why the tool counts them for you.

Your DMARC policy should end at reject once you have verified that all legitimate mail passes authentication. Start at p=none to monitor with aggregate reports, move to p=quarantine to send failing mail to spam, then set p=reject to block spoofed mail outright. Rushing to reject before checking reports can drop real email.

No, the DMARC, SPF and DKIM Checker reads only public DNS TXT records and never touches your mailbox, credentials, or message content. The lookup is the same query any mail receiver performs, and it requires no login. There is nothing private involved, only records you have deliberately published to DNS.

Results change after a DNS edit because DNS propagation is not instant. Resolvers and caches hold old records until their time-to-live expires, so a new SPF or DMARC value may take minutes to hours to appear everywhere. If a fresh change is not showing, wait a while and re-run the check.