Network

Mail Health and SPF/DMARC

Check MX, SPF, DMARC and a DKIM selector; prepare DNS record drafts for your sending sources and review them before publishing.

01 / QUERY

Inspect your email domain

Find it in your sending service or the s= field of a message’s DKIM-Signature header. Leaving this blank means DKIM is unknown; selectors are not guessed.

All your sending sources

Include business email, your website, CRM, newsletters and transactional mail services. MX records do not identify your sending sources.

Enter one value per line or separate values with commas. Omit the include: prefix.

Leave blank to keep existing rua, or omit it from a new record. Reports contain sending information. Use an address that accepts these reports.

Only DNS records are inspected. No email is sent and no DNS records are written. Each analysis makes at most 4 DNS requests, each limited to 3 seconds.

Security verification

Checked by Cloudflare to limit automated queries.

02 / RESULTS

Mail infrastructure findings

Your results will appear here

Enter the information above and start the query.
Data will appear here when it is ready.

Your query is running

Complete the verification above if needed. Your previous results are preserved.

Waiting for the server’s response. This may take a little while.

Why does mail go to spam? Where should you start?

SPF concerns the sending server, DKIM the message signature, and DMARC alignment with the visible From domain. Correct DNS may be necessary but cannot guarantee inbox delivery.

Google Workspace setup

  1. Include every sender in one SPF record. Google Workspace uses include:_spf.google.com; add your website and other services to the inventory too.
  2. In the Admin console, open Apps → Google Workspace → Gmail → Authenticate email and generate the domain’s DKIM record. Publish the supplied TXT value, then start authentication in that panel.

Microsoft 365 setup

  1. Include every sending service in one SPF record. Microsoft 365 uses include:spf.protection.outlook.com; retain other legitimate sources.
  2. Publish the exact selector1 and selector2 CNAME targets shown for your domain in Microsoft Defender; do not guess them. Enable DKIM signing, then query the selector shown in the panel.

DMARC

Set up SPF/DKIM first and verify From alignment. Monitor DMARC with none and an authorized reporting address; move to quarantine/reject based on reports. Inspecting a message header is a separate step from checking published DNS.