Email Deliverability
Will your email reach the inbox?
Free SPF, DKIM and DMARC checker
Test the DNS records that decide whether your email lands in the inbox or in spam – checked live against your domain, with plain-English advice on anything that's off.
- MX · SPF · DKIM · DMARC
- Live DNS checks
- Free
01Email deliverability
Check SPF, DKIM and DMARC
The three DNS records that decide whether your email lands in the inbox or in spam – checked live, with what to fix if something's off.
02How it fits together
Four records decide your email's fate
Receiving servers don't take your word for who you are. They read these records from your DNS and act on what they find.
01
MX – receiving
Routes incoming mail to your provider. Without MX records the domain can't receive email at all.
02
SPF – who may send
Publishes the list of servers allowed to send as your domain, so receivers can spot mail from anywhere else.
03
DKIM – proof it's yours
A cryptographic signature on every message, verified against a public key in your DNS. Forwarding-proof where SPF isn't.
04
Selectors
The name a DKIM key is filed under in DNS. Your provider assigns it – Google uses "google", Microsoft 365 uses "selector1" and "selector2".
05
DMARC – the policy
Tells receivers what to do when SPF and DKIM both fail: deliver anyway, quarantine, or reject. This is what actually stops spoofing.
06
Reports
DMARC can mail you aggregate reports showing everyone sending as your domain – how you find forgotten services and impostors.
Want to see the raw records these checks read? Use the DNS lookup. Curious who owns a domain? That's the WHOIS lookup.
03FAQ
Questions we get asked
- What is SPF?
- A TXT record listing the servers allowed to send email as your domain. Receivers check the sending server against it; mail from anywhere else fails the check. It should end in ~all or -all so unlisted senders are actually rejected or flagged.
- What is DKIM, and what's a selector?
- DKIM signs each outgoing email with a private key; the matching public key is published in DNS so receivers can verify the message wasn't forged or altered. The selector is just the name the key is filed under – your email provider assigns it, which is why our checker asks for it if it isn't one of the common ones.
- What is DMARC?
- The policy that ties SPF and DKIM together. It tells receivers what to do with mail that fails both checks – nothing (p=none), spam-folder it (quarantine), or refuse it (reject) – and where to send reports. Without it, spoofed mail from your domain is much more likely to be delivered.
- Do I need all three?
- For business email today, effectively yes. Gmail and Microsoft now expect SPF and DKIM from every sender and DMARC from anyone sending in volume. Any one of them alone leaves a gap – SPF breaks on forwarding, DKIM says nothing about unsigned mail, and DMARC does nothing without the other two to lean on.
- My emails keep landing in spam. Will fixing these records help?
- Usually a lot. Missing or broken SPF, DKIM, and DMARC are the most common technical reasons legitimate business email gets junked. Content and sending habits matter too, but the records are where to start – and we can set them up for you.
- Where does this data come from?
- Live DNS resolution – the same records receiving mail servers read when they decide what to do with your message. Nothing is simulated, and results are cached for a minute at most.
Emails going to spam?
We set up SPF, DKIM, and DMARC properly as part of hosting and email migrations – and fix them when a receiver starts junking your mail.