DNS Lookup
Look up DNS records for any domain and see how that name resolves on the public internet. DNS records control website routing, email delivery, verification tokens and many security settings.
Choose ALL for an inventory view, or choose one focused record type.
Raw DNS response
Uses the MyIPScan /api/dns-lookup route backed by a free DNS-over-HTTPS resolver. Results are a limited resolver view and may differ by network or resolver cache.
Direct answer
DNS Lookup: answer first
Look up DNS records including A, AAAA, CNAME, MX, TXT, NS, CAA, and SOA. Use the result as an observable public-signal check with stated limitations, not as an absolute guarantee.
When to run a DNS lookup
DNS lookup is useful when a website does not load, email delivery fails, a domain migration is in progress, or you want to confirm which records are visible publicly. Checking A and AAAA records shows where a domain points, while MX and TXT records are commonly used for email routing and verification.
DNS changes can take time to propagate because resolvers cache records according to their TTL. If your result looks old, compare it again later or check from another resolver before assuming the domain is misconfigured.
- Use A and AAAA records to inspect website IPv4 and IPv6 targets.
- Use MX records to troubleshoot email delivery.
- Use TXT records to verify SPF, DKIM, DMARC and ownership tokens.
Complete your privacy check:
- Domain Intelligence Report — combine DNS inventory, RDAP, IP/ASN, PTR, CAA, DNSSEC, TXT, and provider hints
- Website Exposure Scanner — combine DNS, HTTPS, redirects, headers, IPv6, and mixed-content signals
- Email Deliverability Doctor — combine MX, SPF, DMARC, DKIM selector, PTR, and sender-IP signals
- Reverse DNS Lookup — check PTR records for a public IP address
- SSL Certificate Checker — review certificate issuer, expiry, and SAN signals
- DNS Leak Test — review DNS resolver exposure signals
- WebRTC Leak Test — inspect browser WebRTC address candidates
- IP Checker — see your current public IP
Learn more about DNS and privacy:
- What Is a DNS Leak and How to Prevent It — understand how DNS queries can expose your browsing
- How VPNs Use DNS — how VPN tunnel handles your DNS queries
- How to Hide Your IP Address — privacy methods including DNS-over-HTTPS
- DNS Server Differs From VPN Country — what it means when DNS and VPN locations don't match
B2B diagnostic report model
Domain intelligence diagnostics
Domain checks connect public DNS, RDAP-safe context, reverse DNS, CAA, DNSSEC hints, IP/ASN context, provider hints, and blacklist context.
Client-safe report
Share findings without leaking raw technical material
Use Safe Copy or this page's summary when sending results to a client, vendor, developer, or support team. Raw headers, credentials, tokens, cookies, private addresses, email local-parts, and oversized payloads should stay out of client-facing copy.
Check my website/domain
What this checks
Public DNS, HTTP, HTTPS, certificate, redirect, header, IP/ASN, or domain configuration signals.
Limits
What this cannot check
It cannot perform credentialed vulnerability testing, scan private hosts, bypass access controls, or certify complete security.
Read results
How to use the output
Treat results as review signals for this browser/session or public target. Re-test after one change, then use Safe Copy or notes that avoid raw identifiers.
SEO and AI citation summary
DNS Lookup: what this tool does
Looks up DNS records including A, AAAA, CNAME, MX, TXT, NS, CAA, and SOA.
How to use
- Enter one public domain, IP address, or ASN value supported by the tool.
- Review record values, TTLs, provider hints, and confidence notes before changing DNS.
- Retest after propagation and compare with the Domain Intelligence Report.
What the result means
Treat DNS, RDAP, PTR, CAA, and provider context as public registry or resolver evidence. DNS can be cached, delegated, proxied, or incomplete.
Limitations
- This tool reports observable signals only; it is not a guarantee or certification.
- Uses /api/dns-lookup backed by Cloudflare DNS over HTTPS.
- Results can change after VPN reconnects, DNS propagation, browser updates, cache changes, or provider configuration changes.
DNS Lookup — Common Questions
What DNS record types can I look up?
This tool queries A (IPv4 address), AAAA (IPv6 address), CNAME (alias), MX (mail server), TXT (SPF, DKIM, verification), NS (nameserver), CAA (certificate authority), and SOA (zone authority) records. Queries run through Cloudflare's DNS over HTTPS (1.1.1.1) for accurate, up-to-date results.
Why do DNS results differ from my local resolver?
DNS propagation takes time — when a record changes, different resolvers around the world cache the old result for up to the TTL (Time to Live) value. This tool uses Cloudflare DoH which updates quickly. If you see different results here vs your local dig or nslookup, your local resolver is probably serving a cached answer. Wait for the TTL to expire and recheck.
How do I check if my domain's DNS is configured correctly?
1. Look up the A record — it should point to your server's IP. 2. Look up the MX record — it should point to your mail provider. 3. Check TXT records for SPF (starts with "v=spf1") and DKIM (usually a subdomain like "mail._domainkey"). 4. Check DMARC by looking up "_dmarc.yourdomain.com" TXT record. Use our SPF Checker and DMARC Checker for dedicated validation.
What does a missing A record mean?
No A record means the domain cannot resolve to an IP address — the website or server is unreachable at that hostname. This can mean the DNS record was deleted, never created, or the propagation is still in progress (allow up to 48 hours for new records). If you just set up a domain, add an A record pointing to your server's IP and recheck after 15–30 minutes.
What is TTL and why does it matter?
TTL (Time to Live) is how long, in seconds, resolvers cache a DNS record. A TTL of 300 means resolvers keep the cached result for 5 minutes before re-querying. Low TTL (60–300s) is useful during migrations — changes propagate faster. High TTL (3600–86400s) reduces DNS query load but slows down updates. Before changing DNS records, lower the TTL to 300 first, wait for the old TTL to expire, then make the change.