DNS Lookup
Query any DNS record type for any domain instantly — A, AAAA, MX, TXT, CNAME, NS, SOA or all at once.
Free · No credit card · 50 credits/day
DNS record types explained
Every record type supported — what it stores and when you'd query it.
A
Maps a hostname to an IPv4 address. The most common record — what resolves example.com to 93.184.216.34.
example.com → 93.184.216.34
AAAA
Same as A but for IPv6 addresses. Required for IPv6-only network access.
example.com → 2606:2800:220:1:248:1893:25c8:1946
MX
Lists the mail servers that accept email for the domain, with priority values (lower = higher priority). Check these when debugging email delivery.
10 mail.example.com
TXT
Used for SPF, DKIM, DMARC, domain ownership verification (Google, GitHub, etc.) and many other protocol extensions.
v=spf1 include:_spf.google.com ~all
CNAME
An alias that points one hostname to another. www.example.com → example.com. Cannot be used at the zone apex.
www.example.com → example.com
NS
Lists the nameservers responsible for a domain's DNS zone. These are the servers that answer DNS queries for the domain.
ns1.example.com, ns2.example.com
SOA
The Start of Authority record — contains the primary nameserver, admin email, serial number and TTL defaults for the zone.
ns1.example.com. admin.example.com. 2024010101 3600 900 604800 300
When to run a DNS lookup
MX + TXT
Check MX records to see which mail servers handle your domain. Query TXT records to verify SPF, DKIM and DMARC are configured — missing or misconfigured email auth is the #1 cause of email landing in spam.
A / CNAME
After updating DNS, use the lookup to confirm the new A or CNAME records are live. Compare the TTL — a high TTL means old records may still be cached for hours.
TXT
Google Search Console, GitHub, Stripe and many other services ask you to add a TXT record to prove you own a domain. Query TXT to confirm the record was added correctly.
TXT
Query TXT records and look for v=spf1 (SPF), v=DKIM1 (DKIM at the selector subdomain) and v=DMARC1 at _dmarc.yourdomain.com. All three should be present on any sending domain.
CNAME
Follow CNAME chains to understand where traffic ultimately resolves — useful when debugging CDN configurations, load balancers and third-party integrations.
NS
Query NS records to identify which DNS provider manages a domain. Useful when you need to add records or investigate who controls DNS for a third-party domain.
Understanding TTL (Time To Live)
Every DNS record has a TTL — the number of seconds resolvers are allowed to cache it. A TTL of 3600 means caches hold the record for 1 hour before re-querying. Before making DNS changes, lower your TTL to 300 (5 min) so the change propagates faster. After propagation is confirmed, raise it back to reduce DNS query load.
Frequently asked questions
Related network & security tools
More tools to audit domains and infrastructure.
Look up DNS records now
Free account. 50 credits per day. Access to 75+ tools instantly.
Create free account →