DevPik Logo

DNS Lookup

Query live DNS records for any domain: A, AAAA, CNAME, MX, TXT, NS and SOA, with TTLs. Useful for verifying deploys, checking MX and SPF email records, and seeing what Google Public DNS returns right now.

Built and maintained by Muhammad Tayyab — Founder, DevPik.

Why Use DNS Lookup?

When a deploy goes sideways, the first question is usually "is DNS pointing at the new server yet?" Running `dig` from the terminal works, but you have to remember the record-type flags and parse the answer section. This lookup tool does it with one click: paste the domain, pick a record type (or just "ALL"), and see the live answer with TTLs. It's equally useful for verifying email records (MX, and the SPF line in TXT) before switching providers.

How to Use DNS Lookup

  1. Enter the domain name you want to look up (e.g., example.com).
  2. Select the DNS record type you want to query, or choose 'ALL' to see all records.
  3. Click 'Lookup' to query the DNS records.
  4. View the results organized by record type, showing values, TTLs, and other details.

Worked Examples

Verify a site has a live A record

Input
Domain: devpik.com · Type: A
Output
devpik.com  TTL 300s  104.21.71.203
devpik.com  TTL 300s  172.67.149.41

Checked 2026-11-02. Seeing an IP back confirms the domain is resolving; a blank answer means a DNS misconfiguration. Two addresses are normal for a site behind a CDN such as Cloudflare. The TTL counts down while resolvers cache the answer, so you will see any value up to the record's 300s.

Check email routing (MX) before migrating

Input
Domain: devpik.com · Type: MX
Output
Priority 4    route1.mx.cloudflare.net.  TTL 300s
Priority 34   route2.mx.cloudflare.net.  TTL 300s
Priority 100  route3.mx.cloudflare.net.  TTL 300s

Checked 2026-11-02: Cloudflare Email Routing handles this domain's email. Senders try the lowest number first (route1) and fall back to the others only if it is unreachable; equal priorities would spread mail across all three servers instead.

Inspect an SPF record (TXT)

Input
Domain: example.com · Type: TXT
Output
v=spf1 -all
_k2n1y4vw3qtb4skdx9e7dxt97qrmmq9

Checked 2026-10-23. "v=spf1 -all" says no server may send mail as example.com; the second line is a verification token. DMARC and DKIM records live on underscore names such as _dmarc.example.com, which this tool does not accept.

About DNS Lookup

DNS (Domain Name System) is the internet's address book — it translates human-readable domain names like 'example.com' into IP addresses that computers use to locate servers. The DNS Lookup tool lets you query DNS records for any domain name. DevPik's server asks Google Public DNS for A, AAAA, CNAME, MX, TXT, NS, and SOA records, helping you troubleshoot DNS issues, verify configurations, or research domain infrastructure.

Troubleshooting & Common Issues

No records returned for a domain I just configured

DNS propagation can take a few minutes to 48 hours depending on the original TTL. Check the SOA record to see the zone's minimum TTL, and try again after that time has passed. If you're impatient, query the authoritative nameservers directly (listed in the NS record) instead of a public resolver — they'll show the new record immediately.

CNAME and A record both exist for the same name

DNS doesn't allow a CNAME to coexist with any other record type on the same name. Most DNS providers will silently reject this or give precedence to one record. Remove the A record if you want a CNAME, or vice versa. The root domain (`example.com` with no prefix) especially can't have a CNAME by RFC — use an ALIAS/ANAME record your provider offers instead.

MX records look right but email is still bouncing

MX records only say which servers handle mail. Ensure the destination servers are actually accepting mail for your domain (often requires a domain entry on their side), and check authentication: SPF is a TXT record on the domain itself, which this tool shows, while DKIM and DMARC are TXT records on underscore names such as _dmarc.example.com that you'll need dig or your DNS provider's dashboard for. Many bounces come from auth misconfiguration, not MX issues.

Different DNS servers return different answers

This is usually a propagation issue during a transition. This tool always queries Google Public DNS (8.8.8.8), so to compare resolvers, run dig @1.1.1.1 (Cloudflare) and dig @208.67.222.222 (OpenDNS) alongside it. If answers diverge, the change hasn't fully propagated, or one resolver is still serving cached records. Wait for TTL expiry or flush the resolver's cache.

Frequently Asked Questions

What are DNS records?

DNS records are entries in the Domain Name System that map domain names to various types of data. They are the backbone of the internet's naming system, translating human-readable domains like example.com into IP addresses and other information that computers use to route traffic.

What is an A record?

An A record maps a domain name to an IPv4 address. It's the most fundamental DNS record type and is what allows browsers to find the server hosting a website.

What is an MX record?

MX (Mail Exchange) records specify the mail servers responsible for receiving email for a domain, along with priority values. Lower priority numbers indicate higher preference.

What is a TXT record?

TXT records store arbitrary text data associated with a domain. They're commonly used for email authentication (SPF, DKIM, DMARC), domain verification, and other purposes.

Which DNS server does this tool query?

This tool queries Google's public DNS servers (8.8.8.8) via their DNS-over-HTTPS API, providing fast and reliable results from one of the world's largest DNS resolvers.

What's the difference between CNAME, ALIAS, and ANAME?

CNAME maps one hostname to another hostname at the DNS level — but can't be used on a zone apex (root domain). ALIAS and ANAME are provider-specific record types that behave like a CNAME but can be used at the apex by dynamically resolving to A records. If you need apex-level aliasing, use ALIAS/ANAME (Cloudflare, Route 53, Vercel DNS support it).

How long does DNS propagation take?

DNS changes propagate based on the record's TTL (time to live). A TTL of 3600 means resolvers cache the answer for one hour; after that they re-check. For fast cutover, lower TTLs to 300 (5 minutes) several hours before the change, then raise them back afterward.

Why does this tool show different results than `dig` on my Mac?

Your local `dig` uses your machine's configured resolver, which might be your ISP, your router, or an internal corporate DNS. This tool always queries Google DNS (8.8.8.8). If you see different answers, ask `dig @8.8.8.8 domain.com` to force the same resolver.

Guides & Further Reading

Related Tools

Was this tool helpful?