ASN Lookups: How A Site Knows Your Address Belongs To A Hosting Company
Type an IP address into a free lookup page and the second line you get back, after the location, is usually something like “AS4773” followed by a company name. That’s the autonomous system number, the ASN, and the name of the organisation that routes that address on the internet. In Singapore, AS4773 is M1 and AS9874 is StarHub, both consumer carriers. If the name that comes back is instead a cloud provider or a company whose business is renting servers, a site knows in one lookup that the traffic is coming from a hosting range, not from someone’s phone or home. No fingerprint needed, no behaviour analysis, no account history. The ownership of the address says it. This piece explains how that lookup works, what else sits in the records around it, why so many “residential” proxies fail it, and how to check your own addresses the way a platform does.
What an autonomous system is
The internet is a network of networks, and each of those networks has to tell the others which addresses it can deliver traffic to. The protocol that does this is called BGP. The networks taking part are called autonomous systems, and each has a number.
An autonomous system is roughly one organisation’s network under one routing policy. A consumer ISP has one or a few. A mobile carrier has one or a few, sometimes separate from its fixed line business. A cloud provider has several. A hosting company that rents servers has its own. Large universities and some big companies have their own too.
Each autonomous system announces the blocks of addresses it handles. Those announcements are public, because every other network needs them to route traffic. So for any IP address, anyone can find out which autonomous system currently announces the block containing it.
That’s the whole basis of an ASN lookup. It doesn’t guess and it doesn’t rely on a vendor’s opinion. It reads the same public routing data the internet uses to deliver packets. The ASN tells you who routes the address, and the organisation name attached to that ASN usually tells you what kind of business they are.
ASNs and address blocks are handed out by five regional internet registries. APNIC covers the Asia Pacific region, RIPE NCC covers Europe and the Middle East, ARIN covers North America, and LACNIC and AFRINIC cover Latin America and Africa. Each keeps public records of who holds which blocks.
The records around an address
The ASN is one piece. A full lookup pulls in several records that together describe an address, and platforms, fraud vendors and curious operators all read the same ones.
There’s the routing data. Which ASN announces the address, which prefix it sits in, how large that prefix is, and in some tools how long it’s been announced by that ASN.
There’s the registry record, usually read with a whois query. It names the organisation holding the block, often with a network name, a country, a registration date and an abuse contact. For larger blocks it may show sub allocations, where the holder has assigned a slice to a customer.
There’s reverse DNS. Many addresses have a name attached, set by whoever controls the block. Consumer ISPs often use patterns that describe customer lines. Hosting companies often use names that describe servers.
There’s the ASN’s own profile. How many prefixes it announces, how many addresses in total, which other networks it connects to, and what kind of network it says it is in public directories like PeeringDB.
And there’s third party classification. IP intelligence services combine all of the above with their own observations and label each address with a type, such as ISP, mobile, hosting or business.
A platform rarely needs to do this work itself. It buys the classification. But the classification is built from public data you can read too.
How the lookup labels an address
The label most sites care about is the connection type. Is this address a consumer line, a mobile line, a business, or a hosting range?
The ASN does most of the work. If the ASN belongs to a company that rents servers, the address is almost certainly hosting. If it belongs to a consumer broadband provider, the address is probably residential. If it belongs to a mobile carrier, it’s probably mobile. Cloud providers make it even simpler. The big ones publish their own IP ranges in machine readable files so customers can configure firewalls, and anyone can download those files.
Finer labels come from the other records. A carrier that runs fixed and mobile services from one ASN might still use distinctive prefixes or reverse DNS names for each. A consumer ISP’s business customers might sit in separate ranges with their own names.
Then observation fills gaps. An address that shows the traffic pattern of a server, like many unrelated clients or activity around the clock with no human rhythm, can be relabelled even if its registration looks residential.
The result is a label that’s usually right, occasionally wrong, and updated over time. For hosting and cloud addresses it’s rarely wrong, because the ownership data leaves little room for doubt. That’s the core reason datacenter proxies struggle on strict platforms. The address announces what it is before anything else happens.
Why hosting ranges are treated differently
A platform treats a hosting address with suspicion for a simple reason. Ordinary people don’t browse from servers.
Real customers use phones on mobile networks, laptops on home broadband and office machines on business connections. Traffic from a hosting range is overwhelmingly machine traffic: crawlers, monitoring, scripts, VPN exits, proxies and bots. There are legitimate uses, like a company’s own server calling an API, but those rarely involve logging into a consumer account through a browser.
So a hosting address on a consumer account login is a mismatch in the same way a desktop GPU on a phone profile is a mismatch. On its own it proves nothing. What it does is shift the probability far enough that most platforms add friction, and some block outright for sensitive actions like signups or payments.
This is also why blocking hosting ranges is cheap for a platform. It is the same cost logic that protects mobile addresses, run in reverse. Few real customers live on hosting addresses, so the collateral damage of treating them harshly is low.
VPN services are a related case. Most commercial VPN exits run in datacenters, so they carry hosting ASNs. Some VPN providers use residential or mobile exits instead, and some IP intelligence services also label known VPN exits separately.
The point for account work is simple. If the ASN says hosting, every other layer of your setup starts at a disadvantage.
Mislabeled residential ranges
This is where the lookup catches people who thought they’d paid to avoid it.
Residential proxies command higher prices because their addresses should come from consumer ISPs. But not every address sold as residential really is. There are a few ways a range ends up sold as residential when it isn’t.
The simplest is plain mislabelling. A provider sells datacenter addresses and calls them residential. The ASN lookup shows a hosting company immediately.
A subtler version involves leased address space. IPv4 blocks are bought, sold and leased like property. A proxy operator can lease a block, announce it from a server in a datacenter, and register it with a network name that sounds like a consumer ISP. For a while, some classification databases may be fooled. But the ASN announcing the block is often a hosting network, or a small, recently created ASN whose only connections are to datacenter transit providers.
Another version is the so called ISP proxy or static residential proxy. These addresses really are registered to an ISP, and the ASN really is an ISP’s. But the traffic is coming from a server in a data centre that the ISP hosts or leases space to. The ASN says ISP. Other signals, like reverse DNS, open ports, latency and the address’s traffic pattern, may say server.
Classification databases catch up with all of these over time. A range that looks residential this month can be relabelled next month once enough observations accumulate. When that happens, every account using it inherits the new label at once.
Geofeeds and the location claim
Location lookups and ownership lookups often disagree on leased ranges, and understanding why makes the disagreement useful.
The location shown for an IP address comes from geolocation databases. Those databases combine registry data, routing data, measurements and, increasingly, geofeeds. A geofeed is a simple file published by whoever holds an address block, stating which city or region each part of the block should be located in. There’s a standard format for it, and the major geolocation providers read them.
That’s a sensible system for real networks. An ISP knows where its customers are, and a geofeed lets it tell the databases. But it also means the holder of a leased block can declare that the block is in almost any city it likes, and some databases will follow.
So a proxy range can show a convincing consumer city in a location lookup while its ASN is a hosting network in another country. The location looks right. The ownership doesn’t.
For operators, this is a reason never to trust a location check alone. A proxy provider that advertises “city level targeting” may be delivering exactly what the location lookup shows, and still be serving addresses from a data centre elsewhere.
It’s also a reason to compare the countries in the records. The registry record, the ASN’s home, the geolocation and the provider’s claim should broadly agree. A block registered in one country, announced by an ASN in a second and geolocated to a third tells a story no consumer ISP would produce.
Platforms can make the same comparison, and some IP intelligence services flag exactly this kind of inconsistency. The location claim is set by the holder. The routing data isn’t, so when the two disagree, the routing data usually wins.
Small and young ASNs
One of the quieter tells is the size and age of the ASN itself.
A real consumer ISP’s ASN is usually large. It announces many prefixes covering a lot of addresses, it has existed for years, and it connects to many other networks, because it has to reach a large customer base. Mobile carriers look similar.
An ASN created recently, announcing only a handful of small prefixes, connected only to one or two transit providers known for hosting customers, looks very different. It might be a small regional ISP. It might be a company’s own network. It might be a proxy operator’s network built to announce leased space. The lookup can’t tell you which for certain, but it tells you the address doesn’t come from a large consumer network.
Tools that show routing history add more. If a prefix was announced by one ASN last year and a different one this year, it moved. Moving is normal for leased space. It’s less normal for a consumer ISP’s customer ranges, which tend to stay put for years.
None of these facts decides anything alone. A small ASN is not a hosting ASN by definition. But when a provider tells you an address is residential, and the address sits in a tiny, young ASN with a generic name and datacenter upstreams, the story and the evidence don’t match.
A platform doesn’t need to be certain either. It only needs the probability to shift.
Reverse DNS and the name on the address
Reverse DNS is the name attached to an IP address, as opposed to the address attached to a name. You can look it up with a simple command or any online lookup tool.
Consumer ISPs often set reverse DNS names that describe customer lines. They might include words that suggest dynamic or customer premises equipment, a region code and a fragment of the address. The exact patterns vary by ISP and country. Mobile carriers often have their own patterns, or no reverse DNS at all for their NAT pools.
Hosting companies usually set names that describe servers. Words like server, host, vps, static or the hosting company’s own domain appear often. Cloud providers use their own naming schemes that make the provider and region obvious.
Many addresses have no reverse DNS name at all, which tells you little on its own.
For an operator checking a proxy, reverse DNS is a quick cross check. If the ASN is a consumer ISP and the reverse DNS follows that ISP’s customer naming, the story holds together. If the ASN says ISP but the reverse DNS contains a hosting company’s domain, something doesn’t add up. If a so called residential address has reverse DNS naming it as a VPS, you have your answer.
Reverse DNS is controlled by whoever holds the block, so it can be set to anything. That’s why it’s a cross check rather than proof. A careful proxy operator can make it look residential. A careless one leaves the hosting names in place.
Business, education and the ranges in between
Not every address is either residential or hosting. A large share of the internet sits in ranges that are neither, and they carry their own story.
Business connections are the biggest group. Offices, shops and factories use business broadband or leased lines from ISPs, often from separate ranges with their own reverse DNS patterns. Traffic from them looks human during working hours and quiet at night.
Universities and research networks often run their own ASNs. Traffic from them is a mix of students, staff and servers, and it looks like a small town.
Large companies sometimes run their own ASNs too, routing their employees’ traffic through their own network and security gateways.
Classification services label these ranges as business or education rather than residential. Platforms generally treat them as ordinary, since real people log in from work and campus all the time.
For account work, the issue is fit rather than suspicion. A personal account that always logs in from a university network, day and night, including holidays, is a slightly odd story. So is a consumer account that only ever appears on a business range belonging to a company in a different industry. None of that is a red flag by itself. It’s one more place where the network should agree with the person the account claims to be.
Some proxy products draw from business ranges and sell them as residential. The ASN might be a real ISP, but the reverse DNS and the classification say business. That’s a milder mismatch than hosting, and it may be perfectly acceptable for some uses. It’s still worth knowing what you’re actually buying.
Mobile ASNs and what they can’t separate
For mobile proxies, the ASN lookup usually looks reassuring. The address belongs to a mobile carrier’s network, and the classification says mobile. That’s what you want.
It’s worth knowing the limits of that check. Some carriers run mobile and fixed services from a single ASN. The ASN then says “this carrier” without saying which service. Classification services separate them using prefixes, reverse DNS and observed traffic, and they don’t always get it right.
Some carriers also host business services or small data centres, and addresses from those can sit in the same ASN as consumer lines.
For operators running their own modems, the ASN is a useful sanity check on the SIM. If you expect a particular carrier and the lookup shows a different one, the modem may have attached to a roaming partner, or the SIM may be from a different operator than you thought. Checking the ICCID prefix on the SIM itself, or asking the modem which network it’s attached to, answers that directly.
For anyone buying mobile proxies, the lookup confirms the carrier at least. Ask the provider which carrier they use, then look up a few addresses from the pool and confirm the ASN matches. If the answer is a hosting network, the proxy isn’t mobile, whatever the product page says.
Running the lookup yourself
Here’s a routine to check any proxy address the way a platform’s vendors would.
Connect through the proxy and load a “what is my IP” page, so you’re checking the actual exit, not the gateway address you connect to. Note the exit address.
Look it up on a tool that shows the ASN and organisation name. Several free services do this, including ipinfo and the Hurricane Electric BGP toolkit at bgp.he.net. Note the ASN number and the name.
Search the organisation name if you don’t recognise it. Is it a consumer ISP, a mobile carrier, a cloud provider, a hosting company, or something else?
Look at the ASN’s profile on the BGP toolkit. How many prefixes does it announce? Who are its upstream providers? For some ASNs, PeeringDB lists a self declared network type.
Run a whois query on the address and read the network name, country and registration date.
Check reverse DNS.
Then compare all of it with what the provider claims. A residential claim should come with a consumer ISP ASN, customer style reverse DNS or none, and no hosting fingerprints anywhere in the records.
Do this for several addresses from the same pool, not just one.
A worked example of a failing range
Here’s a hypothetical to show how the pieces combine.
An operator buys a package of “static residential” addresses from a provider, advertised as coming from a well known consumer ISP. The first address looks up to an ASN whose name sounds like a broadband company. So far, fine.
On the BGP toolkit, the ASN turns out to announce only three small prefixes. It was registered within the past year. Its only upstream provider is a transit network whose customer list is mostly hosting companies.
The whois record for the address shows a network name that includes the word “broadband” but a registration date only a few months old, and a sub allocation to a company whose name matches the proxy provider.
Reverse DNS returns a name ending in a hosting company’s domain.
Nothing here says the provider lied outright. The ASN may well be registered as an ISP. But every record around it points the same direction: a small, new network announcing leased space from a data centre. Classification databases will likely reach the same conclusion if they haven’t already.
The operator’s accounts on those addresses will look residential to some checks and hosting to others, and over time the hosting reading tends to win. When a database relabels the range, every account on it changes category together.
The fix is to test before committing accounts to a range, not after.
What the lookup can’t tell you
The ASN tells you who routes an address. It doesn’t tell you how the address has been used.
A genuine consumer ISP address can carry a terrible reputation, because the previous user ran a spam bot or because a residential proxy network has been sending automated traffic through it. That’s the fraud score side of the picture, and it’s a separate question from ownership.
The ASN also can’t tell you how a residential address came to be available as a proxy. Some residential proxy networks route traffic through real consumer devices whose owners installed an app or software development kit that shares their connection. The ASN lookup on those addresses passes, because the address really is a home connection. Whether the device owner meaningfully agreed to that is a different question, and one worth asking any provider directly before you buy.
And the lookup can’t tell you what a particular platform does with the classification. Some block hosting addresses at signup. Some add friction. Some weigh it lightly and lean on other signals. None of them publish the weights.
So treat the ASN as the first gate. An address that fails it has a problem nothing else can fix. An address that passes it still has to pass everything else.
IPv6 ranges too
Everything above applies to IPv6 as well, with a couple of differences worth knowing.
IPv6 blocks are announced by ASNs and registered with the same registries, so the same lookups work. A hosting company’s IPv6 range sits in the hosting company’s ASN just as its IPv4 range does.
The difference is that IPv6 space is plentiful, so hosting providers hand out large IPv6 blocks cheaply. Some proxy products offer huge numbers of IPv6 addresses for this reason. They’re often all from one or a few hosting ASNs, and platforms that group IPv6 by prefix see them as a small number of hosting networks, however many individual addresses are involved.
Consumer ISPs and mobile carriers that support IPv6 also have distinctive ranges in their own ASNs. A dual stack consumer line that exits over IPv6 carries its ISP’s ASN on that path too.
So if your proxy exits over IPv6, look that address up separately. It’s possible for an IPv4 exit to sit in a consumer ASN while the IPv6 exit from the same product sits somewhere else entirely.
Questions worth asking a provider
Once you know what the lookups show, you can ask proxy providers questions that their product pages rarely answer. How they respond is itself informative.
Which ASNs do your addresses come from? A provider selling residential or mobile addresses should be able to name the networks, or at least the carriers and ISPs, without hesitation.
Is any of your supply leased address space announced from your own ASN? There’s nothing inherently wrong with leasing, but you should know if “residential” means a block announced from a server rack.
How are residential exits sourced? If they come from real consumer devices, how do the device owners agree to share their connections, and can they withdraw?
Are ranges shared with other customers? If so, how many, and does the provider separate customers who run different kinds of traffic?
What happens when a range gets reclassified? Does the provider notice, and do they replace the affected addresses, or do customers find out through rising friction?
For mobile proxies, which carriers, which countries, and are the modems and SIMs dedicated per customer?
A provider that answers these clearly, even when the answers aren’t what you hoped, is easier to plan around than one that repeats marketing lines. A provider that won’t answer the first question at all has told you what the lookups will probably show.
Then check the answers yourself anyway. Look up a sample of exits. Compare the ASNs with what you were told. Trust the records over the conversation.
What to do this week
If you’ve never looked up the ownership of your proxy addresses, here’s where to start.
Pick three exit addresses from each proxy product you use. Look up their ASN and organisation name. Write down what kind of business each one is.
For anything sold as residential or mobile, check the ASN’s size and upstreams on a BGP toolkit, read the whois record and look at reverse DNS.
Flag any product where the ASN, the records and the claim don’t agree. Move valuable accounts off it first.
For mobile SIMs you run yourself, confirm the ASN matches the carrier you expect, and check the SIM’s carrier directly when it doesn’t.
Repeat the checks periodically. Ranges get reclassified, providers change their supply, and a pool that was clean last quarter can shift.
Keep the results in a simple ledger next to the accounts that use each address. When friction rises on a group of accounts, the ledger tells you whether they share a network.
The honest limit
An ASN lookup is the simplest and most reliable check in the whole network layer. It answers one question with very little doubt: who routes this address, and what kind of organisation are they? For hosting ranges the answer is rarely wrong.
It doesn’t answer whether an address is clean, whether a platform will accept it, or whether an account on it will survive. I can tell you what the public records show and how classification services use them. I can’t tell you how any platform weighs the result today.
What it does do is stop you from building on an address that announces itself as a server. That’s worth ten minutes before any account goes near a new range.
I run Singapore mobile proxy farms on consumer carrier SIMs, so the addresses my accounts use come back as the carrier’s own network, because that’s where they are. If you want the rest of the network picture, from fraud scores to proxy types, start on the Multi Account Ops home page.
Get new guides and videos first — join the Telegram channel.