Skip to content

DMARC & SPF Checker

Short answer

Check a domain's MX, SPF, DMARC and DKIM records: SPF includes and the 10-lookup limit, DMARC against RFC 9989, DKIM keys. Builds SPF and DMARC too.

What it does not do: It reads public DNS records only: it cannot list every DKIM selector, sends no test email and does not change your DNS.

Free · No signup · Runs in your browser

It is the s= value in the DKIM-Signature header of an email this domain sent. Separate several with commas. Leave it empty to try 24 common selectors.

Large mailbox providers require bulk senders to publish SPF, DKIM and a DMARC record (p=none at least), with the From domain aligned with SPF or DKIM.

DNS records are read from your browser through a public DNS-over-HTTPS resolver. Nothing is sent to RankProof.

What It Does

Looks up a domain's email authentication records and checks them: the MX records (including a null MX), the SPF record with every include followed and the 10-lookup limit counted, the DMARC record against the current standard (RFC 9989), and DKIM keys at the selector you enter or at a set of common selectors. Two more tabs build SPF and DMARC records from a short form.

Why It Matters

SPF, DKIM and DMARC let receiving servers check that email using your domain really comes from you. Large mailbox providers require them from bulk senders, and without an enforced DMARC policy anyone can send email that appears to come from your domain. Small mistakes break them without any warning: a second SPF record, more than 10 DNS lookups or a typo in the DMARC record mean the check fails or the record is ignored.

How It Works

  1. Enter a domain, and a DKIM selector if you know it

  2. Your browser reads the MX, SPF, DMARC and DKIM records through a public DNS-over-HTTPS resolver

  3. Each record is checked: SPF lookups and the all mechanism, the DMARC policy, report addresses and tags, the DKIM key size

  4. Read the result for each record, or build a new SPF or DMARC record in the other tabs

Sample input + output

INPUT
domain: example.com · DKIM selector: (empty, 24 common selectors tried)
OUTPUT
Score: 96/100 — 2 of 3 areas look good

Mail servers (MX) — 100: Null MX: this domain accepts no email
SPF — 100: SPF record found
  v=spf1 -all · DNS lookups 0 / 10 · empty lookups 0 / 2 · other senders: Fail (-all)
DMARC — 88: Policy: reject
  v=DMARC1;p=reject;sp=reject;adkim=s;aspf=s · found at _dmarc.example.com
  Report addresses: 0 · Alignment (DKIM / SPF): strict / strict
  Needs attention: No rua= address, so you will not receive aggregate reports

How to read the result

Score (96) and "2 of 3 areas look good"
The average of the areas below. An area is in good shape only when nothing in it needs attention; in the sample DMARC scores 88 because one item does, so 2 of the 3 areas count as good.
Mail servers (MX): Null MX
example.com publishes a "null MX" (priority 0, host "."), the standard way to say that a domain accepts no email at all. A domain that receives mail shows its mail servers here instead.
SPF (v=spf1 -all, 0 / 10 lookups)
SPF lists the servers allowed to send mail for the domain. Each include, a, mx or redirect costs a DNS lookup, and more than 10 make the record invalid; empty lookups are capped at 2. The ending decides what happens to everyone else: -all says fail. With no server listed, the sample says that nobody sends mail as this domain.
DMARC (policy reject, 0 report addresses)
DMARC tells receivers what to do with mail that fails SPF and DKIM alignment: none, quarantine or reject. Alignment strict / strict means the From domain must match exactly. It needs attention here only because there is no rua= address, so nobody receives reports about mail sent in the domain's name.
Why there is no DKIM area
DNS cannot list DKIM keys, so we look at the selector you enter, or at 24 common ones when the field is empty. For a domain with a null MX and no key we leave the area out. For a domain that sends mail, copy the s= value from the DKIM-Signature header of one of its emails into the selector field.

Who Uses This

  • IT administrator

    Confirm that SPF stays under the 10-lookup limit after adding a new email service.

  • Marketing manager

    Check that the newsletter domain has SPF, DKIM and DMARC before a large send.

  • Agency consultant

    Show a client that their DMARC policy is still p=none and build the record for the next step.

Common problems and how to fix them

  1. No SPF record, or more than one

    Publish exactly one SPF record that lists every service that sends mail for you, such as your mailbox provider and newsletter tool. Start with ~all while you check the reports, then move to -all.

    example.com.  TXT  "v=spf1 mx include:_spf.mail-provider.example ~all"
  2. More than 10 DNS lookups

    An SPF record with more than 10 lookups fails for every message. Remove includes for services you no longer use, and replace a nested include with the ip4: or ip6: ranges it stands for when the provider publishes them.

  3. DMARC stuck at p=none

    p=none only collects reports. Read them, fix every legitimate source that fails, then move to p=quarantine and finally p=reject, so that forged mail in your name is no longer delivered.

    _dmarc.example.com.  TXT  "v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@example.com"
  4. No rua= address

    Add rua=mailto: with a mailbox you read. Receivers then send daily aggregate reports that show who sends mail in your domain's name and whether it passes.

    _dmarc.example.com.  TXT  "v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@example.com"
  5. A domain that sends no email

    Lock it the way the sample domain is locked: a null MX, an SPF record of v=spf1 -all and a DMARC policy of reject. Parked and redirect-only domains are favourite targets for spoofing.

    example.com.         MX   0 .
    example.com.         TXT  "v=spf1 -all"
    _dmarc.example.com.  TXT  "v=DMARC1; p=reject"

Frequently Asked Questions

What is DMARC?
A DNS record that tells receiving servers what to do with email that shows your domain in the From address but fails SPF and DKIM alignment (deliver it, quarantine it or reject it), and where to send reports about that email.
Why is my SPF record over the 10-lookup limit?
Every include, a, mx, ptr and exists mechanism, and the redirect modifier, costs one DNS lookup, and included records can contain more includes. Above 10 the SPF check fails with a permanent error. Remove services you no longer use, or replace an include with the IP ranges the service publishes.
Why can't it find my DKIM key?
DNS offers no way to list DKIM selectors. Without a selector the tool tries a set of common ones. Enter the s= value from the DKIM-Signature header of an email you sent to check the right key.
Is pct= still valid?
DMARC was updated in May 2026 as RFC 9989. The pct, rf and ri tags are no longer part of it, and the new t=y tag marks a policy as a test. Receivers that follow the new standard ignore pct.
Does it send email or change my DNS?
No. It only reads public DNS records. To use a record you built, add it as a TXT record at your DNS provider.
Where do the DNS answers come from?
Your browser asks a public DNS-over-HTTPS resolver directly. The domain is not sent to RankProof, and nothing is stored.