DNS Lookup — Query Any Domain's DNS Records in Real Time
Diagnose email delivery failures, confirm domain migrations, and audit security policies — without installing dig or nslookup.
What is a DNS Lookup?
A DNS lookup queries the Domain Name System to retrieve the records attached to a domain — functioning like a phone book for the internet, translating human-readable domain names into the technical data networks need to route traffic and deliver services. Every domain carries multiple record types: A records point to IP addresses, MX records route email, TXT records carry security policies, and NS records delegate authority to a nameserver.
When you trigger a DNS lookup, the query travels to a recursive resolver (operated by your ISP, or a public resolver like 8.8.8.8 or 1.1.1.1). If the resolver has a cached answer within the record's TTL window, it returns that cached value. If not, it queries the authoritative nameserver — the server that holds the domain's official records. This tool bypasses caching and queries authoritative servers directly, so results reflect the current published state of the zone, not what your browser has cached.
Your browser performs DNS lookups automatically in the background — but shows you nothing. This tool exposes the full record set: not just the IP address, but every record type attached to the domain, including TTL values that reveal how long each record will persist in caches before resolvers re-check the authoritative source.
How It Works
Enter a Domain
Type any domain name — such as google.com or github.com — into the input field. You can query a root domain or a subdomain.
Select a Record Type
Choose the DNS record type you want to inspect — A, MX, TXT, NS, CNAME, SOA, CAA — or select All Records to retrieve everything at once.
View the Results
Results are returned in real time from authoritative DNS servers. Each row shows the record type, value, TTL (how long the record is cached by resolvers), and — for MX records — the priority number. Copy any record to clipboard with one click.
How to Read Your DNS Lookup Results
Once a lookup completes, each result row contains several fields. Here is what each field means and what to look for.
| Field | What It Tells You |
|---|---|
TTL (Time To Live) | The number of seconds this record is cached by resolvers before they re-query the authoritative server. TTL 300 = changes propagate in ~5 minutes. TTL 86400 = the old record can persist for up to 24 hours after you change it. |
MX Priority | Only present on MX records. Lower numbers have higher priority. A setup of 10 (primary) and 20 (backup) creates a failover chain. Equal priority values mean both servers share load equally. |
Record Value | The actual data the record contains — an IP address for A/AAAA records, a hostname for MX/NS/CNAME, or a text string for TXT records. This is the value DNS resolvers use when routing traffic or verifying policies. |
CNAME Chain | When a CNAME points to another CNAME, a resolution chain forms. Chains longer than 8 hops will fail to resolve in most clients — if depth becomes a problem, replace intermediate CNAMEs with a direct A record. |
TTL and DNS Propagation Timeline
Use TTL to estimate how quickly resolvers should pick up a change and when it is worth checking again.
| TTL (Time To Live) | Expected Propagation Window | When to Re-Check |
|---|---|---|
| 300 | ~15-30 minutes worldwide | Every 5-10 minutes |
| 3600 | ~1-2 hours | Every 30-60 minutes |
| 86400 | Up to 24 hours | Check after 12 hours, then again at 24 hours |
DNS Record Types: What Each One Controls
Maps a domain to an IPv4 address — the most fundamental DNS record. Example output: 93.184.216.34, TTL 3600 (cached 1 hour). When the A record is missing or wrong, the domain becomes unreachable from browsers.
Maps a domain to an IPv6 address for modern network routing. Example: 2606:2800:220:1:248:1893:25c8:1946. If missing, IPv6-only clients cannot reach the domain — though IPv4 (A record) fallback usually applies.
Specifies which mail servers accept email for the domain. Each record includes a priority number — lower values take precedence. Example: priority 10 is the primary server; priority 20 is the fallback. If no MX record exists, email to this domain will be rejected.
Stores arbitrary text data. Primary uses: SPF (v=spf1 include:_spf.google.com ~all) authorizes which servers can send email; DKIM provides a public key for signature verification; DMARC (v=DMARC1; p=reject) sets the policy for unauthenticated email. Multiple TXT records can coexist on one domain.
Identifies the authoritative nameservers for the domain — the servers that hold the official DNS records. If NS records are changed, zone authority transfers to the new nameservers after propagation.
Creates an alias pointing one domain to another, which then resolves to an IP. Used for subdomains (www, cdn, mail) and CDN routing. Critical constraint: CNAME records cannot be set at the root (apex) domain — use an A record or ALIAS record at root instead.
Contains zone metadata: primary nameserver, admin contact (encoded as admin.example.com instead of [email protected]), serial number in YYYYMMDDNN format, and timing parameters. The serial number increments with each DNS change — confirming an update has been committed.
Restricts which Certificate Authorities may issue SSL/TLS certificates for the domain. Example: '0 issue letsencrypt.org' limits issuance to Let's Encrypt only. If no CAA record exists, any CA may issue a certificate for your domain.
What is DNSSEC and does this tool validate it?
DNSSEC (DNS Security Extensions) adds cryptographic signatures to DNS records, allowing resolvers to verify that records have not been tampered with in transit. This tool returns raw DNS records from authoritative servers but does not currently perform DNSSEC signature validation. For DNSSEC validation, use a dedicated DNSSEC analyzer.
When to Use a DNS Lookup Tool
Email Configuration & Troubleshooting
Query MX records to verify mail server routing, check TXT records for SPF, DKIM, and DMARC policies, and confirm that your DMARC policy is set to p=reject or p=quarantine — not p=none.
Domain Migration & Propagation
After updating DNS settings, check A and NS records to confirm propagation. Reduce TTL to 300 seconds at least 24 hours before a planned migration to minimize downtime when you switch.
DNS Security Audit
Check whether SPF, DKIM, and DMARC TXT records are correctly published to prevent email spoofing. Review NS records to confirm your domain is not pointing to a nameserver you no longer control — a common sign of subdomain takeover exposure.
DevOps & Staging Verification
Before deploying to production, verify that staging subdomain A records point to the correct servers, CNAME aliases resolve to the intended CDN origins, and TXT records for service verification are present.
CDN & Subdomain Configuration
Confirm that CDN-routed subdomains (cdn, assets, static) have the correct CNAME targets. Verify that www points to your root domain or CDN endpoint, and check that load-balanced subdomains list all intended IP addresses.
Online DNS Lookup vs dig and nslookup: When to Use Each
Developers often reach for dig or nslookup from the command line. Here is how this online tool compares across the most common use cases.
| Feature | This Tool | dig | nslookup |
|---|---|---|---|
| No installation required | Yes | No | No |
| Query all record types at once | Yes | Partial | No |
| Queries authoritative nameservers directly | Yes | Yes | Partial |
| Shows TTL values | Yes | Yes | Partial |
| Shows MX priority | Yes | Yes | Yes |
| Shareable results | Yes | No | No |