A Lookup
Resolve a hostname to its IPv4 address.
Enter a value above to run A Lookup
e.g. example.com
Quick answer
An A lookup returns the IPv4 address a hostname points to. This is the address browsers and clients connect to when they reach the domain.
An A record is the DNS entry that maps a hostname like example.com to a single IPv4 address such as 93.184.216.34. This A Lookup tool queries the DNS system and returns the IPv4 addresses currently published for the name you enter, exactly as a browser or mail server would resolve them.
It is the fastest way to confirm where a domain actually points. Whether you just changed hosting, set up a new subdomain, or a site is unreachable, checking the A record tells you the address visitors are being sent to right now.
How it works
When you submit a hostname, the tool asks a DNS resolver for that name's A records. The query walks from the root servers to the domain's authoritative nameservers, which return one or more IPv4 addresses along with a TTL (time to live). The TTL, in seconds, tells resolvers how long they may cache the answer before asking again. A single hostname can return several A records, and DNS may rotate their order for basic load distribution.
How to read the results
Each line is one IPv4 address the hostname resolves to. If you see multiple addresses, the service runs on more than one server or behind a CDN. Compare the returned IP against your hosting provider's expected address to confirm the record is correct. An empty result means no A record exists for that exact name, often because the entry is only on www, or it uses AAAA (IPv6) or a CNAME instead.
Common problems & fixes
If a lookup still shows an old IP after you changed it, the previous value is cached until its TTL expires, so lower the TTL before planned migrations. Getting no result for the bare domain but a valid one for www usually means the apex A record is missing. A NXDOMAIN response means the name does not exist at all, typically a typo or a domain that was never registered or has lapsed.
Frequently asked questions
- What is the difference between an A record and a CNAME?
- An A record points a hostname directly to an IPv4 address. A CNAME points one hostname to another hostname, which is then resolved to find the final A record. Use an A record when you have a fixed IP, and a CNAME to alias a subdomain to something like a load balancer or CDN endpoint that manages the underlying IP for you.
- Why does one hostname return several IP addresses?
- Publishing multiple A records is a common way to spread traffic across several servers or data centers. Resolvers typically hand out the addresses in rotating order, so different clients connect to different IPs. Content delivery networks rely on this heavily, often returning the address geographically closest to the person making the request.
- How long until a new A record takes effect?
- It depends on the TTL that was set on the record before you changed it. Resolvers cache the old answer for the full TTL, so a value of 3600 means up to an hour of stale results somewhere on the internet. Lower the TTL a day ahead of a change, make the edit, then raise it again once the new address is confirmed.