We host on Hostinger — get up to 20% off your first plan.Get the link →
Referral link · we may earn a commissionReferral link — we may earn a commission at no extra cost to you.Download a working automation JSON
Can AI answer engines cite your site?
Outreach scripts that get replies
Find the 3 workflows costing you sleep
200+ prompts, ready to ship
12-month posting plan in 60 sec
Brand voice doc in 4 steps
Runway / Pika / Sora / Veo formats
Enter a domain and this tool runs a live SPF, DKIM, DMARC, and MX check against its actual DNS records — pulled fresh from Google Public DNS-over-HTTPS, not a cached database — with a plain-English verdict on each one.
Updated August 2026
Why this tool exists
Deliverability isn't about clever subject lines. It is three DNS records — SPF, DKIM, DMARC — and whether the server receiving your mail can prove you're actually authorized to send as your domain. Gmail and Yahoo tightened their bulk-sender requirements in 2024 specifically around these three records, and most small businesses I've audited have at least one of them missing or set to a do-nothing default.
SPF (Sender Policy Framework, RFC 7208)lists which mail servers are allowed to send as your domain. Receiving servers check the sending IP against this list. Miss it, and you're relying entirely on DKIM and DMARC to vouch for you.
DKIM (DomainKeys Identified Mail)attaches a cryptographic signature to outgoing mail, proving the message wasn't altered in transit and really came from a server holding your private key. There's no DNS record listing which selector name your provider uses — which is why this tool probes 8 common ones rather than claiming certainty either way.
DMARC (RFC 7489) is the enforcement layer: it tells receiving servers what to do when SPF or DKIM fails — nothing (p=none), quarantine to spam (p=quarantine), or reject outright (p=reject). Publishing DMARC at p=none and never moving past it is the single most common gap this tool finds — the record exists, so it looks configured, but it enforces nothing.
Pair this with the Domain Trust & Age Lookup before you vet a vendor or lead, and the Cold Outreach Compliance Checker before you send anything at volume.
Waseem, building from Bali · info@skynetjoe.com
Reference
| Policy | What happens on failure | Enforcement level |
|---|---|---|
| p=none | Nothing — report only, mail still delivers | None (monitoring) |
| p=quarantine | Failing mail routed to spam/junk | Moderate |
| p=reject | Failing mail rejected outright | Strongest |
Quick answers
Four things, all read live from your domain's DNS: SPF (which servers are authorized to send as you), DMARC (what happens when a message fails authentication), DKIM (whether outgoing mail is cryptographically signed — probed against 8 common selector names, since there's no DNS record that lists selectors in use), and MX (which provider receives your mail). Every value shown is the actual DNS answer at the moment you run the check.
p=none tells receiving servers "authenticate this mail, but don't do anything if it fails — just send me a report." It's a monitoring-only mode. Spoofed mail using your domain still lands in inboxes. It's a common default because it's the safe first step when rolling out DMARC, but if it's been sitting at p=none for months, nothing is actually being enforced.
Not necessarily. DNS has no directory of DKIM selectors in use, so this tool probes 8 common selector names (google, default, k1, s1, s2, selector1, selector2, mx). A real DKIM setup using a custom selector name will show as "missing" here even though DKIM is fully configured. Check your email provider's DKIM setup page for the selector it actually publishes.
The domain you enter is sent directly from your browser to Google's public DNS-over-HTTPS API (dns.google) — the same public DNS resolver anyone can query. Nothing is logged, stored, or sent to SkynetJoe's servers.
Either the domain doesn't exist (check the spelling), or it's registered but has never had mail-related DNS records configured — common for a domain that's parked or only used for a website, not email.