The DNS Records Checker queries Cloudflare's DNS over HTTPS (DoH) API to instantly look up DNS records for any domain. Check A, MX, TXT, NS, CNAME, and more — plus compare Cloudflare vs Google DNS to detect propagation issues.
DNS Lookup
Filter by record type:
Querying DNS records...
DNS propagation in progress — Cloudflare and Google DNS returned different results for some record types. Changes may not have fully propagated globally.
No records found for the selected types. Try checking all types.
How to Use the DNS Records Checker
The DNS Records Checker uses Cloudflare's DNS over HTTPS (DoH) API to look up DNS records directly from your browser — no server required. It also queries Google DNS for comparison to detect propagation status.
Step 1: Enter a Domain
Enter the domain you want to look up — for example example.com. To look up subdomain records, enter the full subdomain: mail.example.com or _dmarc.example.com.
Step 2: Check All or Filter by Type
Click Check All to query all common record types at once, or select specific record types first to narrow results. The type filter buttons (A, AAAA, MX, NS, TXT, CNAME, SOA) toggle individual queries.
DNS Record Type Reference
- A — IPv4 address (where the domain resolves to)
- AAAA — IPv6 address
- MX — Mail exchange servers (for receiving email)
- NS — Name servers (authoritative servers for the domain)
- TXT — Text records (SPF, DKIM, DMARC, domain verification)
- CNAME — Canonical name (alias pointing to another domain)
- SOA — Start of authority (zone configuration)
Step 3: Check Propagation Status
The tool queries both Cloudflare (1.1.1.1) and Google (8.8.8.8) DNS resolvers. If they return different results, a propagation warning appears — meaning DNS changes haven't fully spread globally yet. This typically resolves within 1-24 hours depending on TTL settings.
Common DNS Troubleshooting Tasks
- Email not delivering — check MX records and verify they point to the correct mail server
- Verify SPF record — look up TXT records for a line starting with
v=spf1 - Domain not resolving — check A records to confirm an IP is assigned
- After DNS change — compare Cloudflare vs Google to verify propagation progress
FAQ
What is a DNS record and what are the different types?
DNS records map domain names to IP addresses and configure email, services, and security. A records point to IPv4 addresses. AAAA records point to IPv6 addresses. MX records define mail servers. NS records name the authoritative name servers. TXT records store arbitrary text for SPF, DKIM, domain verification. CNAME records alias one domain to another. SOA records define the zone's authoritative server and serial number.
Why do DNS changes take time to propagate?
DNS records have a TTL (Time To Live) that tells resolvers how long to cache the record. A TTL of 3600 means resolvers cache the record for 1 hour before checking for updates. Global DNS propagation can take up to 48-72 hours because each resolver around the world has its own cache. Lowering TTL before making changes (to 300 seconds/5 minutes) speeds up propagation.
What does it mean when Cloudflare and Google DNS show different results?
Different results from Cloudflare (1.1.1.1) and Google (8.8.8.8) indicate that DNS propagation is in progress. One resolver may have cached old records while the other has picked up the new ones. During propagation, some users may see the old site/mail and others the new one. Wait until both resolvers agree before considering propagation complete.
How do I check if my SPF or DKIM record is set correctly?
SPF records are TXT records starting with 'v=spf1'. Look up TXT records for your domain and look for the one starting with 'v=spf1'. DKIM records are TXT records under a selector subdomain like 'selector1._domainkey.yourdomain.com'. Enter that full selector subdomain in the search box and look up TXT records to see your DKIM public key.
What is the TTL in DNS records?
TTL (Time To Live) is the number of seconds a DNS resolver should cache a record before checking for updates. A TTL of 300 means the record is cached for 5 minutes, while 86400 means 24 hours. Lower TTLs mean faster propagation for changes but more DNS queries. Before making DNS changes, temporarily lower TTL to 300 seconds.
Why does this tool use Cloudflare DNS instead of my local resolver?
Cloudflare's DNS over HTTPS (DoH) API allows browser-based DNS queries — regular DNS uses UDP/TCP which browsers don't support directly. The DoH API returns clean JSON responses and is globally consistent, making it ideal for a web-based DNS checker. For comparing propagation, this tool also queries Google's DoH to show if records differ.