Does Gmail trust your domain?
Type your domain. We read its public DNS records and tell you which of the four things that decide delivery are missing — with the exact record to add.
- No signup, no email address
- Read-only DNS lookups
- Runs in your browser
Want it fixed rather than explained?
Send the domain and we will reply with the exact records to add — or do the whole deliverability fix with DNS access, migration and a before/after test.
Privacy: the lookups run from your browser to Cloudflare’s public resolver (1.1.1.1). We have no server in the middle, so we cannot log your IP or your domain, and nothing is sent to your mail server. The only thing that leaves this page is a DNS question that any resolver could answer.
Read-only DNS lookups, taken at the moment you press the button. DNS can change a minute later, and this check cannot see inbound filtering or blocklists.
What this check actually does
Your browser asks the public DNS resolver for the MX, TXT, _dmarc and _domainkey records of the domain you typed.
The four records are compared against what Gmail, Outlook and Yahoo actually require — not a score out of 10.
You get the record to add, or a one-line reason why it cannot be checked from outside.
Questions about the check
Yes, and it asks for nothing: no email address, no account, no cookie wall. It exists because most inbound enquiries start with the same four missing records, and we would rather show you than describe it.
A DKIM key lives at <selector>._domainkey.yourdomain, and the selector is chosen by your provider — nothing publishes the list. We try the twelve most common ones; if yours is not among them, the only honest answer is “not verifiable from outside”. Give us the selector and it becomes a yes or no.
It is the correct first step and a bad place to stop: reports arrive so you can see who legitimately sends as you, but nothing is enforced, so a forged message is only reported. The usual path is none → quarantine → reject over a few weeks.
No. These four records are necessary, not sufficient — content, sending reputation, blocklists and volume still matter. What we will say is narrower and true: with them in place, receivers stop judging you on someone else’s IP reputation.
Want it fixed rather than explained?
Send the domain and we will reply with the exact records to add — or do the whole deliverability fix with DNS access, migration and a before/after test.