DNS Propagation Checker
Check your domain's DNS records live across global servers. Verify A, MX, CNAME, and TXT records instantly.
Built With Care
“DNS changes don't propagate instantly — resolvers cache records based on TTL values. This tool hits live DNS-over-HTTPS endpoints so you see the current state from specific resolvers, not a global average.”
DNS Lookup & Propagation Checker
Look up A, AAAA, MX, CNAME, TXT, and NS records for any domain. Queries Cloudflare and Google DNS over HTTPS so you can see what resolvers are actually returning right now.
- 1Enter the Domain Name (e.g., example.com) in the search field above.
- 2Select your Record Type (A, MX, CNAME, TXT, etc.) to fetch specific data.
- 3Analyze the Authoritative Answers returned directly from Google Public DNS over HTTPS.
- 4Verify TTL (Time To Live) settings to see how long records are cached by resolvers.
- 5Use the results to troubleshoot domain connection issues or verify new mail server settings.
- Instant Global DNS Check: Verify if your DNS changes have propagated across major global resolvers.
- Multi-Record Support: Query A (IPv4), AAAA (IPv6), MX (Mail), CNAME (Aliases), and important TXT records.
- Security-First Queries: Uses encrypted DNS-over-HTTPS (DoH) to ensure your lookup data remains private and tamper-proof.
- Developer-Grade Metadata: See full record content, including SPF/DKIM strings and priority values for mail servers.
- No-Rate-Limit Lookups: Perform unlimited domain scans with zero registration required.
Real Ways People Use This
Domain Migration Verification
Confirm DNS changes have propagated after switching hosting providers or updating nameservers.
Email Server Configuration
Verify MX records point to the correct mail server and check SPF/DKIM TXT records for email deliverability.
SSL Certificate Troubleshooting
Check if A and CNAME records resolve correctly when troubleshooting HTTPS certificate issues.
- Propagation timing depends on resolver caches and TTL, so global consistency is rarely instant.
- Querying one resolver does not guarantee all regions have updated records yet.
- DNS correctness alone does not confirm app health; origin/firewall/SSL layers can still fail.
- 1Query correct record type and verify expected target values.
- 2Check TTL and compare responses across multiple lookups over time.
- 3After DNS looks correct, validate end-to-end service behavior (HTTPS/app/mail).