Free DNS Lookup Tool
Enter any domain name and this tool queries its DNS records in real time – A, AAAA, MX, NS, CNAME, TXT, and SOA. Whether you’re troubleshooting email delivery, verifying a website migration, or just curious about how a domain is configured, the results are displayed in seconds.
How to Use This Tool
Using the DNS Lookup tool takes a few seconds:
- Enter a domain name in the search field – for example,
example.com. You can paste a full URL and the tool will automatically strip the protocol and path. - Click “Lookup” to query the domain’s DNS records. The tool performs seven separate DNS queries (A, AAAA, MX, NS, CNAME, TXT, SOA) and returns all results at once.
- Review the results organized by record type. Each record shows the hostname, value, and TTL (time to live) in seconds. You can copy individual records or export the full set.
Understanding Your Results
Each DNS record type serves a different purpose. Here’s what they mean:
| Record Type | What It Does | Example Value |
|---|---|---|
| A | Maps the domain to an IPv4 address. This is how browsers find the server hosting the website. | 93.184.216.34 |
| AAAA | Maps the domain to an IPv6 address. The modern equivalent of an A record for IPv6-enabled networks. | 2606:2800:220:1:248:1893:25c8:1946 |
| MX | Mail exchange records. Points to the servers that handle email for the domain. The priority number (lower = higher priority) determines which server receives mail first. | 10 mail.example.com |
| NS | Nameserver records. Lists the authoritative DNS servers responsible for the domain’s DNS zone. | ns1.example.com |
| CNAME | Canonical name – an alias pointing one domain to another. Common for subdomains like www or CDN configurations. |
www.example.com -> example.com |
| TXT | Text records used for verification and security policies, including SPF (email authentication), DKIM signatures, and domain ownership verification for services like Google Search Console. | v=spf1 include:_spf.google.com ~all |
| SOA | Start of Authority. Contains the primary nameserver, admin contact, serial number, and timing values that control how DNS updates propagate. | ns1.example.com admin.example.com 2024010101 |
The TTL (time to live) value shown alongside each record tells you how long (in seconds) DNS resolvers are allowed to cache that record before checking for updates. A TTL of 3,600 means the record is cached for one hour. Lower TTLs mean changes propagate faster but generate more DNS queries.
Why This Matters
DNS is the address book of the internet. Every time someone visits a website, sends an email, or connects to an online service, DNS translates human-readable domain names into the IP addresses that computers use to communicate. When DNS records are wrong, things break – websites don’t load, emails bounce, and SSL certificates fail validation.
Common reasons to look up DNS records:
- Email deliverability problems. If emails are landing in spam or bouncing, check the MX records (are they pointing to the right mail server?) and TXT records (is SPF configured correctly?).
- Website migration. After switching hosting providers, verify that A records point to the new server’s IP and that CNAME records are updated for any subdomains.
- SSL certificate issues. Certificate authorities often require specific TXT or CNAME records for domain validation. Missing records mean the certificate won’t issue.
- Security audits. TXT records reveal which third-party services have been authorized (SPF includes, Google verification codes, Microsoft 365 records). This is useful for understanding a domain’s service footprint.
Frequently Asked Questions
What does it mean if no A record is found?
If there’s no A record, the domain doesn’t resolve to an IPv4 address directly. This can mean the domain uses only a CNAME record (which points to another domain that has the A record), the domain is configured for IPv6 only (check the AAAA record), or the domain’s DNS isn’t set up yet. It can also indicate the domain is parked or expired.
Why are there multiple MX records with different priority numbers?
Multiple MX records provide redundancy for email delivery. The priority number (sometimes called preference) determines the order – mail servers try the lowest number first. If that server is unavailable, they move to the next priority. For example, priority 10 is tried before priority 20. Most organizations configure at least two MX records so email still works if one mail server goes down.
What is a TTL and should I change mine?
TTL (time to live) controls how long DNS resolvers cache a record before re-querying the authoritative nameserver. A typical TTL is 3,600 seconds (1 hour) or 86,400 seconds (24 hours). Lower TTLs are useful before planned changes – set it to 300 seconds (5 minutes) a day before a migration so the switch happens quickly. Higher TTLs reduce DNS lookup overhead for stable records. There’s no single right answer, but 3,600 seconds is a sensible default for most records.
Can I look up DNS records for any domain?
Yes. DNS records are public information by design – that’s how the internet works. Any device connecting to a domain needs to resolve its DNS records, so they’re freely queryable. This tool uses PHP’s dns_get_record() function to query the records from the server side, meaning it reflects what our server sees (which may differ from your local DNS resolver if records have recently changed and caches haven’t expired).
How this tool works
This tool runs entirely in your browser and our server. We detect your IP address server-side, then perform DNS and WebRTC checks client-side. No account is needed and no personal data is stored beyond anonymous aggregate statistics.
Results are based on real-time checks against your current connection. For the most accurate results, ensure your VPN is fully connected before running the test.
The Fourteen Eyes intelligence alliance includes 14 countries that share signals intelligence, including internet communications data.