Home›Developer Tools›Domain to IP
⇄ Forward and reverse DNS

Domain to IP Lookup

Resolve a hostname into its current IPv4 and IPv6 answers, inspect cache lifetimes and aliases, and see whether each address publishes a reverse hostname.

A + AAAA recordsTTL & CNAMEReverse DNS
DNS resolution

Enter a domain or hostname

URLs are accepted; the hostname will be extracted. Enter an IP address in the IP Location Finder instead.
Understand the resolution

A domain name can lead through aliases to several network addresses

DNS clients request records for a hostname. A direct A or AAAA answer contains an address; a CNAME redirects the lookup to another hostname. Multiple answers often improve resilience or route visitors through a CDN.

A

IPv4 address

Maps a hostname to a 32-bit IPv4 address such as 192.0.2.1.

AAAA

IPv6 address

Maps a hostname to a 128-bit IPv6 address such as 2001:db8::1.

CNAME

Canonical alias

Points the queried hostname to another name that is resolved for addresses.

PTR

Reverse hostname

Maps an IP back to a name controlled by the address owner; it may differ from the original domain.

How to interpret the results

  1. Check the exact hostname.example.com and www.example.com can resolve differently.
  2. Review every returned address.Firewalls and allowlists may need all current answers, but DNS records can change.
  3. Use TTL as cache context.TTL is the maximum advertised cache lifetime, not a countdown for every resolver.
  4. Do not assume it is the origin.CDNs and proxies intentionally expose edge addresses while hiding the origin server.

Frequently asked questions

Why does the same domain return several IP addresses?

Multiple addresses can support redundancy, load balancing, anycast, geographic routing, or CDN delivery. This is normal.

Why is there no IPv6 result?

The hostname may simply have no AAAA record. IPv4-only DNS remains common and does not by itself mean the website is unavailable.

Does the PTR hostname prove who owns a website?

No. PTR records are managed by the IP address holder and often identify a hosting platform or generic server. They are useful context, not ownership proof.

Why can another DNS checker show different addresses?

Resolver caching, CDN geography, anycast, DNS changes, and split-horizon configurations can produce different legitimate answers.

Can I use these IPs permanently in a firewall?

Only with caution. Many services change addresses or use large published ranges. Prefer an official provider allowlist when available.