SEO & Web★ Free forever✓ No account🔒 No upload📴 Works offlineUpdated April 28, 2026

Free DNS Lookup Tool — Query Any DNS Record Type Instantly

Look up any DNS record type for any domain directly from your browser. Enter a domain, select the record type, and see the live DNS response — no command line, no dig installation, no account required.

Browse all toolsBrowse more seo & web toolsBuilt by Achraf A., Full-Stack Developer · Morocco
DNS Lookup — free online tool interface

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.

Was this tool helpful?

What is DNS Lookup?

DNS (Domain Name System) is the internet's address book — it maps human-readable domain names to the IP addresses, mail servers, and configuration values that make domains actually work. Every time you visit a website, send an email, or configure a service on a domain, DNS records determine what happens. Understanding and being able to query these records is a fundamental skill for developers, system administrators, and anyone who manages websites or infrastructure. A DNS lookup tool lets you inspect these records without opening a terminal or remembering command-line syntax.

The most common record types you need to query are: A records (which IPv4 address a domain points to), AAAA records (IPv6), MX records (which mail servers handle email for the domain — critical for email deliverability debugging), CNAME records (aliases from one name to another, used for CDNs and third-party services), TXT records (verification tokens for Google Search Console, domain ownership proofs, SPF, and DKIM email authentication), and NS records (which nameservers are authoritative for the domain). Each type has a distinct purpose and debugging each one requires knowing what a valid response looks like.

DNS propagation is one of the most common sources of confusion for developers and site owners. When you change a DNS record, the old value is cached by resolvers worldwide for up to the record's TTL (Time To Live). During propagation — which can take minutes to 48 hours depending on the TTL — different users may see different DNS results for the same domain. Using a DNS lookup tool to query multiple resolvers (Google's 8.8.8.8, Cloudflare's 1.1.1.1, and your ISP's) helps you understand where propagation has completed and where the old value is still cached.

How to use DNS Lookup
  1. 1

    Enter the domain name

    Type the domain or subdomain you want to query (e.g. example.com or mail.example.com). Do not include https:// — just the bare domain.

  2. 2

    Select the record type

    Choose from A, AAAA, MX, TXT, NS, CNAME, SOA, or ANY. If you are not sure which type to check, start with A for the main address or MX if you are debugging email.

  3. 3

    Run the lookup

    Click Lookup to query the DNS for that domain and record type. Results show the record values, their TTL (time until they can change), and the class.

  4. 4

    Interpret and act on the results

    Compare results to what your DNS provider shows. If they differ, the old values are still cached — wait for the TTL to expire. If records are missing entirely, check your DNS provider configuration.

Key features and benefits
  • Queries all major DNS record types: A, AAAA, MX, TXT, NS, CNAME, SOA
  • Shows TTL values so you know how long before cached results refresh
  • Works entirely in the browser — no dig command, no terminal, no installation
  • Free and instant — no account, no API key required
  • Useful for debugging email delivery, CDN configuration, and domain setup
  • Query any public domain — not limited to domains you own
  • Results update in real-time on each query, reflecting live DNS state
Common use cases

A developer configuring a new domain checks the A record to confirm DNS is pointing to the right server IP before removing the maintenance page.

An email administrator checks MX records to verify that a domain's mail servers are correctly configured after migrating email providers.

A developer adding Google Search Console verification checks TXT records to confirm the verification token was added correctly by the DNS provider.

A site owner who changed hosting checks DNS propagation by querying A records and comparing to the old IP to see if the change has taken effect.

A developer setting up a CDN verifies CNAME records to confirm the alias is correctly pointing to the CDN's edge domain.

An operations engineer checks NS records to confirm which nameservers are authoritative for a domain after a DNS provider migration.

Why browser-based works better

A browser-based DNS lookup means you can check records from any machine — a work laptop, a client's device, a phone — without needing terminal access or an installed tool like dig or nslookup.

Results show the full record including TTL, which is the key piece of information you need to understand propagation timing — most simple DNS checkers omit it.

It pairs with the SSL Checker and IP Lookup tools, so you can diagnose a full domain configuration issue (DNS, SSL certificate, IP geolocation) without switching between different services.

The tool queries live DNS — not a cached result from a tool's own database — so the result reflects the current state of the DNS as your users would see it.

DNS Lookup FAQs

Quick answers about the workflow, privacy, and where this tool fits in a broader job.

What is the difference between an A record and a CNAME record?

An A record points a domain name directly to an IPv4 address. A CNAME record points a domain name to another domain name (an alias), which is then resolved to an IP. CNAMEs are used for CDN integration, third-party services, and subdomain aliasing.

Why do I see different DNS results depending on where I check?

DNS results are cached by resolvers worldwide for the duration of each record's TTL. During propagation after a change, different resolvers may still have the old cached value. Querying from different geographic resolvers is the only way to track propagation.

What does TTL mean in DNS?

TTL (Time to Live) is how long DNS resolvers cache a record before re-querying the authoritative server. A TTL of 3600 means resolvers cache the record for 1 hour. Low TTLs (300) are used when you plan to change records soon; high TTLs (86400) reduce DNS query load.

How do I check if my MX records are correct?

Query the MX record type for your domain. You should see one or more mail server hostnames (e.g. mail.google.com for Google Workspace) with priority numbers. Lower priority numbers = higher preference. The values should match what your email provider specifies in their setup guide.

Is DNS lookup data private?

DNS queries are inherently public — you can look up the records for any domain on the internet. However, this tool does not log your lookups or track which domains you query.

Keep the workflow moving with nearby tools that solve the next likely step.

Built and maintained by

Achraf A.

Founder & developer — built and maintains every tool on this site

Last updated:

Tested in Chrome, Firefox, and Safari on desktop and mobile.

☕ Support Us