Email authentication
35%- DMARC record, policy, and subdomain policy
- Report addresses and their authorization
- SPF record, lookup count, and ending
- DKIM on 16 common selectors
- BIMI
New 40+ checks across email, DNS, and your domain
One check scores your domain from 0 to 100 across its email, its DNS security, and the website behind it: DMARC, SPF, DKIM, MX, MTA-STS, TLS-RPT, DNSSEC, CAA, blocklists, certificates, and registration. Every fix comes with the exact record to publish.
Example report
This is an example for acme.example, a typical Google Workspace domain. Every fix lists the record to publish and the points it adds.
Example for acme.example, not a real domain
Overall healthGood
Solid authentication, but mail in transit is unprotected. 4 fixes to 100.
Mail providerGoogle Workspace
There is no MTA-STS record at _mta-sts.acme.example.
MTA-STS makes senders deliver your mail only over verified TLS, which blocks downgrade attacks.
There is no TLS-RPT record at _smtp._tls.acme.example.
TLS reports tell you when mail to you was not encrypted.
No CAA records, so any certificate authority may issue certificates for your domain.
CAA limits which certificate authorities can issue certificates for your domain.
Receivers send mail that fails DMARC to spam.
Reject is the setting that stops spoofed mail from reaching inboxes.
The pct tag is a legacy tag that RFC 9989 removed; pct=100 does nothing.
One valid DMARC record is published at _dmarc.acme.example.
DMARC tells receivers what to do with mail that pretends to be your domain.
v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@acme.example
The record has a rua address, so receivers send aggregate reports.
Reports show who sends mail as your domain and whether it passes.
Every report address is on your own domain.
Subdomains follow the main policy.
One SPF record is published at acme.example.
SPF lists the servers allowed to send mail for your domain.
v=spf1 include:_spf.google.com ~all
The SPF record needs 1 DNS lookup; the limit is 10.
The record ends in ~all.
Selector google publishes a 2048-bit RSA key.
DKIM signs your mail so receivers can tell it was not altered or forged.
smtp.google.com resolves to an address.
Senders need MX hosts that resolve to deliver mail.
142.250.31.27 resolves to mail-lf1-f27.google.com, which points back to it.
Many receivers distrust mail servers whose reverse DNS does not match.
Your mail servers and domain are on none of the 8 blocklists we checked.
A listing makes receivers reject or junk your mail.
Google Workspace accepts encrypted connections for incoming mail.
STARTTLS lets other servers encrypt mail on its way to you.
The zone is signed and a validating resolver accepts it.
DNSSEC stops attackers from forging answers for your records.
4 nameservers at Google Cloud DNS, and each resolves to an address.
Two or more working nameservers keep your domain reachable when one fails.
The SOA timers are consistent.
The registration runs until 2027-05-07 at Example Registrar.
An expired domain stops your website and mail.
The domain was registered on 2025-09-14.
Receivers trust older domains more.
The registrar lock is on, so the domain cannot be transferred without your approval.
The lock blocks unauthorized transfers of your domain.
The certificate is valid until 2026-12-30 and issued by Google Trust Services.
An invalid or expired certificate shows visitors a security warning.
The name has an IPv6 address.
Some networks reach websites only over IPv6.
Publish the TXT record and serve the policy file over HTTPS at mta-sts.acme.example with a valid certificate.
v=STSv1; id=20261019
version: STSv1 mode: enforce mx: smtp.google.com max_age: 604800
Publish a TLS-RPT record so senders report TLS failures to tlsrpt@acme.example; create that mailbox first.
v=TLSRPTv1; rua=mailto:tlsrpt@acme.example
Change the policy to p=reject once DNS Autopilot's reports show every real sender passes. The pct tag is dropped.
v=DMARC1; p=reject; rua=mailto:dmarc@acme.example
Allow only pki.goog, the authority behind your current certificate, to issue certificates for your domain.
0 issue "pki.goog"
What it checks
A domain is more than its website. The check reads five areas and weights them into one score, so you see what to fix first.
Email is the deepest area today: it also reads your DMARC reports to show which senders fail. We plan to add other kinds of checks over time, such as uptime, AI crawler access, and SEO.
DMARC reports
DNS tells you what you published. Your DMARC reports tell you what actually happened to your mail.
Free for one domain. Gmail connect on Pro and Agency, plus the 14-day trial.
Senders last 30 days
SamplePassed DMARC Failed
30 days ago15 days agoToday
Ready for p=rejectDay 21 of 30
Passed 6,067 messages from 4 reportersPassed 21 of 30 days cleanFailed Mailchimp fails DKIM
See your real senders
Connect Gmail, or add your report address to your DMARC record. Free for one domain.
Monitoring
DNS Autopilot re-checks your domain every day and reads new DMARC reports as they arrive. When something changes, you hear about it before your mail does.
Score history
Example: acme.example, last 30 days
A weekly digest arrives every Monday with your score, mail volume, pass rate, and new senders.
Alerts
What DNS Autopilot emails you
Add a domain to a free account and we re-check it every day. One domain is free.
Who it is for
The problem You send from Google or Microsoft plus a few tools, and nobody has time to read XML.
The result See each sender in plain words, fix what fails, and get a yes or no on the next policy step.
The problem You run email for clients and need proof the work is done, without a login per client.
The result Agency plan: up to 100 domains, domains grouped by client, and a weekly digest per client.
The problem A newsletter tool, a CRM, or a store platform sends as your domain and mail lands in spam.
The result Find the sender that fails alignment, with one sentence on the DNS record to add.
The problem Transactional mail goes out through services such as Amazon SES or SendGrid, and one bad record breaks it.
The result Watch SPF lookups, DKIM keys, and pass rates, and get an alert when a new sender fails.
How it works
From sign-in to your first readiness result takes a few minutes.
Connect Gmail and DNS Autopilot finds the report emails itself, with no DNS change. Or add your report address, token@rua.dnsautopilot.com, to the rua tag of your DMARC record. That works with any mailbox, including Microsoft 365.
Reports are checked, unpacked, and grouped by sending source, with the service behind each one and a one-sentence fix for anything that fails.
When the numbers are good, DNS Autopilot shows the exact record to publish for p=quarantine, then p=reject.
Features
One health view per domain: its score, its senders, and the next safe step.
Read-only access to DMARC report emails and nothing else. 3 Gmail mailboxes, synced hourly; Agency allows 10. It is on the trial and paid plans until Google verifies the app.
Every account gets token@rua.dnsautopilot.com. Add it to your DMARC rua tag and reports arrive without any mailbox access.
Zip, gzip, and plain XML from any provider, unpacked in memory with limits on size and compression ratio.
Each report email is checked against the reporting provider's own authentication. Reports that fail the check are stored but never count toward readiness.
Sending IPs are named through reverse DNS and DKIM domains: Google Workspace, Microsoft 365, Amazon SES, SendGrid, Mailchimp, HubSpot, Shopify, and more.
Mail relayed by Google Groups, iCloud, Fastmail, and mailing list software is marked as forwarded, so it does not look like an attack.
Built from your policy, the 30-day pass rate, DNS problems, and the share of mail from unknown failing senders.
A plain yes or no with reasons: at least 98 percent of mail from known senders passing, 500 messages from two reporters, over 14 days for quarantine and 30 for reject. When it is yes, you get the exact record to publish next.
Each known service that fails comes with a sentence on what to change. Unknown senders are flagged as possible spoofing.
Every domain you add is re-checked each day against 40+ checks: DMARC, SPF, DKIM, MX, MTA-STS, TLS-RPT, DNSSEC, CAA, blocklists, certificates, and registration. The score from 0 to 100 keeps its history, and each fix shows the points it adds.
Email when a new sender starts failing, the pass rate drops, your DMARC record changes, the health score drops or a check starts failing, Gmail disconnects, or a domain becomes ready for its next policy.
A weekly summary of mail volume, pass rate, new failing senders, and readiness. On Agency it is sent per client.
Download any report as CSV or as the original XML.
Name your clients, assign each domain to one, and manage up to 100 domains.
30 days on Free, 13 months on Pro, 25 months on Agency.
Score any domain from 0 to 100 in about three seconds, with the exact record for each fix. Twenty checks an hour, no sign-up.
Trust
You are handing over a view of your mail, so the limits are narrow and written down.
The only scope is gmail.readonly, requested only when you connect a mailbox.
One fixed search finds report attachments. Other mail and message text are never read.
Use of Google data follows the Google API Services User Data Policy, including the Limited Use requirements. It is not sold or used for advertising. Read the policy.
Settings removes your reports, domains, Gmail connection, and tokens at any time.
On Google Cloud. Payments run through Stripe, so we never see your card number.
Compared
Most teams start with raw reports or a free viewer, or get quoted for an enterprise platform. This sits between them.
Pricing
Start free with one domain. Pro adds alerts, the weekly digest, longer history, and Gmail connect, with a 14-day trial that needs a card. Cancel any time from Billing.
$0 forever
$19 a month
$49 a month
Guides
Plain answers on SPF, DKIM, DMARC, and the rest of your domain's email health.
Move DMARC from p=none to p=reject without losing legitimate mail: collect reports, fix senders, then quarantine and reject, with clear criteria for each step.
Mail in transitSet up MTA-STS and TLS-RPT step by step: the DNS records, the mta-sts.txt policy file, a safe testing-to-enforce rollout, and the mistakes that break mail.
Email authenticationSPF allows 10 DNS lookups. Go over and it returns permerror, which can fail DMARC. See what counts, how to count yours, and how to fix it safely.
Questions
When a domain publishes a DMARC record with an rua address, mailbox providers such as Google, Microsoft, and Yahoo send a daily zipped XML report to that address. Each report lists the servers that sent mail as your domain and whether that mail passed SPF and DKIM alignment. They are accurate and almost unreadable, which is why most domains never look at them.
Only DMARC report emails. It runs one fixed search for messages with a report-style subject and a .xml, .gz, or .zip attachment, then reads the sender, subject, date, authentication headers (Authentication-Results and ARC), and those attachments. It never reads other mail or any message text. The exact query is on the Gmail page, and you can disconnect at any time.
Every account gets a report address of the form token@rua.dnsautopilot.com. Add it to the rua tag of your _dmarc record and reports arrive there directly. It works with any mailbox, and it is the better route when the mailbox belongs to a client or a shared inbox.
It looks only at reports it can verify came from the reporting provider, and it leaves known forwarders out of the count. A domain is ready for quarantine when at least 98 percent of the mail from known senders passed for 14 days with no sender left to fix, and ready for reject on the same test over 30 days. It also needs at least 500 messages from at least two reporters in that window. Each result lists the reasons in plain sentences.
Parsed reports and their raw attachments are kept for 25 months. Gmail message ids, used only to avoid importing a report twice, are kept for 60 days. You can delete everything from Settings at any time, including the Gmail connection and the stored reports.
Pro starts with a 14-day trial that needs a card and includes Gmail connect. Cancel from Billing at any time: you keep the plan until the end of the period you paid for, and a trial cancelled in time is not charged. There is no contract.
No. Enter a domain on the check page and in about three seconds you get a score from 0 to 100 across more than 40 checks: DMARC, SPF, DKIM, MX, reverse DNS, blocklists, STARTTLS, MTA-STS, TLS-RPT, DNSSEC, CAA, the HTTPS certificate, and registration. Each problem comes with the exact record to publish. It is limited to 20 checks an hour per visitor.
Every check passes, warns, or fails. They fall into five areas, and the overall score weights them: email authentication 35%, mail servers 20%, mail in transit 15%, DNS security 15%, and domain and website 15%. Each fix shows the points it adds, and the fix plan shows the score you would reach with all of them applied.
Small businesses that send mail through a handful of services such as Google Workspace, a CRM, a newsletter tool, and a store, and the agencies and IT providers that run email for them. The Agency plan groups domains by client and sends a digest per client.
It can if a real sender is not aligned, which is why DNS Autopilot only says a domain is ready when known senders pass and no known service is still failing. Go in steps: p=quarantine first, then p=reject. Each step comes with the exact record to publish, and you can go back to the previous policy by editing the record.
With Gmail connect, no: reports are read from your mailbox. With the report address you change one thing, the rua tag of your _dmarc record, to include token@rua.dnsautopilot.com. DNS Autopilot only reads public DNS records and never changes them; you publish any later policy change yourself.
Yes, through the report address, which works with any mailbox and any DNS host. Gmail connect is for Google mailboxes only. Microsoft 365 mail is recognized as a sending source, and the setup guide lists where to edit the DMARC record at common DNS hosts.
Yes, on the Agency plan: up to 100 domains, grouped by client, with a weekly digest per client. Point each client's rua tag at your report address, or connect a mailbox that already receives their reports.
Yes. It names the service behind each sending IP, shows whether SPF or DKIM aligned, and says what to change when it did not. It also checks your SPF lookup count against the limit of 10 and the DKIM keys for the selectors seen in your reports.
Add a domain to a free account and we re-check it every day and read its DMARC reports. Free for one domain.