Residential IP
A public IP address that an internet provider assigned to a home connection, which address databases therefore label residential rather than hosting.
Updated 19 September 2026 · 17 primary sources
A residential IP is a public IP address that an internet service provider has assigned to a home connection. Websites care about the word because it suggests who is behind a request: a household rather than a server. No field inside the address says residential, though. The label comes from records about the address, and each site reads those records through a database it pays for.
End-user addresses make up a large part of the internet. Spamhaus keeps a list of end-user ranges that should not send email straight to other servers. It holds more than 1.4 billion IPv4 addresses, almost 40 percent of the routable IPv4 space. Which of those count as residential, business or mobile is a question each database answers in its own words.
What the registry says about a home address
The North American registry does define the word. ARIN calls residential customers "individual persons and not organizations" who receive service "at a place of residence for personal use only". Its rules only ask providers to register blocks of eight addresses or more, so a single home address rarely has a whois record of its own.
Even a registered home block may read "Private Customer" and "Private Residence" instead of a name and a street. The registry tells a site which provider holds the space, and little about the household.
How databases decide an address is residential
Most checks therefore start one level up, with the network that announces the address: its ASN. Many operators declare a type for their network in PeeringDB, a database the networks maintain themselves. Almost a third of all ASNs are listed there. On 19 September 2026 Comcast listed its network as Cable/DSL/ISP, while Hetzner Online and DigitalOcean listed theirs as Content. The type is a statement, not a test: Deutsche Telekom, Verizon and AT&T, three of the largest home providers, listed theirs as NSP, a transit type.
The commercial databases add their own labels on top. MaxMind sorts addresses into 15 user types, residential among them, and into connection types such as Cable/DSL and Cellular. IP2Location uses codes such as Fixed Line ISP, Mobile ISP and Data Center/Web Hosting/Transit. IPinfo types the owner of a network as isp, hosting, business, education or government.
The lists do not line up, so one address can carry different labels in different databases. A site sees only the one it uses.
| Source | Who decides | A home line | A server |
|---|---|---|---|
| ARIN whois | The registry's rules | Residential customer; may show "Private Residence" | The holder's own name |
| PeeringDB | The network's operator | Cable/DSL/ISP | Content |
| MaxMind | The vendor | User type residential; connection Cable/DSL | User type hosting |
| IP2Location | The vendor | ISP (Fixed Line ISP) | DCH (Data Center/Web Hosting/Transit) |
| IPinfo | The vendor | ASN type isp | ASN type hosting |
What a reverse DNS name tells you
Reverse DNS is a weaker clue than it looks. A guide to common DNS errors asked in February 1996 for a matching PTR record behind every IP address. When we checked 300 live addresses from networks that declare themselves Cable/DSL/ISP, only 112 returned a name at all.
Of those, 87 were generic names built from the address or carrying words such as dynamic, adsl or pppoe. Hosting networks build names from the address too: 47 of the 136 named addresses in our hosting sample did. A name like that proves little on its own. Words such as vps or dedi, which 48 of those hosting names carried, say more.
| Measure | Cable/DSL/ISP networks | Content networks |
|---|---|---|
| Addresses checked | 300 (205 networks) | 300 (62 networks) |
| Returned any reverse name | 112 | 136 |
| Name built from the address | 73 | 47 |
| Name with dynamic, adsl, pppoe or a similar word | 36 | 25 |
| Name with vps, dedi, hosted or a similar word | 2 | 48 |
Is one residential IP one household?
Not always. Carrier-grade NAT puts many subscribers behind a single public address. In April 2012 the range 100.64.0.0/10 was reserved for the inside of such networks.
An IETF memo of June 2011 had already expected one public IPv4 address to be "shared by multiple homes or small businesses". It listed geolocation among the services that would be affected, and blocklists too: a ban or a location attached to that address applies to everyone behind it.
Why residential addresses are rented, and how proxy networks get them
The trust behind the label is why residential addresses are rented out. A residential proxy routes traffic through such an address. In March 2026 the FBI described how proxy networks get them: with the owner's consent, or without it.
It named SDKs inside mobile apps, free VPNs with hidden terms, compromised TV streaming devices and picture frames, malware, and bandwidth sharing apps that promise to pay for the connection. The same alert told businesses to block addresses known to belong to residential proxy networks.
The databases flag them too. MaxMind marks an address that "belongs to a residential ISP" but sits on a suspected anonymizing network, with a confidence score from 1 to 99. A residential label is no longer a pass on its own.
Where the term comes from
Sorting addresses by who uses them began with email, years before anyone sold a residential proxy. In 1997 Dave Rand and Paul Vixie started keeping a list of addresses that had sent them spam, which became the Real-time Blackhole List. Others built DNS blocklists that listed different categories of addresses, among them dial-up and dynamic ranges. A home connection had no reason to deliver mail to other servers directly.
In January 2007 Spamhaus launched its Policy Block List. In its own words it "builds on the concept of older dynamic/dialup lists", but covers end-user ranges in general. A year later, more than 500 internet providers had submitted roughly 100 million of their own addresses to it.
The registries argued over the privacy side in the same years. ARIN members debated proposal 2003-3 on hiding home customers in whois in November 2003, with spam and abuse contacts as much in the argument as privacy. Today's rules let a provider show "Private Residence".
The proxy market turned the old lists around. Mail servers refuse end-user ranges because a person, not a server, should be behind them. Websites trust the same ranges for the same reason, and that trust is what a residential proxy sells.
How it works
- 1.The registry record names the organisation that holds the block. A home customer's block may read "Private Customer" and "Private Residence", and a single address rarely has a record of its own.
- 2.The ASN shows which network announces the address. Its operator may declare a type, such as Cable/DSL/ISP or Content.
- 3.A commercial database adds its own reading: a user type, a connection type or a usage code, depending on the vendor.
- 4.The reverse DNS name, when there is one, may show whether the provider names its lines like homes or like servers.
- 5.Behaviour comes last. An address seen inside a proxy network can be flagged even though its network is residential.
How HProxy handles it
Our free IP lookup shows the operator behind any address, its ASN and whether the database reads it as hosting or residential. It also checks the address against our record of open proxies. Treat the type as one database's reading, ours included, and check the operator it names first.
Frequently asked questions
Is my IP residential or datacenter?
Look up your address and read who holds it. If the operator is a cable, DSL or fibre provider, your address sits on a consumer access network, which is what the residential label describes. A mobile carrier usually gets its own label, such as Cellular or Mobile ISP. If the operator is a hosting or cloud company, the address is a datacenter address, whatever you use it for. A VPN or a proxy moves the answer to the network its exit sits in.
How do websites tell residential, mobile and datacenter addresses apart?
From records, not from the address. The registry names the holder of the block, and the network's own PeeringDB entry may declare its type. A commercial database adds labels, such as a Cable/DSL or Cellular connection type or a Mobile ISP usage code. Sites combine one of those databases with the reverse name, the history of the address and the behaviour of the request.
Can many people share one residential IP?
Yes. Carrier-grade NAT puts many subscribers behind one public address, which an IETF memo of June 2011 described as sharing "by multiple homes or small businesses". The same memo expected blocklists and geolocation to suffer, because a ban or a location attached to that address applies to everyone behind it.
What is a static residential IP?
The phrase has two meanings. On a home line it is an address the provider does not change. In proxy sales it names an ISP proxy: a server in a data center that uses address space registered to a consumer provider. It reads as residential and stays online around the clock.
How do I get a residential IP?
Your home connection already uses one, sometimes shared with other subscribers behind carrier-grade NAT. To use a residential address that is not your own, you route traffic through someone else's connection, which is what a residential proxy sells. Ask how the provider obtained its addresses: the FBI's alert of March 2026 draws the line at whether the owner of the device agreed.
How are IP addresses assigned to home users?
Down a chain. IANA allocates pools to the five regional internet registries, the registries serve local registries such as internet providers, and the provider assigns an address to each line. On a network short of IPv4 addresses, the line may get a shared address from the 100.64.0.0/10 range instead. The public address then sits on the provider's NAT.
Sources
- Number Resource Policy Manual, sections 2.13, 4.2.3.7.1 and 4.2.3.7.3.2, ARIN, 2026-09-19.
- Last Call for Comment: Policy Proposal 2003-3 (arin-ppml), ARIN, 2003-11-18.
- Number Resources, IANA, 2026-09-18.
- RFC 7020: The Internet Numbers Registry System, IETF, 2013-08.
- About PeeringDB, PeeringDB, 2026-09-19.
- PeeringDB network records for AS7922, AS24940, AS14061, AS3320, AS701 and AS7018 (info_type), PeeringDB, 2026-09-19.
- GeoIP web services: response fields (user_type, connection_type, anonymizer), MaxMind, 2026-09-19.
- IP2Location web service: usage_type, IP2Location, 2026-09-19.
- ASN API: type of the owning organization, IPinfo, 2026-09-19.
- RFC 1912: Common DNS Operational and Configuration Errors, IETF, 1996-02.
- RFC 5782: DNS Blacklists and Whitelists, IETF, 2010-02.
- Policy Blocklist (PBL), Spamhaus, 2026-09-18.
- The Spamhaus PBL, a one year old anti-spam heavyweight, Spamhaus, 2008-01-29.
- RFC 6269: Issues with IP Address Sharing, IETF, 2011-06.
- RFC 6598: IANA-Reserved IPv4 Prefix for Shared Address Space, IETF, 2012-04.
- Evading Residential Proxy Networks (PSA I-031226-PSA), FBI, Internet Crime Complaint Center, 2026-03-12.
- Declared network type and reverse DNS of 3,645 live proxy addresses, HProxy measurement, 2026-09-19.
Back to the full glossary.