Free tool
Find the IPv4 addresses a domain points to. Real-time resolution via Google and Cloudflare DNS.
Enter a domain to look up its A records.
An A (Address) record is the most fundamental DNS record: it maps a hostname to an IPv4 address. When someone visits your domain, their resolver reads the A record to find the server that should answer.
A domain can have multiple A records for redundancy or load distribution. This tool queries public resolvers and shows every IPv4 address the hostname currently resolves to.
In a zone file, an A record is a name, a time to live (TTL) in seconds, the class IN, the record type and a single IPv4 address:
example.com. 3600 IN A 192.0.2.10
example.com. 3600 IN A 192.0.2.11
www.example.com. 3600 IN A 192.0.2.10
Each record holds one address, so a name served by two machines has two A records, as example.com does here. The TTL tells resolvers how long they may cache the answer: 3600 seconds is one hour. The bare domain (written as @ in most DNS panels) and www are separate names, so each needs its own record, unless www is set up as a CNAME pointing at the bare domain.
An A record can only hold an IPv4 address. IPv6 addresses go in an AAAA record, and one hostname can have both.
The tool asks Google Public DNS (8.8.8.8), with Cloudflare (1.1.1.1) as the fallback, from the PulseStack™ server in the UK. Each IPv4 address that comes back gets its own row, and the bar above the list shows the number of records and the query time in milliseconds. Nothing is stored.
If the name you enter is a CNAME, the resolver follows the alias and you see the addresses at the end of the chain. To see the alias itself, use the CNAME lookup.
No A records found means the resolver returned no IPv4 address for that exact name. The name may not exist, may be misspelt, or may only have an IPv6 address. Remember that www.example.com and example.com are looked up separately.
Sites behind a content delivery network often hand out different addresses depending on where the question comes from, so what you see here can differ from what a visitor in another country gets. That is expected, not an error.
The old address still appears after a move. Resolvers keep the previous answer until its TTL runs out. Lowering the TTL to 300 seconds a day before a planned migration shortens the wait, and the DNS propagation checker shows which public resolvers already return the new address.
The bare domain and www disagree. One was updated and the other was forgotten, so some links reach the old server. Look up both names.
A leftover address. An extra A record for a server you have switched off means some visitors are sent to it in turn and see the site fail at random. Remove every address you no longer use.
A private address in public DNS. An A record pointing at 10.x.x.x, 172.16.x.x to 172.31.x.x or 192.168.x.x cannot be reached from the internet. It usually means an internal record was added to the public zone by mistake.
Edits that never take effect. If the domain's nameservers point to a different provider, changes made in your registrar's panel do nothing. The nameserver lookup shows who is really in charge of the zone.
On macOS or Linux, dig A example.com +short prints just the addresses. On Windows, macOS or Linux, nslookup -type=A example.com 8.8.8.8 asks the resolver named at the end. In PowerShell, use Resolve-DnsName -Name example.com -Type A.
To skip every cache and ask the domain's own nameserver, name it in the query: dig A example.com @ns1.example.net, using one of the servers the nameserver lookup returns. If that answer is right but public resolvers still show the old one, you are waiting on caches, not looking at a mistake.
A lookup is a snapshot. To be told when the address changes, a PulseStack™ DNS record monitor on a paid plan checks the A record as often as every five minutes and alerts you when no record contains the address you expect. For every record type at once, try the DNS lookup.
An A record points a domain or subdomain to an IPv4 address, telling browsers and other clients which server to connect to. It is the record that makes example.com resolve to a specific server.
Yes. Multiple A records are common for redundancy and simple round-robin load balancing. Resolvers may return them in a rotating order so traffic is spread across servers.
DNS answers are cached at many levels. If you recently changed a record, some resolvers may still serve the old value until its TTL expires, and sites behind a CDN can return different addresses in different places. This tool asks Google Public DNS (8.8.8.8), with Cloudflare (1.1.1.1) as the fallback, from our server in the UK.
No. An A record holds exactly one IPv4 address. To point a name at another hostname, use a CNAME record, or the ALIAS or ANAME style record some DNS providers offer for the bare domain, where a CNAME is not allowed.
Every one runs a real check, live, with nothing to install.
PulseStack™ DNS record monitors check A, AAAA, MX, CNAME, TXT and NS records as often as every five minutes and alert you when the value you expect disappears. Included from the Starter plan at £9 a month, with a 14-day trial and no card.