Lookup Domain
Looking up DNS records...
Check DNS records for any domain — A, AAAA, MX, NS, TXT, CNAME, SOA
Looking up DNS records...
DNS (Domain Name System) is often called the phonebook of the internet. When you type a domain name like google.com, your computer queries DNS servers to find the corresponding IP address. This tool performs those queries and displays all available DNS records for a domain.
DNS lookups are essential for verifying domain configuration, troubleshooting email delivery issues, checking DNS propagation after making changes, and auditing a domain's DNS setup for security purposes.
| Type | What it holds | Typical value | Common TTL |
|---|---|---|---|
| A | IPv4 address for the name | 203.0.113.10 | 3600 |
| AAAA | IPv6 address | 2001:db8::1 | 3600 |
| CNAME | An alias pointing at another name | shop.example.com → myshop.myshopify.com | 3600 |
| MX | Mail servers, with a preference number — lower wins | 1 aspmx.l.google.com | 3600 |
| TXT | Free text: SPF, DKIM, DMARC and platform verification | v=spf1 include:_spf.google.com ~all | 3600 |
| NS | The authoritative name servers for the zone | ns1.example-dns.com | 86400 |
| SOA | Zone metadata: primary server, serial, refresh timers | one per zone | 86400 |
| CAA | Which certificate authorities may issue for this name | 0 issue "letsencrypt.org" | 3600 |
| SRV | Service location: port and host for a named service | _sip._tcp | 3600 |
| PTR | Reverse lookup, IP back to a name | lives in the provider’s zone, not yours | 86400 |
| You changed | Governed by | Realistic wait |
|---|---|---|
| An A, AAAA or CNAME record | The old record’s TTL | 5 minutes to 1 hour |
| An MX record | The old TTL. Mail retries, so little is lost. | Minutes to hours |
| A TXT record | The old TTL | Minutes |
| The name servers themselves | The TLD zone TTL, often 24 to 48 hours | 1 to 24 hours |
| A brand new domain’s first delegation | Registry zone publication | Minutes to a few hours |
You are moving example.com from an old server to a new one on Wednesday at 10:00.
Monday 10:00 — drop the A record TTL from 3600 to 300. Resolvers holding the old 3600-second copy need up to an hour to see the shorter one, so do this early.
Wednesday 10:00 — change the A record to the new IP.
Wednesday 10:05 — verify from a resolver you have not queried before.
Wednesday 11:00 — raise the TTL back to 3600.
Worst-case visitor delay is 5 minutes instead of an hour, and only the new TTL is left in place afterwards.
v=spf1. Exactly one. Two SPF records is a permanent error and mail providers will treat the domain as unauthenticated.<selector>._domainkey. You need the selector name from your mail provider to find it._dmarc, beginning v=DMARC1. p=none only monitors; p=quarantine and p=reject actually enforce.Because every recursive resolver caches independently with its own expiry clock. Someone whose resolver fetched the record a minute before your change waits the full TTL; someone with nothing cached sees the new value immediately. It is not a gradual rollout, it is many separate caches expiring at different moments.
It fixes your machine only. ipconfig /flushdns on Windows or dscacheutil -flushcache on macOS clears the local stub cache, but the recursive resolver upstream still holds its own copy until the TTL expires.
Because a CNAME must be the only record for that name, and the root of a zone has to carry SOA and NS records. Providers work around it with ALIAS, ANAME or CNAME flattening, which resolve the target and answer with an A record instead.
3600 seconds is a sensible default. Drop to 300 for the window around a planned migration and raise it back afterwards. A permanently low TTL means more queries, slower first page loads, and no cached fallback if your DNS provider has an outage.
Check SPF, DKIM and DMARC before touching MX again. MX controls where inbound mail is delivered; the TXT records control whether your outbound mail is accepted. A bounce that mentions authentication, alignment or policy is a TXT problem, not an MX one.
Lookups on this page query public registry and DNS data. Nothing about the domain you type is stored, and the domain owner is not notified.
Go deeper
The calculator gives you the number. These SnoopTool guides explain the method, the assumptions and the decision — with worked examples, data tables and FAQs.
Browse all SnoopTool guides →Questions this lookup answers in full, with the reference tables.
For teams, not just visitors
We build WHOIS, RDAP, DNS, SSL and IP lookups as embeddable widgets or a plain JSON API in your branding, wired to your own lead form — the same checks, your colours, your domain, your leads. Tell us what you need and we will send back a working demo.
Thanks — we have it, and you will get a reply from a person within one business day. Meanwhile every tool on SnoopTool stays free, with no signup.