Domain into IP
Enter a URL
About Domain into IP
Your website has been loading slowly in certain regions. Your email is bouncing. A server migration happened last week and you are not sure the DNS propagated correctly. Or you are investigating an unfamiliar site and want to know which server it actually runs on before trusting it. In each of these situations, one piece of information cuts through everything else: the IP address behind the domain name.
Every website on the internet, regardless of its domain name, is ultimately hosted on a physical or virtual server identified by an IP address. The domain name — yoursite.com — is a human-readable label that points to that IP. The DigitalSub Pro Domain into IP tool performs that lookup instantly: enter any domain and it returns the IP address (or addresses) the domain currently resolves to, along with the hosting organisation, server location, and whether the domain sits behind a CDN like Cloudflare.
But there is more to understand here than just a number. This page covers the complete picture: how the conversion from domain name to IP address actually works at a technical level, what the IP you get back tells you about a website's infrastructure, why large sites have multiple IP addresses, how CDNs deliberately hide real server IPs, and the practical difference between a shared hosting IP and a dedicated one. Understanding these fundamentals makes you a better troubleshooter, a smarter investigator, and a more informed decision-maker when it comes to your own infrastructure.
What the Tool Returns — Live IP Resolution Results
When you enter a domain, the tool performs a live DNS query and returns the IP address the domain currently resolves to, along with key details about what that IP represents. Here is what a result looks like.
Above is a sample result based on real DNS data. Your result is fetched live when you run the check — IPs can change if a domain switches hosting or CDN providers.
How Your Browser Converts a Domain Name to an IP Address — The Full DNS Chain
Every time someone types a domain name into a browser, a process called DNS resolution runs in the background — usually completing in under 20 milliseconds, fast enough that most users never notice it exists. But the journey from example.com to an IP address is a multi-step chain involving at least four different types of server, working together in a strict hierarchy that has been the backbone of the internet since 1983.
Understanding this chain is not just academic. It explains why DNS changes take time to propagate globally, why your website might be unreachable in one country but not another, and why the IP your tool returns is not always the "real" server IP for sites using CDNs.
Before any network request is made, your operating system checks whether it already knows the IP for this domain from a recent lookup. If you visited example.com an hour ago and the DNS record's TTL (Time to Live) has not expired, the cached IP is used immediately — no network request required. This is why DNS changes sometimes seem slow to take effect: devices and servers cache the old IP until the TTL expires, which can be anywhere from 60 seconds to 24 hours depending on how the domain owner has configured their DNS records.
If no cached answer exists, the request goes to a recursive resolver — a server whose job is to find the answer on your behalf. Most users' recursive resolver is provided by their ISP automatically. Alternatively, you may be using a public resolver like Google's 8.8.8.8, Cloudflare's 1.1.1.1, or OpenDNS. The recursive resolver does the heavy lifting: it queries the hierarchy of DNS servers, collects the answer, returns it to your device, and caches it for future requests. This is the server our Domain into IP tool queries when you submit a domain.
If the recursive resolver does not have the answer cached, it asks one of the 13 logical root name servers (operated by organisations including ICANN, NASA, the US Army, and several universities). These servers do not know the IP address of example.com — but they know who does. They respond with the address of the TLD (Top-Level Domain) name server responsible for .com domains. This first step in the chain narrows the query from "the entire internet" to just "who manages .com."
The TLD name server (run by VeriSign for .com and .net, by PIR for .org, and by country registries for ccTLDs) does not know the final IP address either — but it knows which authoritative name server is responsible for example.com specifically. It returns the address of that authoritative server. This step narrows the query from "who manages all .com domains" to "who manages this specific domain."
This is the server configured by the domain owner — it holds the actual DNS records for the domain. When queried, it looks up the A record (for IPv4) or AAAA record (for IPv6) associated with the domain and returns the IP address. This is the answer the recursive resolver has been looking for. It caches this answer for the duration of the TTL and returns it to your device. Your browser then opens a TCP connection directly to that IP address to load the website.
This entire chain — from your browser's query to the final IP being returned — typically completes in 20 to 120 milliseconds for a fresh lookup. When you use the Domain into IP tool, it performs this lookup fresh each time, bypassing any local DNS cache on your device, so you see the current live IP rather than whatever your computer has stored from a previous visit.
A Records vs AAAA Records — The Two DNS Records Behind Every Domain-to-IP Lookup
Not all domain-to-IP lookups return the same type of address. There are two DNS record types that map domain names to IP addresses, and understanding which one you are looking at tells you something about the server's infrastructure.
A Record — IPv4 Address
The original DNS record type, maps a domain to a 32-bit IPv4 address in the familiar dot-decimal format.
IPv4 addresses look like four numbers separated by dots, each between 0 and 255. This is still the most common type you will encounter — the vast majority of the internet runs on IPv4, despite the address pool being technically exhausted at the allocation level.
AAAA Record — IPv6 Address
The modern record type, maps a domain to a 128-bit IPv6 address in hexadecimal colon notation.
IPv6 addresses look completely different — eight groups of four hexadecimal digits separated by colons. They are far longer because they represent a vastly larger address space (340 undecillion addresses vs IPv4's 4.3 billion). About 40% of global traffic now uses IPv6, and modern servers typically support both simultaneously (dual-stack).
Our tool returns both the A record (IPv4) and AAAA record (IPv6) when both exist. If a domain only has one type, only that one is returned. For troubleshooting purposes, it is worth checking both — a domain might resolve correctly over IPv4 but have a misconfigured or missing AAAA record, causing connectivity issues specifically for users on IPv6-only networks.
What a Website's IP Address Actually Tells You
An IP address looks like a random string of numbers, but it is actually rich with information about a website's infrastructure — if you know how to read it. Here is what the IP behind a domain reveals, and what it cannot tell you.
Hosting Provider / Organisation
Every IP address belongs to an organisation registered with ARIN, RIPE, or another Regional Internet Registry. By looking up which organisation was assigned the IP block, you can identify who is hosting the site. An IP in an AWS block means the site runs on Amazon Web Services. A Hetzner IP means it is on a European dedicated server provider. A Cloudflare IP means you are seeing the CDN, not the real server.
Server's Physical Location
IP geolocation databases map IP ranges to geographic regions. The accuracy varies — country-level is highly reliable, city-level is approximate. For sites on their own servers or with regional hosting, the IP location tells you where the server is physically located. This matters for latency: a server in Frankfurt delivering content to users in Sydney will be significantly slower than one in Singapore. Understanding where a server lives is the first step in optimising global performance.
CDN Detection
Cloudflare, Fastly, Akamai, AWS CloudFront, and other CDN providers operate from known IP ranges that are publicly documented. If a domain's IP falls within one of these ranges, you know the site is behind a CDN — and that the IP you are seeing is the CDN's edge server, not the origin server where the actual website files live. This distinction is crucial for troubleshooting, security research, and understanding true server location.
Shared vs Dedicated Hosting Signal
A single IP hosting hundreds of different domains is a shared hosting environment — common, inexpensive, and completely normal for most small sites. A single IP serving only one or a handful of domains suggests dedicated hosting or a VPS. This can influence email deliverability (one neighbour's spam can affect everyone on a shared IP), SEO understanding, and security assessment of a domain you are investigating.
You check a competitor's domain and get back IP 104.21.57.102
A quick check against Cloudflare's published IP ranges confirms this is a Cloudflare edge server IP. This tells you immediately: the competitor is using Cloudflare as a CDN — so this IP is one of thousands Cloudflare uses, shared across potentially millions of other sites. You cannot determine the real origin server location from this IP. You also know the site has DDoS protection, likely has caching enabled, and is using a globally distributed edge network.
Compare this to a competitor whose domain resolves to 95.217.44.128 — a Hetzner GmbH IP in Helsinki, Finland. No CDN layer. Direct server. You now know their hosting provider, approximate server location, and that their origin IP is publicly exposed — which has implications for both their security posture and your understanding of their infrastructure cost.
Why Does a Domain Sometimes Have Multiple IP Addresses?
Run a domain-to-IP check on Google, Amazon, or Netflix and you will often get back not one IP but several. This is not an error — it is a deliberate architectural choice that allows websites handling enormous traffic volumes to stay fast and reliable. Understanding why helps you interpret what you see when checking any domain.
Simple Site — One IP
A small site, personal blog, or small business site typically resolves to a single IP. All traffic hits one server. Simple, inexpensive, and entirely appropriate for sites that do not need to handle thousands of concurrent visitors.
Load Balanced — Multiple IPs
api.service.com → 52.15.87.194
api.service.com → 52.15.103.90
A high-traffic site or API distributes requests across multiple server IPs using DNS round-robin. Each DNS query may return the IPs in a different order, directing users to different servers to spread the load. Any one server going down does not take the whole service offline.
CDN — Anycast IPs
shop.example.com → 104.22.12.29
shop.example.com → 172.67.75.183
Cloudflare and similar CDNs use anycast routing — the same IP addresses are announced from hundreds of data centres globally. Your DNS query returns whichever Cloudflare edge servers are closest to you, minimising latency. The origin server's IP is hidden entirely.
Recognising What a Domain's IP Tells You About Its Infrastructure
Different IP ranges are reliably associated with specific hosting providers and CDNs. When you run a domain-to-IP check, the result tells you far more than just a number — it tells you who built and operates the infrastructure behind that website. Here is a reference guide to the most common patterns.
| IP Pattern / Range | What It Means | Type | Real Server IP Visible? |
|---|---|---|---|
104.16.x.x – 104.31.x.x172.64.x.x – 172.71.x.x |
Cloudflare CDN edge network. The domain is behind Cloudflare. Up to 47M domains share these ranges. | CDN | No — origin hidden |
13.x.x.x52.x.x.x54.x.x.x |
Amazon Web Services (EC2, CloudFront). The site runs on AWS infrastructure — could be a direct EC2 instance or CloudFront CDN. | Cloud/CDN | Partial — EC2 direct; CloudFront hides origin |
34.x.x.x35.x.x.x |
Google Cloud Platform. The site is hosted on GCP — likely a modern, scalable deployment, startup, or SaaS product. | Cloud | Usually yes — direct GCE IP |
23.185.x.x185.230.x.x |
Fastly CDN. Used by companies like GitHub, Spotify, and Shopify for high-performance content delivery. | CDN | No — origin hidden |
91.108.x.x149.154.x.x |
Telegram's server infrastructure. If a domain resolves to these, the site is likely Telegram-associated. | Specific Service | N/A |
185.199.108.x – 185.199.111.x |
GitHub Pages hosting. A personal or project site served directly from a GitHub repository. | Direct Host | Yes — but shared GitHub Pages infrastructure |
95.x.x.x / 65.x.x.x (Hetzner blocks) |
Hetzner dedicated or VPS server. Budget European hosting — common for developers and small tech businesses. | Direct Server | Yes — real server IP exposed |
| Shared hosting IPs (many domains per IP) | One server hosting many different customer websites simultaneously. Common with GoDaddy, Bluehost, HostGator shared plans. | Shared Host | Yes — but shared with others |
Shared Hosting IP vs Dedicated IP — What It Means for Your Site
One of the most practically important things a domain-to-IP check reveals is whether a domain is on shared hosting. This is not just a technical detail — it has real implications for email deliverability, security, and understanding why a site might be having problems.
What Shared Hosting Actually Looks Like
On a shared hosting server, one physical or virtual server runs hundreds or sometimes thousands of websites simultaneously. They all share the same IP address. When you check the IP of any of those domains, you get back the same number. If you then run a reverse IP lookup, you might find 200, 500, or even 1,000 different domains all pointing to that one IP address.
This is completely normal and perfectly functional for most small websites. The shared server handles requests for each domain correctly using virtual hosting — a configuration that lets a web server serve different content for different domains that all arrive at the same IP, based on the domain name in the HTTP request header.
Where Shared IPs Create Real Problems
The risk with shared IPs is what your neighbours do. If one website on your shared server starts sending spam emails, the IP address gets blacklisted by email providers — and your domain's email gets caught in that blacklist even though you did nothing wrong. This is called IP reputation contamination, and it is one of the most common causes of unexplained email deliverability problems for small businesses on shared hosting.
Similarly, if a neighbouring site on your IP gets blacklisted by Google's Safe Browsing system — for malware, phishing, or spam — the IP itself may take on a bad reputation signal that affects surrounding domains. Running a domain-to-IP check followed by a Blacklist Lookup on the IP address will surface whether your server's IP has been flagged.
When a Dedicated IP Matters
A dedicated IP means one domain (or one hosting account) owns that IP address exclusively. Nobody else's behaviour on the server affects your IP reputation. This matters most for high-volume transactional email sending, payment processing that requires an IP whitelist, SSL certificates that use IP-based validation in legacy systems, and any application where IP reputation is a trust signal. For most standard websites and blogs, shared hosting IPs are completely appropriate.
TTL — Why the IP Behind a Domain Can Change, and How Fast
Every DNS record — including the A and AAAA records that map domains to IP addresses — includes a value called TTL: Time to Live. This number, measured in seconds, tells DNS resolvers how long to cache the record before re-querying for a fresh answer. It is the mechanism that controls how quickly DNS changes propagate globally.
A TTL of 3600 means resolvers cache the IP for 1 hour before re-checking. A TTL of 300 means they re-check every 5 minutes. Some domains use TTLs as low as 60 seconds for rapid failover. Others use 86400 (24 hours) for stability on domains that rarely change servers.
This explains a common confusing scenario: you migrate your website to a new server, update your DNS records, and then check the domain-to-IP result — but it still shows the old IP. That is because resolvers around the world are still serving the cached old IP until their TTL expires. During a server migration, the old IP and the new IP can both be returned by different resolvers simultaneously, depending on when each one last refreshed their cache. This "propagation window" typically takes between 1 and 48 hours to complete globally.
For the Domain into IP tool, this means the result you see reflects the DNS answer from the resolver the tool queries at that moment — which may differ from what a resolver in a different country or network returns if the TTL is currently in transition.
How to Use the Domain into IP Tool — 3 Steps
Enter the Domain Name
Type any domain — e.g. google.com — without https:// or www.. Just the root domain or subdomain you want to look up.
Submit the Query
Click Submit. The tool performs a live DNS resolution, returning the current A and AAAA record results without using your device's local DNS cache.
Read the Full Result
See the IP address, record type (IPv4/IPv6), hosting organisation, and server location. Multiple IPs mean load balancing or CDN. A Cloudflare IP means the real server is hidden.
Real Situations Where Domain-to-IP Lookup Matters
Verifying a DNS Migration Worked
After pointing a domain to a new server, use this tool to confirm the IP has updated to the new server's address. If the old IP is still showing, the TTL has not expired globally yet — or the DNS records were not updated correctly. Checking from a tool bypasses your local cache and gives you a fresh result.
Security Investigation of Suspicious Sites
When a suspicious domain appears in logs, an email, or a report, checking its IP reveals the hosting provider and location. An IP resolving to a known bulletproof hosting provider (one that ignores abuse complaints) is a strong signal of intentional malicious operation. Cross-reference the IP with the Blacklist Lookup tool to check reputation databases.
Confirming CDN Is Active
After setting up Cloudflare or another CDN, check your domain's IP to confirm it now resolves to the CDN's edge IP range rather than your origin server. If the original server IP is still showing, the DNS change to point to the CDN's nameservers has not propagated fully, or there is a misconfiguration in your CDN setup.
Diagnosing Email Delivery Problems
If your domain's emails are being rejected or landing in spam, check the IP your domain resolves to. On shared hosting, your sending IP is often the same as your web IP. If that IP is on a spam blacklist due to another tenant's behaviour, your email suffers. Identifying the IP lets you check its reputation and escalate to your hosting provider or switch to a dedicated IP for email sending.
Competitor Infrastructure Research
Checking a competitor's domain IP reveals their hosting setup — whether they are on AWS, Google Cloud, Hetzner, or a CDN — and approximately where their server is located. This is useful for understanding their technology investment, geographic targeting, and performance infrastructure without access to any of their internal systems.
Server Configuration Firewall Whitelisting
Developers and system administrators who need to whitelist specific domains in firewall rules, access control lists, or application security layers often start with a domain-to-IP lookup. The IP is what the firewall needs — not the domain name. For load-balanced systems returning multiple IPs, all returned IPs need to be whitelisted.
Getting More From Your Domain-to-IP Lookup
5 Ways to Use IP Data More Effectively
- Check both the root domain and the www subdomain. Some websites configure different servers for
yoursite.comandwww.yoursite.com— or have only configured one. Checking both can reveal configuration inconsistencies. If one resolves correctly and the other returns a different or missing IP, there may be a missing DNS record causing visitors on the other version to get a connection error. - If you get a Cloudflare IP, check your own subdomains for the real origin. CDNs typically only proxy the main domain and
www— other subdomains likemail.yoursite.comorftp.yoursite.comoften point directly to the origin server and are not proxied. This is worth knowing if you are managing your own infrastructure — those non-proxied subdomains reveal your real server IP. - Run the check before and after a DNS change. Before changing nameservers or A records, note the current IP. After making the change, run the check periodically to track when the new IP starts appearing. This gives you a concrete way to monitor propagation rather than guessing.
- Cross-reference the IP with a blacklist check after a malware incident. If your site has been infected with malware or used for spam, your hosting IP may have been added to blacklists. Running a Blacklist Lookup on the IP (not just the domain) surfaces reputation issues that your domain may inherit even after cleaning the malware.
- Check a domain's IP before building a link to it from your site. A domain resolving to a Cloudflare IP tells you the site is live and properly configured. A domain resolving to a parked page IP or showing no result at all suggests the site may be abandoned, expired, or broken — linking to it from your content would create a dead outbound link. Our Google Malware Checker pairs with this check for a full safety assessment before linking.
Tools That Work Alongside Domain into IP
A domain-to-IP lookup is typically the starting point for a deeper investigation. These free DigitalSub Pro tools pick up where the IP leaves off.
Frequently Asked Questions
Real questions about domain-to-IP lookups from developers, webmasters, and site owners.
Why does a domain sometimes return multiple IP addresses?
Multiple IP addresses for a single domain are intentional and indicate one of three things:
- Load balancing (DNS round-robin): The domain has multiple A records pointing to different servers. DNS resolvers return them in rotation, distributing incoming traffic across multiple servers. This is used by high-traffic websites and APIs to prevent any single server from being overwhelmed.
- CDN anycast: CDN providers like Cloudflare announce the same IP addresses from hundreds of data centres globally. Different DNS resolvers return different IPs from the CDN's range based on which edge location is closest to the querying resolver. This makes it appear that a domain has multiple IPs when in reality it has many IPs, each associated with a different geographic edge node.
- Dual-stack IPv4 and IPv6: If a domain has both A records (IPv4) and AAAA records (IPv6), the tool returns both — one of each type for the same domain.
Seeing multiple IPs is generally a sign of sophisticated infrastructure rather than a problem.
The tool returns a Cloudflare IP for my website. How do I find my real server IP?
When your domain is behind Cloudflare, the A record returns Cloudflare's edge IP — not your origin server. This is by design and is actually a security feature (hiding your origin IP protects it from direct attacks).
To find your real server IP as the site owner: log into your hosting control panel — it is always listed there as your server IP or hosting IP. You can also check your hosting welcome email, or your domain's direct IP in the hosting panel's DNS settings before Cloudflare was added.
There are also indirect methods: if your domain has an MX record pointing to a mail server on the same physical server (and that subdomain is not proxied through Cloudflare), checking the mail server's A record will reveal the origin IP. However, for most sites this is not recommended — keeping the origin IP hidden is the main point of using a CDN.
I changed my domain's DNS records but the tool still shows the old IP. Why?
This is DNS propagation — one of the most common sources of confusion during server migrations.
When you update a DNS record, the change is made at your authoritative nameserver immediately. But the rest of the internet does not know about it yet. DNS resolvers around the world have cached your old IP address and will continue serving it until the old record's TTL expires. If your TTL was 3600 (1 hour), it can take up to 1 hour for each resolver worldwide to pick up the change. With a TTL of 86400 (24 hours), propagation can take up to 24–48 hours to be complete globally.
The tool performs a fresh DNS lookup bypassing your local cache, but it still queries through a resolver that may have the old record cached. For faster propagation, set your TTL to a low value (like 300 seconds = 5 minutes) well before a planned migration, wait for the old TTL to expire, then make the DNS change. This dramatically reduces the propagation window.
Can I find the IP of any website, including competitors?
Yes — DNS resolution is a public, open process. Any domain name that has a valid A or AAAA record is resolvable by anyone making a DNS query. The Domain into IP tool simply automates this public lookup, the same way your browser does every time you visit a website.
The only limitation is CDNs: if a competitor uses Cloudflare or another proxy CDN, the IP you retrieve is the CDN's edge server — not their origin server. This tells you they are using a CDN and which one, but not where their actual server is located.
What is an ASN and what does it tell me?
ASN stands for Autonomous System Number. An Autonomous System (AS) is a large network or group of networks under a common routing policy, typically operated by an ISP, hosting company, CDN, or large organisation. The ASN is a unique identifier for that network.
When the tool shows an ASN alongside an IP address, it tells you which network operator owns the IP block. For example:
- ASN AS13335 = Cloudflare
- ASN AS16509 = Amazon AWS
- ASN AS15169 = Google
- ASN AS36459 = GitHub
- ASN AS24940 = Hetzner Online
The ASN is particularly useful in security research — multiple malicious domains resolving to IPs in the same ASN may indicate they are operated by the same threat actor, hosted on the same infrastructure, or using the same bulletproof hosting provider.
Does my website's IP address affect its SEO?
Directly, no — Google does not use IP address as a direct ranking factor. The IP your domain resolves to does not inherently help or hurt your rankings.
However, there are indirect ways the IP environment can affect SEO:
- Blacklisted shared IP: If your site is on a shared hosting IP that is on email blacklists, it does not directly affect search rankings — but if the IP has been flagged in Google Safe Browsing due to another tenant's malware, it could affect your site's reputation
- Server location and speed: The geographic distance between your server and your visitors affects page load time, which is a confirmed Core Web Vitals signal. A server in London serving users in Dhaka will be slower than one in Singapore — this speed difference affects rankings
- CDN usage: A CDN improves load time for global visitors by serving content from nearby edge servers, which can improve Core Web Vitals scores — a genuine SEO signal
So while the IP number itself is not a ranking factor, the infrastructure decisions it represents — server location, CDN usage, shared vs dedicated hosting — have real performance implications that do affect SEO.
Is the Domain into IP tool completely free? Any usage limits?
Yes — completely free with no sign-up, no account, and no usage limits. Check as many domains as you need, as often as you need. This applies to all 47 free tools on DigitalSub Pro — there is no premium tier, daily cap, or paywall on any feature.