Type a domain to see if its email authentication is set up correctly — and exactly what to fix so your emails stop going to spam.
The list of servers allowed to send email for your domain. We check that there is exactly one record, that it stays under 10 DNS lookups and how it ends (~all or -all).
A signature added to every email that proves it wasn't changed on the way. We look for the public key under the most common selectors and check its size.
Tells Gmail, Outlook and others what to do with mail that fails SPF or DKIM, and where to send reports. We read the policy, coverage and reporting address.
They are three DNS records that prove an email really comes from your domain. SPF lists the servers allowed to send for you, DKIM adds a cryptographic signature to each message, and DMARC tells receivers what to do when a message fails those checks — and sends you reports about it.
Since 2024, Gmail and Yahoo require SPF and DKIM for everyone, and DMARC for anyone sending more than 5,000 emails a day. Mail without them is far more likely to go to spam or be rejected outright.
Start with p=none and a rua address to collect reports. When the reports show only your own services sending, move to p=quarantine, and finally to p=reject, which blocks anyone spoofing your domain.
DKIM keys live under a selector (selector._domainkey.yourdomain) and there is no way to list them. We try the most common selectors; if yours is different, open "DKIM selector" and type it. You can find it in the DKIM-Signature header of an email you sent (s=…).
Each include:, a, mx and redirect in your SPF record costs a DNS lookup, and the standard allows only 10. Above that, receivers treat SPF as failed. Remove services you no longer use or flatten some includes into ip4:/ip6: ranges.
Yes. No account and no email address needed. Run it as often as you like for your own domains or your clients'.
Sendcorex sets up SPF, DKIM and DMARC for you, warms up your IPs automatically and watches the blocklists — free up to 3,000 emails a month.