DNS Record Lookup & Propagation Checker
Compare common DNS record answers from Cloudflare and Google public resolvers.
Enter a public domain to inspect A, AAAA, CNAME, MX, TXT, NS, and CAA records.
The domain is sent to CodeAva and two public DNS-over-HTTPS resolvers. Results are point-in-time observations, not a global propagation guarantee.
The public domain is sent to CodeAva, Cloudflare DNS, and Google Public DNS. Inputs are not saved by CodeAva, but resolver providers apply their own logging policies.
Overview
Compare A, AAAA, CNAME, MX, TXT, NS, and CAA DNS answers from Cloudflare and Google public resolvers with conflict guidance.
Start with one of the included examples, inspect every finding, and verify consequential changes against the linked primary documentation and your own environment.
Use cases
When to use it
- Example 1.Compare a domain's web, mail, verification, authoritative nameserver, and certificate-authority records.
- Example 2.Spot resolver differences during a TTL-based migration without treating two vantage points as a worldwide guarantee.
When it's not enough
- Production guarantees.A point-in-time tool result cannot prove every runtime, resolver, client, or edge location behaves the same way.
- Blind automation.Review generated output and findings before committing configuration or security changes.
How to use it
- 1
Load or paste a representative input
Compare a domain's web, mail, verification, authoritative nameserver, and certificate-authority records.
- 2
Run the focused checks
Read the exact path, record, operation, or certificate field attached to each finding.
- 3
Verify and apply
Use DNS record debugging guide and the related tools to confirm the fix before release.
Common errors and fixes
The input is incomplete or malformed
Reduce it to the smallest reproducible sample, correct the parse error, and rerun the check.
The tool passes but production still fails
Compare environment-specific inputs, network vantage points, versions, caches, and full standards conformance.