Ready signal
Ready for provider review
MX, SPF, DMARC, and DNS lookup results are present, recent changes have settled across resolvers, and the records match the provider setup you intended.
Public-record triage
Email Auth Inspector and Security Triage
Use this collection as a public DNS, email-authentication, and public-response signal report. It is not a deliverability guarantee, penetration test, vulnerability scanner, private-network inspection, or provider-specific setup audit.
Start here
Choose the next recovery path
Email authentication changed Run the combined Email Health Report, then inspect MX, SPF, DMARC, DNS, and resolver differences before editing records again. SPF or DMARC looks wrong Open the specific record checker, then compare against DNS lookup and provider instructions. Website launch check Check DNS, redirects, status, headers, and SSL before deeper review. Header report looks weak Use security-header troubleshooting before treating a single report as a full audit.
Preflight result
Email authentication readiness
Review these signals together before changing DNS records or escalating to a mail provider. Ready means the public records are easier to inspect, not that delivery is guaranteed.
Needs review
Needs DNS review
Missing records, resolver differences, malformed hostnames, or recent changes should be checked before treating a mail issue as an application problem.
Needs review
Needs SPF review
Missing SPF, multiple SPF records, weak all mechanisms, or provider includes you do not recognize should be reviewed with your sender setup.
Needs review
Needs DMARC review
Missing DMARC, multiple records, monitor-only policy, or report destinations you do not control should be reviewed before relying on the policy.
Task groups
Start with the part of the workflow that is failing
Inspect email authentication
Check MX, SPF, DMARC, root DNS, and resolver differences together so email-authentication issues are routed through public record signals before deeper provider work.
Check DNS and reachability
Review DNS records, website IP addresses, propagation-like resolver differences, redirect chains, and basic status before interpreting header or certificate reports.
Review headers and redirects
Inspect response headers, security-header signals, redirect behavior, and final-status differences without treating the report as a full site-safety verdict.
Check SSL and domain registration signals
Review certificate details, host expectations, website IPs, and RDAP-style registration fields as part of public launch or handoff triage.