Home › Network Tools › DNS Lookup

DNS Lookup

Look up the DNS records of a host name: its IPv4 and IPv6 addresses, mail servers, text records and name servers.

When you press Look up, the name you enter is sent to Cloudflare's DNS resolver, which sees the name and your IP address. The tool sends one request for each record type you tick, all to that resolver. Nothing else is sent by this tool, and the site does not store lookups. As on every page of this site, the standard analytics load on this page too.

A host name only, for example tools4free.dev. Do not include http:// or a path.

Record types

TypeNameTTL (seconds)Value
No lookup yet.

How it works

The tool asks Cloudflare's public DNS resolver for each record type you tick, using DNS over HTTPS in JSON format. The request is a normal browser request to cloudflare-dns.com, and the answer comes back as text that this page reads. No DNS packets are sent from your computer, and the lookup goes through the resolver rather than your own network settings.

The host name is checked before anything is sent. Only ASCII letters, digits, hyphens and dots are accepted, each part between dots is 1 to 63 characters, and the whole name is at most 253 characters. A single trailing dot is allowed. Names with international characters must be entered in their punycode form, which starts with xn--.

The result shows what the resolver reported. A status of NXDOMAIN means the name does not exist. A status of SERVFAIL means the resolver could not answer. "No records of this type" means the name exists but has no record of that type. A request that takes longer than 10 seconds is stopped and reported as a timeout.

The list covers the common standard record types. There is no single query that returns every type: the resolver does not answer ANY queries, so each type is asked for separately. For a type that is not in the list, enter its number in the other-type box (any number from 1 to 65535). Records that the tool cannot name are shown with their number.

The results reflect the resolver's cache, so a record you changed recently may show its old value until the TTL (time to live, in seconds) runs out.