DNS Lookup

5 of 1 ratings

Instantly inspect DNS records online to verify configuration, troubleshoot outages, and confirm changes have propagated. This DNS lookup tool lets you query common and advanced record types—A, AAAA, CNAME, MX, TXT (SPF, DKIM, DMARC), NS, SOA, CAA, PTR—and see TTLs, target hosts, and nameservers in real time. Use it to check DNS records online, validate email authentication, compare answers from multiple resolvers, and spot misconfigurations before they impact users.

If you’re wondering “why isn’t my site loading?” or “did my new MX record go live yet?”, a quick online DNS lookup is the fastest way to find out. It’s like running dig or nslookup—but from your browser, no command line needed.

What is a DNS Lookup?

A DNS (Domain Name System) lookup is the process of asking the DNS infrastructure for information about a domain—such as the server IP (A/AAAA), the mail exchangers (MX), or ownership/verification data (TXT). Our DNS record checker queries authoritative sources and/or popular public resolvers to return accurate, cache-aware results with TTLs and target values so you can make informed changes.

When should you use this DNS Lookup tool?

Website not resolving: Confirm A/AAAA records and TTLs after a server or CDN change.
Email deliverability: Check MX, SPF (TXT), DKIM (TXT), and DMARC (TXT) for correctness.
Subdomain routing: Verify CNAME chains for apps, shops, or landing pages.
Security & compliance: Validate CAA (allowed CAs) and DNSSEC-related flags (where applicable).
Nameserver changes: Ensure NS and SOA are updated and consistent across zones.
Reverse DNS: Look up PTR records for IPs used in outbound email or services.
Propagation checks: Re-query after TTL expiry to confirm that updates are live.

How to use the tool (step-by-step)

Enter a domain or subdomain (e.g., example.com or mail.example.com).
Select a record type (A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, PTR). If unsure, start with ANY or the most relevant type.
Optionally choose a resolver (e.g., Cloudflare 1.1.1.1, Google 8.8.8.8) to compare answers.
Run the lookup and review answers, TTLs, and authority. Re-run after changes to confirm propagation.

Who is this for?

Developers & DevOps verifying deployments, CDN mappings, and microservice endpoints.
Marketers & email teams validating SPF, DKIM, and DMARC for inbox placement.
IT admins & MSPs auditing nameserver health, SOA settings, and record hygiene.
Domain owners checking DNS propagation and troubleshooting downtime.

Common DNS records (quick reference)

A / AAAA

Maps a hostname to an IPv4 (A) or IPv6 (AAAA) address. Long-tail uses: “check A record online”, “find domain IP address”, “verify AAAA record for IPv6”.

CNAME

Aliases one hostname to another. Typical for www → apex, app subdomains, or third-party tools. Long-tail: “how to check CNAME record online”, “CNAME chain tester”.

MX

Mail exchanger entries that route email. Ensure priorities and targets are correct. Long-tail: “MX lookup tool for email”, “check mail server DNS records”.

TXT (SPF, DKIM, DMARC)

Free-form data used for verification and email authentication.

SPF: Sender Policy Framework, e.g., v=spf1 include:mailprovider.com -all
DKIM: Public key published at selector._domainkey.example.com
DMARC: Policy at _dmarc.example.com (e.g., v=DMARC1; p=quarantine;)

Long-tail: “check TXT SPF record online”, “verify DKIM selector record”, “DMARC DNS lookup tool”.

NS & SOA

NS defines authoritative nameservers for the zone; SOA includes the primary nameserver, admin email, and timing values (refresh, retry, expire, minimum). Long-tail: “check nameserver records”, “SOA record lookup online”.

CAA

Restricts which Certificate Authorities can issue TLS certificates for your domain. Long-tail: “CAA record checker”, “how to verify CAA DNS”.

PTR (Reverse DNS)

Maps IP addresses back to hostnames—important for mail server reputation. Long-tail: “reverse DNS lookup online”, “PTR record checker for email”.

Good practices for accurate results

Mind the TTL: If TTL is 3600s, allow up to an hour after a change before expecting global updates.
Query multiple resolvers: Compare 1.1.1.1 vs 8.8.8.8 to spot cached/geo differences.
Check the apex and subdomains: example.com may differ from www.example.com.
Validate email trio: SPF + DKIM + DMARC must all align for best deliverability.
Watch for CNAME loops & mixed records: Avoid setting A/AAAA on a hostname that is also a CNAME.

Examples

# A record example.com → 93.184.216.34 (TTL 3600)
MX records

10 mail1.example.com
20 mail2.example.com

SPF (TXT)

v=spf1 include:_spf.examplemail.com -all

DKIM (TXT at selector._domainkey.example.com)

v=DKIM1; k=rsa; p=MIIBIjANBgkqh...

DMARC (TXT at _dmarc.example.com)

v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@example.com; adkim=s; aspf=s

FAQ

How long does DNS propagation take?

It depends on TTLs and resolver caches. Many updates are visible within minutes, but allow the full TTL (and sometimes up to 24–48 hours) for global consistency.

Why do different resolvers show different answers?

Resolvers cache independently and may serve geo-optimized answers. Querying multiple resolvers helps reveal differences during propagation or CDN steering.

What if my lookup shows no record?

Check that you queried the correct hostname, record type, and zone. For new domains, verify nameserver delegation (NS/SOA) is correct at the registrar.