Does your company's mail even reach the inbox?
Four DNS records decide most of it. Paste your domain and see what receivers see: which servers may send as you, what happens to mail that fails, and whether your signatures exist at all.
Which DNS records this check reads, and how the verdict is counted.
The domain you enter goes to our server, which looks up public DNS records through Cloudflare's DNS-over-HTTPS resolver. It asks for the MX records, the TXT records on the domain (looking for one that starts with v=spf1), the TXT record at _dmarc under the domain, and TXT records under twelve common DKIM selectors: default, google, selector1, selector2, k1, s1, s2, mail, dkim, zoho, mandrill and pm. You can paste a full email address or a URL and the domain part is taken from it. No message is sent and no mailbox is contacted. An email address, if added, is saved with the domain and the verdict.
The verdict is a count of problems. Each of these counts as one: no MX record, no SPF record, more than one SPF record, an SPF record containing ?all or +all, no DMARC record, a DMARC policy of none, and no DKIM key under any of the twelve selectors. Zero problems reads Looks right, one or two reads Worth fixing, three or more reads Losing mail. An SPF record ending in ~all, or with no all term, is described in its row but does not count against the verdict. The DKIM row names the selectors under which a key was found.
Several things that matter sit outside DNS. The check does not follow SPF include chains or count lookups against the limit of ten, does not verify that a published DKIM key matches the signatures on your mail, and does not test DMARC alignment between the visible From domain and the signing domain. From the DMARC record it reads the p tag only, not the subdomain policy or the percentage. Sender reputation, blocklists and message content are out of scope. An empty DKIM row may only mean a custom selector: open the headers of a message you sent and look for s= in the DKIM-Signature line.
- What is the difference between SPF, DKIM and DMARC?
- SPF is a DNS record listing the servers allowed to send mail for a domain. DKIM adds a cryptographic signature to each message, which receivers verify with a public key published in DNS. DMARC ties both to the address shown in the From header and tells receivers what to do when neither passes in alignment with it: nothing, quarantine or reject. It also names an address for aggregate reports.
- Why are my emails going to spam?
- The usual causes are missing or failing authentication (SPF, DKIM, DMARC), a sending address or domain with a poor reputation, a sudden jump in volume from a new domain, recipients marking earlier messages as spam, and content or links that filters associate with abuse. Authentication is the place to start, because large mailbox providers expect it from bulk senders and it is entirely in your own hands.
- Should an SPF record end with ~all or -all?
- An ending of -all asks receivers to fail mail from servers that are not listed; ~all marks it as a soft fail, which is usually accepted but treated with more suspicion. Where a DMARC policy is published, receivers evaluate DMARC on top of either result, so the difference matters less. A common path is to use ~all while confirming that every legitimate sender is listed, then switch to -all.
When one check is not the whole job.
The inbox desk answers what lands there, and the outreach guard makes sure what leaves passes these checks too.
