SPF
The list of servers allowed to send as your domain. We count the DNS lookups it makes, because over 10 breaks it, and check how it ends: -all and ~all are fine, +all lets anyone send as you.
Check SPF, DKIM and DMARC for any domain. See what is missing and the exact record to add.
The list of servers allowed to send as your domain. We count the DNS lookups it makes, because over 10 breaks it, and check how it ends: -all and ~all are fine, +all lets anyone send as you.
A signature on every message. We look for it at the selector names providers commonly use, or at the one you give us.
The policy and the reports. We read the policy, how much mail it covers, whether you get reports, and whether it is inherited from a parent domain.
Whether the domain can receive replies, whether it is on the Spamhaus domain blocklist, and whether MTA-STS, TLS-RPT or BIMI are set up. Those last three are optional.
SPF lists the servers allowed to send mail for your domain. DKIM adds a signature so receivers can tell a message was not changed on the way. DMARC tells receivers what to do when SPF and DKIM fail, and sends you reports. Together they are how receiving servers decide whether mail that says it is from you really is.
Missing or broken SPF, DKIM or DMARC is one of the most common reasons, and the easiest to fix. Others are a new or low-reputation sending address, sending to people who did not ask for mail, links to bad sites, or too much volume too fast. This tool checks the first group. It cannot see your sending reputation.
A DKIM record lives at a name that depends on your mail provider, such as selector1._domainkey.yourcompany.com. We try the common ones. If your provider gave you a record and you added it, open “I know my DKIM selector” and enter the part before ._domainkey to check it exactly.
Start with p=none and a reporting address, read the reports for a few weeks, then move to p=quarantine and finally p=reject once only your own mail passes. Going straight to reject can block your own legitimate mail.
An SPF record may cause at most 10 DNS lookups. Each include, a, mx, ptr and exists counts, including the ones inside the records you include. Over 10, receivers treat the whole record as broken. Remove services you no longer use.
No, and nothing can. Correct records are necessary, not sufficient: inbox placement also depends on your reputation and what you send. A good score means the technical basics are in place.
No. We read public DNS records to answer, and keep nothing about your domain. Results are cached for a minute to be kind to DNS servers.
Learn more: What is SPF? · What is DKIM? · What is DMARC? · Why emails go to spam. Want the records added and checked for you? See how SendSend verifies a domain, or read the deliverability guide.