Skip to content
Search

Search this site

DNS Lookup

This tool asks Cloudflare's public DNS resolver (1.1.1.1) for a record of a chosen type and explains each answer: the record value, its TTL, the response code and what the record is for. It shows one resolver's view, which may be cached, so it is not a propagation check. Your browser sends the query straight to cloudflare-dns.com; this site never sees it.

Look up DNS records

Enter a host name and choose a record type. For an IP address, choose PTR. Results come from Cloudflare's public resolver and may be cached.

Lookup

Example: example.com, www.example.com or _dmarc.example.com.

Result

General information about domain names, not legal, trademark or financial advice. Registrar and registry rules and fees change; confirm with your registrar before you pay or transfer. Shows what Cloudflare's public resolver (1.1.1.1) returns, which may be cached. Your query goes from your browser to cloudflare-dns.com; this site does not receive or store it, and the tool uses no cookies, local storage or analytics events.

How the lookup works

The tool builds one request to Cloudflare's DNS JSON API and reads the answer. For an IP address with the PTR type it first builds the reverse name: IPv4 octets in reverse order under in-addr.arpa (RFC 1035) or the 32 hexadecimal digits of an IPv6 address in reverse order under ip6.arpa (RFC 3596).

Request and response
GET https://cloudflare-dns.com/dns-query?name=<name>&type=<type>
Accept: application/dns-json
  -> { Status, AD, Answer[ {name, type, TTL, data} ], Authority[] }
PTR for 192.0.2.7 -> name = 7.2.0.192.in-addr.arpa
Status
the DNS response code (0 NOERROR, 2 SERVFAIL, 3 NXDOMAIN, and so on)
AD
the resolver validated the answer with DNSSEC
TTL
seconds the answer may be cached

Worked example: MX records for gmail.com

Given: name gmail.com, type MX; a stored response in this page (captured 2026-11-17).

  1. The response code is read: 0 = NOERROR
  2. The answers are sorted by preference, lowest first: 5 gmail-smtp-in.l.google.com.; 10 alt1.gmail-smtp-in.l.google.com.; 20 alt2.gmail-smtp-in.l.google.com.; 30 alt3.gmail-smtp-in.l.google.com.; 40 alt4.gmail-smtp-in.l.google.com.
  3. The TTL of the first answer is converted to words: 3405 s = 56 min 45 s

Answer: Mail for the domain is delivered to the host with preference 5 first; the others are tried only if the first cannot be reached. Your result will differ whenever the owner changes the records.

Record types the tool can look up

DNS record types and what their data means
TypeNumberWhat it isHow to read it
A 1An IPv4 address for the name.Each A record holds one IPv4 address (four numbers, 0 to 255). Several A records on the same name are normal. (RFC 1035)
AAAA 28An IPv6 address for the name.Same role as an A record, but the value is an IPv6 address (eight groups of hexadecimal digits, often shortened with ::). (RFC 3596)
CNAME 5An alias: this name is another name for a canonical name.Resolvers restart the lookup at the target name. A name that has a CNAME should have no other record types (RFC 2181 section 10.1), which is why a CNAME is not used at the zone apex. (RFC 1034, RFC 2181)
MX 15The mail exchanger: a host that accepts email for the domain, with a preference number.The number first in each answer is the preference; a lower number is tried first. The target is a host name, not an IP address. (RFC 1035)
TXT 16Free-form text attached to the name.A TXT record holds one or more character strings of up to 255 bytes each; a longer value is split into several strings that readers join together. Common uses are domain-verification tokens and policy text such as SPF. (RFC 1035)
NS 2An authoritative name server for the zone.NS records name the servers that hold the zone's official records. The parent zone (for example .com) publishes the delegation; the zone itself also lists its NS records. (RFC 1035)
SOA 6Start of authority: administrative details for the zone.The data has seven fields in order: primary name server (MNAME), responsible mailbox (RNAME, with the first dot standing for @), serial, refresh, retry, expire and minimum (the last four in seconds). (RFC 1035)
CAA 257Which certification authorities may issue certificates for the name.The data is flags, a tag and a value, for example 0 issue "ca.example". The tag issue names a permitted issuer, issuewild applies to wildcard names, and iodef gives a place to report violations. (RFC 8659)
SRV 33The host and port of a service, with priority and weight.The name has the form _service._protocol.name. The data is priority, weight, port and target host. (RFC 2782)
PTR 12A pointer from an address back to a name (reverse DNS).IPv4 reverse names are the address octets in reverse order under in-addr.arpa (RFC 1035); IPv6 names are the 32 hexadecimal digits in reverse order under ip6.arpa (RFC 3596). (RFC 1035)

Type numbers: IANA, Domain Name System (DNS) Parameters (last updated 2026-11-09), read 2026-11-17.

Response codes

DNS response codes shown by the tool
CodeNameMeaning
0 NOERRORThe query succeeded. If the answer list is empty, the name exists but has no record of the type you asked for (NODATA).
1 FORMERRThe query was malformed.
2 SERVFAILThe name server was unable to process the query because of a problem with the name server (RFC 1035).
3 NXDOMAINThe name does not exist.
4 NOTIMPThe server does not support the requested operation.
5 REFUSEDThe server declined to answer the query.

IANA, DNS Parameters (RCODEs); RFC 1035 section 4.1.1, read 2026-11-17.

What a lookup cannot tell you

  • Whether a change has propagated. One resolver's cache is one data point; this is not a propagation check.
  • That a record is "live" at your registrar or DNS provider, or that a missing record was never configured.
  • That DNSSEC is valid for the whole chain. The AD flag reports only that this resolver validated the answer.
  • Anything about web hosting or email deliverability. The tool shows records; it does not judge whether a mail or web service works.

Frequently asked questions

Is this a DNS propagation checker?

No. It queries a single public resolver, Cloudflare's, and that resolver may return a cached answer. A different resolver, or your authoritative name server, can show a different value until the old answer's TTL runs out. Use the NS and SOA results to see which servers hold the zone, and compare against those.

Why does it say no record when I know I added one?

The record may not have reached the authoritative servers yet, may be on a different name (for example www instead of the bare domain), may be a different type, or an earlier "no record" answer may still be cached. An empty answer does not prove the record was never configured.

What do the A, AAAA and CNAME records do?

An A record gives an IPv4 address and an AAAA record an IPv6 address for a name. A CNAME says the name is an alias for another name, and the resolver then looks up that target. The tool explains whichever type you pick next to its answer.

Why are TXT values joined?

A TXT record holds strings of up to 255 bytes. Longer values, such as long verification or policy text, are split into several strings that readers join together. The tool joins them and notes how many strings there were.

Can I look up an IP address?

Yes, with the PTR type. The tool turns the address into its reverse name (in-addr.arpa for IPv4, ip6.arpa for IPv6) and asks for the PTR record. Many addresses have no PTR record, or one that does not match the name you expect.

Does this site store my lookups?

No. The query goes from your browser to cloudflare-dns.com. The tool uses no cookies, local storage or analytics events, and there is no server of ours in between.

Sources and further reading

  1. Cloudflare: DNS JSON format (1.1.1.1 documentation) (developers.cloudflare.com) Opened 2026-11-17. Cloudflare notes the format has no formal RFC and may change.
  2. RFC 1035: Domain names, implementation and specification (rfc-editor.org) Record formats, TTL and response codes.
  3. IANA: Domain Name System (DNS) Parameters (RCODEs and record type numbers) (iana.org) Opened 2026-11-17; page last updated 2026-11-09.
  4. RFC 3596: DNS Extensions to Support IP Version 6 (AAAA and ip6.arpa) (rfc-editor.org)
  5. RFC 2181: Clarifications to the DNS Specification (CNAME rules) (rfc-editor.org)
  6. RFC 8659: DNS Certification Authority Authorization (CAA) Resource Record (rfc-editor.org) Opened 2026-11-17.
  7. RFC 2782: A DNS RR for specifying the location of services (SRV) (rfc-editor.org)
  8. RFC 8499: DNS Terminology (NODATA, response codes) (rfc-editor.org) Opened 2026-11-17.

You might also like