Domain to IP

Knowing the IP behind a hostname is the first debugging step when a site is unreachable, CDN failover is misbehaving, or a new record has not propagated. This tool resolves the A and AAAA records for any domain and lists every IPv4 and IPv6 address it finds.

How to resolve a domain to IP

  1. 1

    Enter the hostname

    Root domain or subdomain: `example.com` or `api.example.com`. Schemes and paths are stripped.

  2. 2

    Read the A and AAAA records

    Every IPv4 and IPv6 address the domain answers with is listed on its own line, ready to copy into any network tool, firewall rule or access list.

Why a domain can have multiple IPs

  • Load balancing. Busy sites return several A records; clients pick one (often at random).
  • CDN fronting. Cloudflare, Fastly and Akamai serve traffic from hundreds of edge locations; the IPs you see depend on the resolver geography.
  • Failover pairs. Primary and secondary IPs for redundancy.
  • IPv4 and IPv6 in parallel. Dual-stack deployment; modern clients prefer AAAA if they have IPv6 connectivity.

Forward vs reverse DNS

Direction Record type Example
Forward A / AAAA example.com -> 93.184.216.34
Reverse PTR 93.184.216.34 -> example.com

Reverse DNS lives under the special zone in-addr.arpa for IPv4 and ip6.arpa for IPv6. Not every IP has a PTR: home ISP addresses often have none, generic cloud IPs sometimes show the provider’s hostname rather than your app’s.

Forward-confirmed reverse DNS (FCrDNS) means: the A record points to the IP, AND the PTR of that IP resolves back to a domain where a forward lookup again points to the same IP. Mail receivers use this check to score spam likelihood.

Troubleshooting checklist

  • Domain does not resolve: NXDOMAIN; check the spelling and whether the domain is still registered.
  • IP differs from what you expect: DNS cache on your device or ISP; bypass by querying a public resolver, or flush local cache.
  • Different IPs from different locations: CDN geo-routing, expected for big providers.

Frequently Asked Questions

Cloudflare proxies your domain, which means public DNS returns Cloudflare edge IPs, not your origin server. To find the real origin, look at deeper configuration, historical DNS data before enabling the proxy, or try to access through DNS-based leaks.

No. This tool only resolves hostnames to their IP addresses. For country-level location data, use a dedicated GeoIP lookup service.

Not necessarily. Some domains are intentionally configured for MX (email) only, or use a CNAME that resolves lazily. Check NS records to see whether the domain has working nameservers first.

The domain you enter is sent to our server because the lookup runs there. The tool itself does not store lookups or tie them to your account.

Related Tools

Tool available in other languages