Find the IPv4 and IPv6 addresses behind any domain, with live DNS records, TTLs and the network that owns each address. Free, no signup.
Free · Live DNS · IPv4 & IPv6Run a complete audit of this domain's page speed, meta tags, mobile-friendliness and more.
Run Free Website AuditEvery website lives on a server, and every server is reached through an IP address. Domain names exist so nobody has to remember those numbers: when you type a domain into a browser, a DNS lookup translates it into one or more IP addresses. This tool performs exactly that lookup and shows you the result, including A records (IPv4), AAAA records (IPv6), any CNAME aliases in between and each record's TTL, the number of seconds the answer may be cached.
For every address it finds, the tool also shows the reverse DNS hostname, the network owner and ASN and the country where the address block is registered, so you can tell at a glance whether a domain is on a shared host, a cloud platform or behind a CDN such as Cloudflare. It is useful for checking that a DNS change has taken effect after a migration, confirming where a domain really points, debugging “site not loading” reports, and building firewall or allow-lists. Because some sites return different answers depending on the visitor's location, treat the result as what DNS returns from this server's point of view.
Sites use several addresses for load balancing, redundancy, or because they are served by a CDN whose edge servers share traffic. Having both an IPv4 and an IPv6 address also counts as two.
Resolvers cache answers for as long as the TTL allows. Check the TTL shown above: the old address can keep appearing until that time has passed.
Not always. If the domain uses Cloudflare or another CDN or proxy, the address belongs to the provider's edge network, and your real server stays hidden behind it.
Every website on the internet lives on a remote physical or virtual server, and every server is reached through a unique IP address. Human-friendly domain names exist so that users never have to memorize complex strings of numbers. When you type a URL into your web browser, a Domain Name System (DNS) query executes instantly, translating that domain into one or more IP addresses.
This utility—combining a Live DNS Resolver, an IP Network & ASN Inspector, and a Reverse DNS Lookup Engine—is engineered to give webmasters, systems administrators, and SEO professionals precise visibility into how domain names map to underlying server infrastructure.
When auditing domain infrastructure, understanding the specific record components returned during a lookup is vital for diagnosing connection errors, migration delays, and hosting setups.
┌──────────────────────────────────────────────┐
│ IP Resolution Workflow │
└──────────────────────┬───────────────────────┘
│
┌─────────────────────────────────┼─────────────────────────────────┐
│ │ │
┌───────┴───────────────┐ ┌───────┴───────────────┐ ┌───────┴───────────────┐
│ Address Records │ │ Alias CNAME Chain │ │ TTL Caching │
└───────┬───────────────┘ └───────┬───────────────┘ └───────┬───────────────┘
│ │ │
• A Records (IPv4) • Target Hostname Mapping • Caching Duration (Seconds)
• AAAA Records (IPv6) • Redirection Tracking • Propagation Interval Control
A Records (IPv4): Resolves the domain name to a standard 32-bit IPv4 address (e.g., 192.0.2.14), representing the direct destination server for standard web traffic.
AAAA Records (IPv6): Resolves the domain to a 128-bit IPv6 address, accommodating modern global network infrastructure and dual-stack connectivity.
Purpose: Traces alias mappings where one domain name points to another hostname (e.g., pointing a subdomain to a SaaS platform, bucket storage, or a Content Delivery Network endpoint).
Purpose: Measured in seconds, the TTL value indicates how long local recursive DNS resolvers and browsers are permitted to cache a specific IP record before requesting a fresh lookup from the authoritative nameserver.
Beyond basic IP addresses, this tool performs deeper infrastructure queries to reveal the administrative and geographic context of the destination server:
| Feature | Technical Implementation | Administrator Benefit |
| Reverse DNS (PTR) | Queries pointer records to resolve IP addresses back to hostnames. | Identifies specific server hostnames and infrastructure providers. |
| ASN & Network Owner | Retrieves the Autonomous System Number (ASN) and routing registry data. | Clarifies whether a site runs on shared hosting, AWS, Google Cloud, or Azure. |
| Geographic Registry | Identifies the physical country and regional IP block registration. | Verifies CDN edge locations and hosting server physical regions. |
Verifying Migrations: Confirm immediately whether a domain's A records have successfully updated to point to a new web host or staging server after a migration.
Debugging Site Outages: Investigate "site not loading" reports by checking if the domain resolves to an active, responsive IP address or returns a resolution error.
Identifying CDN and Cloud Usage: Quickly spot whether a site is sitting behind a reverse proxy or CDN (such as Cloudflare, Akamai, or Fastly) by analyzing the returned ASN and network owner.
Building Security Allow-Lists: Gather accurate server IP blocks and network metadata for configuring firewall rules, API access policies, or server allow-lists.
Location-Dependent Resolution Note: Because modern global networks utilize Anycast routing and geo-targeted DNS, different visitors around the world may receive different IP addresses depending on their physical location. Treat the results generated by this tool as what DNS returns from this specific testing server's point of view.
Enter the target domain or hostname (e.g., example.com) into the lookup input box.
Review the returned A and AAAA records alongside their TTL values to determine how long changes will take to propagate across local network caches.
Examine the Reverse DNS hostname, ASN, Network Owner, and Country fields to understand the underlying hosting environment.
Lower TTLs Before Server Migrations: When planning a server migration, lower your DNS record TTL values to 300 seconds (5 minutes) at least 24 hours prior. This ensures quick global cutovers when you update your A records.
Monitor Infrastructure Changes: Periodically check your IP resolution to ensure your CDN proxies or hosting provider allocations have not unexpectedly shifted.
Websites utilizing high-availability servers, load balancers, or CDNs often return multiple IP addresses. This allows traffic to be distributed across different server nodes to prevent congestion and ensure continuous uptime.
An ASN is a unique identifier assigned to a large network or group of IP routing prefixes operated by a single entity (such as Cloudflare, Amazon, or DigitalOcean). Checking the ASN instantly reveals which cloud provider or enterprise network hosts the server.
DNS results can vary due to local ISP caching, regional DNS resolvers (like Google 8.8.8.8 or Cloudflare 1.1.1.1), or Anycast routing that directs queries to the nearest data center relative to the resolver's physical location.
Understanding how domain names map to underlying server IP addresses is essential for technical troubleshooting, migration verification, and infrastructure security.
For Accurate Migration Audits: Always verify that your A and AAAA records point to the correct server endpoints and check TTL values to anticipate propagation delays.
For Infrastructure Transparency: Use Reverse DNS, ASN data, and network owner lookups to confirm whether a site operates on dedicated cloud infrastructure or behind a CDN proxy.
Use the IP & DNS Resolution Lookup Tool above to inspect live server mappings, diagnose routing issues, and maintain total control over your web infrastructure!