Developer

Email Authentication Checker

Resolve a domain's public email-authentication TXT records, identify missing, malformed or conflicting SPF/DMARC/DKIM records, and export the findings.

View Developer Tools

The entered domain and optional DKIM selector are sent to Tool Teaze's bounded server-side DNS resolver. No message contents are accessed.

Enter a domain only, without https://, a path or an email address.
DKIM cannot be discovered reliably without a selector. Find it in your mail provider or a received message header.

No DNS check has been run.

What this tool does

The checker validates a public domain, performs bounded server-side TXT lookups for root SPF, _dmarc and an explicitly supplied DKIM selector, then distinguishes missing, conflicting and apparently malformed records.

How to use it

  • Enter a domain without a URL or email address.
  • Optionally enter the DKIM selector from your provider or a real message header.
  • Review, copy or export the DNS findings and verify them against a real received message.

Example input and output

Input: example.com and selector selector1

Output: Separate SPF, DMARC and DKIM statuses, records and recommendations

Common use cases

  • Checking a new sending domain
  • Reviewing a DMARC rollout
  • Troubleshooting a known DKIM selector

FAQ

Can DKIM be checked without a selector?

Not reliably. DKIM keys live under selector-specific DNS names, so the tool reports DKIM as not checked unless you supply the selector.

Does a passing result prove email is authenticated?

No. DNS records alone do not prove message-level SPF/DKIM results or DMARC alignment. Verify a real received message's Authentication-Results header.

What does p=none mean?

It is DMARC monitoring mode. Messages are not requested to be quarantined or rejected, so the tool reports a warning rather than enforcement.

Are paid APIs used?

No. The same-origin server uses public DNS resolution with validation, timeouts and rate limits.