System Tools
Verified Tool

DNS Lookup

Query DNS records for any domain

Start Using DNS Lookup Now
Free Forever No Signup
Last Updated: March 2, 2026
avatarBy Viblaa Team

A/AAAA records

MX records

TXT records

NS records

CNAME lookup

SOA records

TTL display

You launch your new domain. Email stops working. The website shows someone else's site. Your DNS propagation has been "pending" for 48 hours. And you're not even sure what DNS records you currently have.

DNS is the internet's phone book—translating human-readable domains into IP addresses and routing email to the right servers. When DNS is wrong, nothing works. When it's right, you never think about it.

This lookup tool shows exactly what DNS records exist for any domain, so you can verify configurations, troubleshoot failures, and understand how your domain routes traffic.

What is DNS Lookup?

DNS (Domain Name System) lookup queries authoritative nameservers to retrieve DNS records for a domain. These records control how your domain routes web traffic (A records), email (MX records), verification (TXT records), and more.

Common record types:

A       →  IPv4 address (93.184.216.34)
AAAA    →  IPv6 address
MX      →  Mail server addresses
TXT     →  Text data (SPF, DKIM, verification)
CNAME   →  Alias to another domain
NS      →  Authoritative nameservers
DNS Has Multiple Layers

When you query DNS, you might hit cached results from your ISP. For authoritative records, query the domain's nameservers directly. This tool shows what the authoritative servers return.

Why People Actually Need This Tool

DNS Problems Masquerade as Everything Else

Website down? Could be DNS. Email not delivering? Probably DNS. SSL certificate won't issue? Check DNS first. Most "mysterious" internet problems start with DNS misconfiguration.

  1. Troubleshooting website access — Verify A/AAAA records point to the correct server IP.

  2. Email deliverability issues — Check MX records and SPF/DKIM TXT records.

  3. Domain verification — Confirm TXT records for services like Google, Microsoft, and SSL certificates.

  4. Migration planning — Document current DNS before making changes.

  5. Propagation checking — Verify DNS changes have taken effect globally.

  6. Security auditing — Review DNS configuration for potential issues.

  7. Competitor research — See what infrastructure domains are using.

How to Use DNS Lookup

  1. Enter domain name — Type the domain (e.g., example.com, not https://example.com).

  2. Select record type — Choose specific type (A, MX, TXT) or query all.

  3. View results — See all matching records with TTL values.

  4. Interpret findings — Cross-reference with expected configuration.

RecordPurposeExample Value
AIPv4 address93.184.216.34
AAAAIPv6 address2606:2800:220:1:248:1893:25c8:1946
MXMail server10 mail.example.com
TXTVerification, SPF, DKIMv=spf1 include:_spf.google.com ~all
CNAMEAliaswww.example.com → example.com
NSNameserversns1.example.com
SOAStart of AuthorityPrimary NS, admin email, serial
TTL Affects Change Speed

TTL (Time To Live) determines how long DNS records are cached. High TTL (86400 = 24 hours) means changes propagate slowly. Lower TTL before making changes, then raise it after.

Real-World Use Cases

1. The Missing Email Mystery

Context: Company switched email providers. Some messages arrive, others disappear.

Problem: No bounce messages. Email just vanishes.

Solution: DNS lookup reveals old MX records still pointing to previous provider. New provider's MX missing entirely.

Outcome: Add correct MX records, remove old ones. Email flows properly within hours.

2. The SSL Certificate Failure

Context: Let's Encrypt certificate won't issue for domain.

Problem: Error says "CAA record prevents issuance."

Solution: DNS lookup shows CAA record restricting certificates to a different CA.

Outcome: Update CAA record to include Let's Encrypt. Certificate issues immediately.

3. The Website Pointing Wrong

Context: After server migration, website shows old content.

Problem: Server has new content but visitors see old site.

Solution: DNS lookup shows A record still pointing to old server IP.

Outcome: Update A record to new IP. Site works after TTL expires.

4. The SPF Verification

Context: Marketing emails landing in spam folders.

Problem: Gmail shows "failed SPF" in email headers.

Solution: DNS lookup reveals SPF TXT record missing the email service's include statement.

Outcome: Add include:spf.mailservice.com to SPF. Deliverability improves.

5. The Subdomain Delegation

Context: Creating a subdomain for a new app, but it's not resolving.

Problem: app.example.com returns NXDOMAIN (doesn't exist).

Solution: DNS lookup on parent domain shows no A record or CNAME for app subdomain.

Outcome: Add appropriate record. Subdomain resolves within TTL.

6. The DKIM Setup Verification

Context: Setting up DKIM for email authentication.

Problem: DKIM test fails but records were supposedly added.

Solution: DNS lookup for selector._domainkey.example.com shows no TXT record found.

Outcome: Discover wrong selector name was used. Correct it. DKIM passes.

7. The Nameserver Migration

Context: Changing from one DNS host to another.

Problem: After NS record update, some users can reach site, others can't.

Solution: DNS lookup shows NS records changed, but queries still return old records from cache.

Outcome: Normal propagation delay. Full resolution within 48 hours as caches expire.

Common Mistakes and How to Avoid Them

DNS Changes Aren't Instant

TTL caching means changes can take hours to days to fully propagate. Plan accordingly—don't make DNS changes Friday afternoon before a Monday launch.

Forgetting the Trailing Dot
❌ The Mistake
Creating CNAME to `example.com` without trailing dot, which gets interpreted as `example.com.yourdomain.com`.
âś… The Fix
Use fully qualified domain names with trailing dot (`example.com.`) or check your DNS provider's interface—many handle this automatically.
SPF Record Lookup Limit
❌ The Mistake
SPF record with too many includes: `include:_spf.google.com include:spf.protection.outlook.com include:...` exceeds 10-lookup limit.
âś… The Fix
SPF allows max 10 DNS lookups. Consolidate includes or use SPF flattening services.
Wrong MX Priority
❌ The Mistake
Setting primary mail server with higher number (lower priority) than backup, so backup receives all mail.
âś… The Fix
Lower MX numbers = higher priority. Your primary server should be MX 10, backup MX 20.
CNAME at Root Domain
❌ The Mistake
Trying to set CNAME for the bare domain (example.com, not www.example.com). CNAME conflicts with other records.
âś… The Fix
Root domains must use A/AAAA records. Some providers offer ALIAS/ANAME pseudo-records that work around this.
Ignoring TTL Before Changes
❌ The Mistake
Changing DNS records without first lowering TTL. Old records cached for days.
âś… The Fix
Lower TTL to 300 seconds at least 48 hours before planned changes. Raise it again after confirming new records work.

Privacy and Data Handling

This DNS Lookup tool queries public DNS records that are intentionally published.

  • DNS records are public information by design.
  • Queries go to authoritative nameservers.
  • No personal data is collected.
  • Results are not stored or logged.

You're looking up the same records any internet user or search engine could query.

Conclusion

DNS is invisible when it works and catastrophic when it fails. Most internet problems that seem mysterious—websites unreachable, email vanishing, certificates failing—trace back to DNS misconfiguration.

This lookup tool shows exactly what records exist, right now, from authoritative sources. No guessing, no waiting, no wondering if propagation is complete. See the truth of your domain's DNS configuration instantly.

When everything else seems broken, check DNS first. This tool makes that check trivial.

Frequently Asked Questions