Reverse IP lookup: how to find the domains on an IP

Run a reverse IP lookup to find the host name and websites behind an IP address, see who owns it, and know why every result is incomplete.

7–11 minutes
Network switch with many blue patch cables

A reverse IP lookup starts from an IP addressIP address The number address of a device on the internet, like 203.0.113.10. Computers use it to find each other, the way post uses street addresses. More about IP address → and tries to find the domain names that use it. This guide is for site owners and new developers who want to know which websites share their server, who an address belongs to, or why an unfamiliar name keeps appearing in their logs.

A reverse IP lookup means one of two different things. **To get the single official name set for an address, run dig -x 203.0.113.10 +short or nslookup 203.0.113.10: this reads the address’s PTR record. To list every website hosted on an address, you need an online reverse IP lookup tool**, which searches a database of DNSDNS The internet’s phone book. It turns a name people can remember, like example.com, into the number address computers use to find the server. More about DNS → answers it has collected over time. Neither method is complete, so treat the results as clues rather than a full list.

The two kinds of reverse IP lookup

Normal DNS works forwards: you give it a name such as example.com and it returns an IP address from the domain’s A recordA record The line in a domain’s settings that says which server’s address to send visitors to. Like a forwarding address card for your website. More about A record →. Going backwards is harder, because nothing in DNS keeps a list of every name that points at a given address. Anyone can create an A record pointing at any IP address, and the owner of that address is never told.

That is why “reverse IP lookup” covers two separate jobs:

MethodWhat it asksWhat you getWhere the answer comes from
Reverse DNS (PTR lookup)What name has the address owner set for this IP?Usually one host name, sometimes noneThe address owner’s DNS, live
Reverse IP lookup toolWhich domains have been seen pointing at this IP?A list of domains, often incomplete or out of dateA database of past DNS answers

The first is part of DNS itself and is free to run from any computer. The second is a research service: the tool’s operator collects DNS answers from crawlers and resolvers (called passive DNS), then lets you search that collection by IP address.

Method 1: reverse DNS with dig, nslookup or PowerShell

Reverse DNS asks for the PTR record of an address. The address owner, usually a hosting company or internet provider, controls it, not the owners of the websites on the server. Replace 203.0.113.10 in these examples with the address you are checking.

macOS and Linux

dig -x 203.0.113.10 +short

The -x option turns the address into the special reverse name for you and asks for its PTR record. A typical answer looks like this:

server42.examplehost.net.

If you prefer, host gives the same answer in a sentence:

host 203.0.113.10

On Ubuntu and Debian, dig and host come in the dnsutils package (sudo apt install dnsutils). On AlmaLinux and Rocky Linux they are in bind-utils (sudo dnf install bind-utils).

Windows

Both of these work in Command Prompt or PowerShell:

nslookup 203.0.113.10
Resolve-DnsName 203.0.113.10

Resolve-DnsName is PowerShell only. Look for the NameHost value in its output.

What the answer tells you

Behind the scenes, the address is reversed and placed under a special domain. For 203.0.113.10, the PTR record lives at 10.113.0.203.in-addr.arpa. IPv6 addresses use ip6.arpa in the same way, and dig -x handles both.

The name you get back is usually the server’s own host name, such as server42.examplehost.net or 203-0-113-10.example-isp.net. On shared hosting it almost never names the websites on the server, because hundreds of sites share one address and a PTR record normally holds one name. So reverse DNS tells you who runs the machine, not what is on it.

If you get no answer at all, the address simply has no PTR record. That is common and not an error. For a deeper look at running these queries and reading their status codesHTTP status code The three-digit number a website sends back with every page, saying how it went: 200 means fine, 404 means not found, 500 means the site itself broke. More about HTTP status code →, see how to do a DNS lookup.

Reverse DNS matters most for email. Many receiving mail servers check that a sending server’s IP address has a PTR record, and that the name it returns points back to the same address. If your own server sends mail, set its PTR record through your host’s control panelControl panel A website you log into to manage your hosting with buttons and forms, instead of typing commands. cPanel and Plesk are the common ones. More about Control panel → or support team.

Method 2: find every domain on an IP address

When people search for a reverse IP lookup, they usually want the list: every website on the same server. There is no DNS query that returns this. You have to use a database that someone has built by watching DNS over time.

Use an online reverse IP lookup tool

Search for “reverse IP lookup” and you will find several free tools. Enter the IP address and the tool returns the domains its database has seen resolving to it. Keep three limits in mind:

  • It only knows what it has seen. A domain that nobody’s crawler has visited will be missing.
  • It can be out of date. A site that moved away last month may still be listed, and one that arrived yesterday may not.
  • Free versions are often capped. Many show only the first few dozen results.

Run the same address through two different tools and compare. If both list a domain, it is probably real. If only one does, check it yourself (see below).

Check each result yourself

Confirm that a domain really points at the address today with a forward lookup:

dig example.com A +short

If the answer matches the IP address you started with, the domain is currently hosted there. If it shows a different address, the tool’s record is stale.

Look at what the server itself says

You can also ask the server directly. Open the bare address in a terminal:

curl -sI http://203.0.113.10

The headers often show a redirect (Location:) to the server’s default site, or a hosting company’s placeholder page. For HTTPSHTTPS The secure version of the web, shown by the padlock. Everything sent between you and the site is scrambled so nobody in between can read or change it. More about HTTPS →, read the certificate the server offers when no site name is given:

openssl s_client -connect 203.0.113.10:443 </dev/null 2>/dev/null | openssl x509 -noout -subject -ext subjectAltName

The subjectAltName line lists the names that certificate covers. On a server with many sites this is only the default certificate, because browsers send the site name during the connection (a feature called SNI) and get a different certificate for each site. It is still a useful clue.

Find out who owns an IP address

Sometimes you do not need the domains at all. You want to know which organisation an address belongs to, for example to report abuse or to understand a visitor in your logs. For that, use a WHOIS lookup on the address itself, which asks the regional internet registry that handed it out.

On macOS and Linux:

whois 203.0.113.10

On Ubuntu and Debian you may need sudo apt install whois first. Look for fields such as OrgName, NetName, netname, descr and OrgAbuseEmail or abuse-mailbox. The names differ between registries, but they all show the network’s owner and its abuse contact.

The newer protocol for the same data is RDAP, which returns structured JSON. ARIN’s RDAP service redirects queries for addresses held by other registries, so this works for most addresses:

curl -sL https://rdap.arin.net/registry/ip/203.0.113.10

The owner is usually a hosting company, cloud provider or internet provider, not the person running the website. That is still the right place to send an abuse report.

The 203.0.113.x addresses in this guide are reserved for documentation, so they return no useful results. Use a real address, such as the one you found with an IP checker, when you run the commands.

Reading the results

Once you have results, a few patterns come up again and again.

Hundreds or thousands of domains. The address belongs to a shared hostingShared hosting Hosting where your website shares one server with many others. Cheap and simple; the host looks after the server. More about Shared hosting → server or, more often, a CDN or reverse proxy. Services that sit in front of websites answer for huge numbers of unrelated sites on the same addresses, so the list tells you nothing about who shares the real server behind them.

One or two domains. The address is probably a VPSVPS A private slice of a powerful server, with its own guaranteed share of memory and processing and full control, at a fraction of the price of a whole machine. More about VPS → or dedicated server used by one organisation. See shared vs VPS vs dedicated hosting for how hosting types divide up addresses.

A PTR name from a hosting company and no domains. A new server, or one used for something other than websites, such as a mail relay or a VPN.

Why you might check your own server

  • After a move. Confirm that your domain now resolves to the new server and that no forgotten domain still points at the old one.
  • On shared hosting. If a neighbouring site sends spam, the shared address can end up on a block list and your email can suffer. Knowing your neighbours helps you understand the cause, though only your host can fix it, usually by moving you to another address.
  • When you see a strange host name in your logs. A reverse DNS lookup on the visitor’s address often reveals a search engine crawler, a monitoring service or a cloud provider.

Do not trust a PTR name on its own to identify a visitor. Whoever controls an address can set its PTR record to any name. To check a claimed crawler, do the reverse lookup, then a forward lookup on the name you got back, and make sure it returns the original address.

Common problems

SymptomCauseFix
dig -x returns nothingThe address has no PTR recordNormal for many addresses. For your own server, ask your host to set one
PTR name is a generic host name, not your domainThe host set a default nameAsk your host or use their control panel to set a custom PTR record
Online tool shows a domain that no longer uses the IPThe tool’s database is out of dateConfirm with dig example.com A +short before acting on it
Online tool shows thousands of unrelated sitesThe address belongs to a CDN or proxyLook up the origin server instead, if you know it
Your own domain is missing from the tool’s listThe tool has not seen it yetNothing to fix. The tool is incomplete, not your DNS
whois says command not foundThe whois client is not installedInstall the whois package, or use the RDAP command instead

Official documentation

Get the next guide

One email when there is something worth reading: new guides, errors going around, and hosting changes that affect your site.

No tracking pixels, and one click to leave.

Something out of date? Software changes. If a step no longer works, tell us and we will check it and update the page.