DNS Lookup
Look up every DNS record for a domain, or the hostname for an IP address. Queries go straight from your browser to a public DNS-over-HTTPS resolver.
Look up every DNS record for a domain, or the hostname for an IP address. Queries go straight from your browser to a public DNS-over-HTTPS resolver.
example.com), a subdomain (mail.example.com) or an IP address. Pasting a full URL works too; the hostname is extracted.Results can be shared: the address bar updates to a link such as /dns-lookup?q=example.com&type=MX that reruns the same lookup.
| Type | What it holds | When to check it |
|---|---|---|
| A | IPv4 address of the host | A site does not load, or you moved hosting |
| AAAA | IPv6 address | IPv6-only clients fail, or a CDN needs dual-stack |
| CNAME | Alias pointing to another hostname | Connecting a subdomain to Vercel, Netlify, Shopify or a CDN |
| MX | Mail servers with priority (lower = preferred) | Email is not arriving after a provider change |
| NS | Authoritative nameservers for the zone | Checking that a registrar change to Cloudflare or Route 53 has applied |
| TXT | Free text: SPF, domain verification tokens, DKIM | Google, Microsoft 365 or SES verification; SPF errors |
| SOA | Primary nameserver, admin contact, zone serial and timers | Confirming a zone update (the serial increases) |
| CAA | Which certificate authorities may issue TLS certificates | Let's Encrypt or another CA refuses to issue |
| SRV | Service host and port, e.g. _sip._tcp | VoIP, XMPP, Minecraft and Microsoft Teams setups |
| PTR | Hostname for an IP (reverse DNS) | Mail server reputation; identifying an IP in logs |
Enter an IPv4 or IPv6 address and the tool automatically runs a PTR query: 8.8.8.8 is looked up as 8.8.8.8.in-addr.arpa and returns dns.google. IPv6 addresses are expanded to 32 nibbles under ip6.arpa. Many residential and cloud IPs have no PTR record, which is normal. For mail servers, the PTR name should resolve back to the same IP (forward-confirmed reverse DNS), or many receivers will mark the mail as spam.
Choose MX to list the mail servers, TXT to find the SPF record (it starts with v=spf1), and DMARC to query _dmarc.yourdomain for the policy that starts with v=DMARC1. A typical Google Workspace domain shows MX records ending in google.com and an SPF record containing include:_spf.google.com. DKIM keys live under a selector-specific name such as selector1._domainkey.example.com; type that full name and choose TXT.
This page asks a public resolver over DNS over HTTPS (Cloudflare's 1.1.1.1 or Google's 8.8.8.8), not your operating system or router. If you just changed a record, your ISP's resolver may still be serving the cached old value until its TTL expires, while the public resolver shows the new one, or the other way round. Switch the Resolver menu to compare the two. Records on a private network (split-horizon DNS, .local or corporate names) are not visible to public resolvers. From a terminal, the equivalent commands are:
dig example.com MX +short
nslookup -type=TXT example.com
dig -x 8.8.8.8 +short
There is no global push. Each resolver keeps a cached answer until its TTL expires, so a change becomes visible within the old record's TTL, typically 5 minutes to 24 hours. Lower the TTL a day before a planned migration to make the switch faster.
The name does not exist in DNS: the domain is unregistered, expired, misspelled, or the subdomain has no records. A domain that exists but has no record of the requested type returns an empty answer instead.
Your browser sends the query directly to Cloudflare or Google over HTTPS. NeatJSON does not see or log the domains you look up.
Yes. Enter the IP and a PTR (reverse DNS) query runs automatically. You can also use IP Lookup for the owner network and location of an address.