A free, no-signup, browser-based email authentication checker aimed at cold-email senders. You type a sending domain (a URL or email address also works—only the domain is kept), and the page reads its MX, SPF and DMARC records live from public DNS via Cloudflare\'s resolver (Google DNS as fallback), then grades MX, SPF and DMARC A–F and explains in plain words what to fix before sending cold email. It also probes ten common DKIM selectors (google, selector1, selector2, default, k1, s1, s2, resend, mail, dkim) and shows the DKIM result without grading it, because a key that cannot be found may still exist. Each card shows the record as published, what it means, what to change, and any record to publish ready to copy; the SPF card also lists each include and the DNS lookups it costs against the RFC 7208 limit of 10. Grading logic: MX, SPF and DMARC each pass/warn/fail, and the worst finding caps the grade—clean sheet A, one warning B, two or more warnings C, one fail D, two or more fails F. It marks p=none as a warning even though Google and Yahoo accept it, because it asks receivers to do nothing with failing mail. The page cites Google\'s and Yahoo\'s sender guidelines as checked on 21 October 2026 (every sender needs SPF or DKIM; bulk senders above 5,000/day to Gmail need SPF, DKIM and DMARC, with DMARC allowed at p=none; Yahoo requires a passing DMARC policy of at least p=none for bulk senders; DKIM keys must be 1024 bits or longer). Privacy: lookups run in the browser and go to the DNS resolver, never to the site\'s servers; nothing is stored beyond one page-view count and one completion event, neither of which holds the domain. Documented limits: DKIM selectors are private and cannot be enumerated, so \"no key found\" does not mean no DKIM (check the s= value in a sent email\'s DKIM-Signature header); the lookup count is an estimate; it reads DNS only, not sending IPs, blocklists, spam rate or copy—good records let mail land but do not make it land; and for cold email you should use separate domains, never the one your invoices come from.
Pros & Cons:
Pros: Free with no signup and no server-side storage—the DNS lookups run in the browser against Cloudflare/Google public resolvers, which is a genuinely privacy-preserving design for a domain-check tool; it grades three records and explains each finding in plain language with a copy-ready record to publish, rather than just dumping raw DNS output; the SPF card counts includes against the RFC 7208 10-lookup limit, which is the failure mode most senders actually hit; ten DKIM selectors are probed and the result is shown but deliberately not graded, with an honest explanation of why; it cites the specific Google and Yahoo sender rules with a checked-on date, and flags p=none as a warning instead of quietly passing it; the limitations section is unusually candid—it states outright that good DNS records do not guarantee inbox placement.
Cons: It only reads DNS—sending IP reputation, blocklists, spam rate and message content are out of scope, so a passing grade can still land in spam; DKIM coverage depends on ten guessed selectors, so a provider using another selector will show \"not found\" and require manual header inspection; the SPF lookup count is an estimate because a receiver stops at the first match; there is no bulk/portfolio check—you must check every sending domain one at a time, which is tedious for agencies managing many domains; there is no API or export surfaced, so results cannot be piped into a monitoring workflow; the page\'s deeper value sits behind a paid GTM teardown service that bundles this check with ICP and cold-email writing, so the free tool is partly a lead magnet; and no independent third-party reviews of the tool itself surfaced, only a Product Hunt listing.
Who is it for?:Cold-email senders and agencies who need to confirm SPF, DKIM and DMARC are correctly published before a campaign goes out; marketers and founders setting up a new outbound domain who want a plain-language read on what is broken; teams affected by Google\'s and Yahoo\'s bulk-sender rules who need a quick check against those requirements; privacy-conscious users who want a DNS check that does not send their domain to a third-party server; anyone troubleshooting \"why is my email going to spam\" who has already ruled out content and wants to verify authentication records first.