DNS Lookup Tool — Check DNS Propagation & MX, TXT Records Free

Free DNS Lookup Tool — check DNS records for any domain online instantly

Look up A, AAAA, CNAME, MX, NS, TXT, and SOA records for any domain directly in your browser. All queries use secure DNS‑over‑HTTPS — your lookups never touch our servers and require no account.

Quick Answer

How do I check if DNS has propagated for my domain?

Enter your domain in the lookup tool above and check the A record. If it shows your new IP address, DNS has propagated to that resolver. Propagation takes 0–48 hours depending on your domain's TTL setting — the lower the TTL, the faster the change spreads. Run the lookup repeatedly until you see the new record.

Query Configuration

Do not include http:// or trailing slashes.


DNS record types and what they control

RecordPoints toCommon use
AIPv4 address (e.g. 93.184.216.34)Root domain and subdomains to a server
AAAAIPv6 addressIPv6 server address — increasingly common with CDNs
CNAMEAnother hostnamewww → apex, or custom domain → CDN hostname
MXMail server hostname + priorityEmail routing — required for receiving email
TXTArbitrary textSPF, DKIM, DMARC, domain verification tokens
NSNameserver hostnameDelegates DNS authority to a specific provider
SOAZone metadataStart of authority — read-only, set by registrar
CAACertificate Authority nameRestricts which CAs can issue SSL certs for the domain

TTL and why DNS propagation takes time

TTL (Time To Live) is the number of seconds a resolver caches your DNS record before re-querying the authoritative nameserver. A TTL of 3600 means resolvers keep your old record for up to one hour after you change it. This is why "DNS propagation" takes time — every recursive resolver worldwide has its own cache, and they expire independently.

Best practice before a planned DNS change: lower your TTL to 300 (5 minutes) at least 24 hours before making the change. After the change is verified, raise the TTL back to 3600 or higher. Lower TTL = more DNS queries (slightly more load) but faster propagation. Production A records typically run at 3600; records you change frequently (like CNAME for feature flags) can stay at 300.

To check whether a DNS change has reached a specific resolver, use: dig @8.8.8.8 example.com A (queries Google's resolver) or dig @1.1.1.1 example.com A (queries Cloudflare). Seeing different results from different resolvers is expected during propagation — it just means their caches haven't expired yet.

DNS record types — what each record does

Record typePurposeCommon use cases
AMaps domain to IPv4 addressPoint example.com to your server IP — the most basic DNS record
AAAAMaps domain to IPv6 addressIPv6 equivalent of A record — increasingly required for full coverage
CNAMEAlias from one domain to anotherwww → example.com; subdomain → CDN provider hostname
MXMail exchanger — where email is deliveredRequired for email to work; set to your email provider (Google Workspace, Outlook, etc.)
TXTArbitrary text associated with the domainSPF (email anti-spoofing), DKIM, DMARC, domain ownership verification for Google/Cloudflare
NSName servers for the domainPoints to which DNS servers are authoritative for your domain
SOAStart of Authority — zone metadataContains primary NS, admin email, serial number, refresh intervals
CAACertificate Authority AuthorizationRestricts which CAs can issue SSL certs for your domain
PTRReverse DNS — IP to hostnameUsed by email servers to verify sender legitimacy; set at the hosting level
SRVService location recordUsed by VoIP (SIP), XMPP, Microsoft Teams for service discovery

TheFreeAITools — DNS Lookup Tool is a fully private, browser‑based utility for looking up A, AAAA, CNAME, MX, NS, TXT, and SOA records. All queries are sent directly from your device to a public DNS resolver using DNS‑over‑HTTPS — no server‑side logging, no account, and no cost. Perfect for web developers, system administrators, and anyone who needs fast, reliable DNS diagnostics in 2026.

Video demo

☕ Support Us