A Record Lookup

An A record maps a domain name to an IPv4 address. Look up any domain's A records across 21 global servers to confirm the address is correct and has propagated to resolvers worldwide.

Global DNS Propagation

New York, USA Google	---
Chicago, USA Gcore	---
Los Angeles, USA Cloudflare	---
Toronto, Canada CIRA	---
Mexico City, MX OpenDNS	---
London, UK Quad9	---
Frankfurt, Germany DNS.Watch	---
Paris, France FDN	---
Amsterdam, NL OpenNIC	---
Moscow, Russia Yandex	---
Singapore Singtel	---
Tokyo, Japan IIJ	---
Mumbai, India Google India	---
Seoul, Korea KT	---
Dubai, UAE Etisalat	---
Sydney, Australia Telstra	---
Auckland, NZ Cloudflare	---
São Paulo, Brazil NIC.br	---
Buenos Aires, AR Telecom Arg	---
Johannesburg, ZA ISPA	---
Cairo, Egypt Telecom Egypt	---

DNS Map

0 0

What an A record does

An A (Address) record maps a hostname to a single IPv4 address. It is the record that turns example.com into a number like 93.184.216.34 so browsers and clients can open a connection to the right server. Almost every domain that serves a website has at least one A record.

A domain can have several A records for the same name. Resolvers hand them out in rotation, which spreads traffic across multiple servers. For the full background, read what is an A record.

How to read the results

Each row shows one of the 21 global servers and the IPv4 address it returned. In a healthy setup, every server returns the same address, or the same set of addresses. That tells you the record is consistent worldwide.

If one region returns a different or missing address after a change, that resolver is still serving a cached answer. It catches up once the record's TTL expires. A red row with no value means the server found no A record for that name, which usually points at a typo in the hostname or a record that was never published.

Common A record values

A record points at whatever hosts your site. A domain on Cloudflare shows Cloudflare proxy IPs rather than your origin. A domain on a VPS shows that server's public IP. A domain behind a CDN shows the CDN edge addresses, which can differ by region since the CDN answers with the nearest node.

Root domains usually use an A record because they cannot use a CNAME. Subdomains like www can use either an A record or a CNAME. If you are choosing between them, see A record vs CNAME.

Troubleshooting A records

If your site loads for some visitors but not others right after a change, the new A record has not reached every resolver yet. Run the lookup and watch which regions still show the old IP. A short TTL set before the change speeds this up next time.

If every server returns the old address long after the TTL should have expired, check that you edited the record at the authoritative nameservers, not at a provider you no longer use. Confirm the domain's NS records point where you think they do. A mismatch there means your edits never take effect.