A record lookup

What the A record lookup shows

An A record lookup shows the IPv4 address or addresses published for a name, each with its TTL. The query goes straight to Cloudflare's 1.1.1.1 from the IPVIEW server, UDP and then TCP if clipped, so the page shows what a public resolver answers rather than what your local network returns. If the name sits behind several servers every address is listed; resolvers rotate the order, so the order on the page means nothing.

If the name is an alias, the resolver follows the CNAME and the rows carry the target's name, which may not be the one you typed; the records followed on the way are shown under Along the way so the substitution is visible. A single label such as com is accepted.

How to read the result

The table has Name, Value and TTL. The TTL is seconds the record may be cached; this page shows the time left on 1.1.1.1's cached copy, which can be lower than the TTL set in the zone; the Full report asks the zone's own nameservers and grades their TTL (under 60 very short, under 300 short, up to a day normal, longer very long). A long TTL means a wrong address stays live that long after you correct it. Under an empty answer the authority section shows the zone's SOA and how many seconds resolvers keep the negative answer, which is why a record created a minute ago still reads as none.

Three different empty answers. No A record means the zone exists and has no IPv4 address at that name, normal for a name with only a CNAME or MX. The name does not exist at all is NXDOMAIN. The query failed means no answer could be had and nothing about the zone follows. From inside Iran, an address in 10.0.0.0/8 for a public name is a forged answer; the Reachability check reads it as a sign of filtering.

When it is useful

After pointing a domain at a new server, to see whether the public answer has changed and how long the old one may linger. If this tool shows the new address and your browser still reaches the old server, your device or ISP holds a cached copy; DNS propagation shows which resolvers still disagree.

When a site loads for some people and not others, several A records with one dead address is a common cause. Take each address to Ping or Check one port on 443 and the dead one shows itself. For the IPv6 side, the AAAA record tool is next door.

Common questions

What is an A record?

The record that maps a name to an IPv4 address. A browser resolves it before it can connect; a name can have several, and clients pick among them.

Why does the lookup show a different name from the one I typed?

The name is a CNAME, an alias, and the resolver followed it. The A records belong to the target, so the Name column shows it; the alias is listed under Along the way.

Why is my new A record not showing?

Resolvers keep the old record until its TTL runs out and a negative answer for as long as the SOA minimum says; both numbers are on the page. If the SOA serial did not go up, the zone was not reloaded.