Hostname to IP lookup
Resolve a domain name to the IPv4 and IPv6 addresses returned by DNS.
Quick answer
A hostname resolver translates a public name into the IPv4 and IPv6 destinations returned through DNS. The useful outputs are A records for IPv4 and AAAA records for IPv6. A hostname can publish several addresses for resilience or traffic distribution, and it can return no address in one family while working normally in the other.
Resolve a hostname before testing the service behind it
Choose this page when the input is a hostname and the immediate need is its IPv4 and IPv6 destination set. It is intentionally narrower than the full DNS record reader. The answer helps distinguish name-resolution trouble from a later routing, certificate, server, or application failure.
Compare address families
Keep A and AAAA results separate so an IPv6-only failure is not hidden by a successful IPv4 connection.
Check a CDN-backed name
Expect multiple or region-dependent addresses and record the resolver and observation time before comparing another network.
Confirm a deployment target
Verify the exact production hostname rather than assuming the root domain and www label are configured identically.
Follow the result into the next relevant page
Read full DNS record lookup because it adds CNAME, MX, NS, and TXT context; Read TLS certificate checker because it verifies the certificate served for the hostname; Read DNS field guide because it explains caching and why correct answers can differ.
How to interpret the output
Several correct answers may exist at once. Content delivery networks commonly tailor responses by resolver location, network, load, or health. Cached records can outlive a configuration change until their TTL ends. The first address printed by a resolver is not necessarily the only destination or the one every client will choose.
A reliable checking workflow
Enter the precise hostname used by the application, including its subdomain. Compare A and AAAA responses, repeat through the resolver used by the affected device, and test the authoritative nameserver when diagnosing a recent change. If only IPv6 or only IPv4 fails, keep the two connection paths separate during troubleshooting.
Key ideas behind hostname to ip lookup
A hostname can lead to one address, many addresses, or only one IP family. The result tells a client where it may connect; it does not prove that the application at that destination is healthy.
IPv4 path
An A record supplies an IPv4 destination.
IPv6 path
An AAAA record supplies an IPv6 destination and can succeed or fail separately.
Several answers
CDNs and load balancers may return multiple valid destinations based on place, load, or health.
Example: IPv4 works while IPv6 fails
A hostname returns both an A and an AAAA record. One device reaches the A address, but another prefers the AAAA address and stalls. That comparison points toward the IPv6 path, firewall, or service listener. Removing unrelated DNS records would hide the useful distinction rather than solve it.
The boundary that matters
Resolution proves that DNS supplied an address, not that a web server is healthy, a certificate is valid, or a route is reachable. An absent AAAA record is not automatically a fault. Likewise, resolving to a cloud or CDN address does not identify the organization that owns the site’s content.
How the main entities relate
| Subject | Relationship | Object |
|---|---|---|
| Hostname | resolves through A to | an IPv4 destination |
| Hostname | resolves through AAAA to | an IPv6 destination |
| Client | selects among | reachable returned addresses |