Public-record triage
Email Auth Inspector and Security Triage
Use this collection as a public DNS, email-authentication, and public-response signal report.
Step 1
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.
Step 2
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.
Step 3
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.
Step 4
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.
Workflow notes and help
Check MX, SPF, DMARC, DNS, redirects, headers, SSL, and public website lookup signals before deeper provider-specific review.
- 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.
- 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 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 DMARC review: Missing DMARC, multiple records, monitor-only policy, or report destinations you do not control should be reviewed before relying on the policy.