Map Extract
Free tool

Email deliverability checker

Enter the domain you send from, or any address on it. Your browser asks public DNS for the five records that decide whether receivers can trust your mail, and you get a card for each one with a Pass, Warning, Problem or Not checked badge and the reason in plain words.

Runs in your browser. Domain names are looked up through public DNS over HTTPS (Cloudflare, with Google as a fallback); nothing goes to Map Extract.

Checking a sending domain

  1. Type the domain or an email address

    Use the part after the @ in your From address. Pasting the full address or a web address works too; the domain is taken from it.

  2. Add your DKIM selector if you know it

    It is the s= value in the DKIM-Signature header of an email you sent. Several can be separated by commas. With the box ticked, 28 common selectors are tried as well.

  3. Choose a resolver and run it

    Cloudflare (1.1.1.1) is the default; Google Public DNS (8.8.8.8) is the alternative if a lookup fails or you want a second opinion.

  4. Read the summary line

    One sentence totals the cards that need fixing, the ones with only a caution and any that came back unknown, and says how many questions went to the resolver.

  5. Open each card

    Every finding has its own badge. The raw record is under each card, with a copy button, so you can paste it into a generator or send it to whoever manages your DNS.

What each card checks

CardLooks upMain things it flags
MXMX records on the domainNo MX (replies and bounces have nowhere to go), a null MX, an MX that points at an IP address
SPFTXT on the domain, then every includeMissing record, two records, +all or ?all, ptr, unknown terms, more than 10 lookups, more than two void lookups
DKIMTXT at selector._domainkey for each selectorNo key found for the selectors tried, revoked keys, RSA keys under 1024 or under 2048 bits, testing mode
DMARCTXT at _dmarcMissing record, two records, invalid p=, p=none, pct below 100, no rua= report address
BIMITXT at default._bimiMissing logo URL, logo not an HTTPS SVG, no certificate, DMARC not strong enough for the logo to show

Example: a pottery studio on Microsoft 365

Kilnworks (fictional) sends from Microsoft 365 and a newsletter service. The owner set up SPF and DKIM when the mailboxes were created and added a DMARC record later, but never moved it past monitoring.

The checker ran 10 queries. MX and SPF pass, DKIM is published but on an older 1024-bit key, DMARC is monitoring only and BIMI is not set up, which is fine.

Input
Domain: kilnworks.example
Selectors: selector1, selector2, google
Also try common selectors: off
Result
kilnworks.example: 0 problems, 2 warnings, 0 not checked. 10 DNS queries.
MX     Pass     10 kilnworks-example.mail.protection.outlook.com
SPF    Pass     ~all, 3 of the 10 allowed DNS lookups used
DKIM   Warning  selector1: 1024-bit RSA key. 2048 bits is the current recommendation.
DMARC  Warning  p=none only monitors: failing mail is still delivered.
BIMI   Info     Not set up

When a check says Not checked

Not checked means the tool could not reach a conclusion, not that something is wrong. The usual case is DKIM: a selector can have any name, so if none of the ones tried has a key, the result is unknown rather than a failure. Look in the headers of an email you sent for DKIM-Signature, copy the s= value and run the check again with it.

A lookup can also fail if the resolver times out or a browser extension blocks DNS over HTTPS. Switch the resolver and run it once more before treating anything as a real gap.

Questions people ask

What does an email deliverability checker test?

This one tests the DNS records receivers use to decide whether mail claiming to be from your domain is genuine: MX for receiving, SPF for which servers may send, DKIM for signing keys, DMARC for what to do with failures, and BIMI for an optional logo. It does not send a test email, read your content or check blocklists.

Why does Gmail send my emails to spam when all checks pass?

Passing authentication is necessary but not sufficient. Gmail also weighs the reputation of your domain and IP, how many recipients mark you as spam, how many of your addresses bounce, how quickly volume rose and how people engage. A new domain needs a gradual ramp, a verified list and messages people actually want before placement improves.

Do I need DMARC for cold email?

If you send in bulk to Gmail or Yahoo users, their published rules require a DMARC record, and p=none is accepted as a minimum. For smaller senders it is still strongly advisable: it costs nothing, gives you reports on who sends as your domain and is expected by most receivers. Start at p=none with a report address and tighten later.

Is it better to use a separate domain for outreach?

Many B2B senders do, so that a reputation problem from cold email does not affect invoices and everyday replies from the main domain. The outreach domain needs its own MX, SPF, DKIM and DMARC, and should be checked here exactly like the main one. It also needs time and a slow start before it carries real volume.

Where your data goes

Your browser sends the DNS questions directly to the resolver you choose (Cloudflare's or Google's public DNS over HTTPS service). The queries contain only the domain and record names. Map Extract receives nothing and no email is sent.

Checked against the tool on

Top