IP Address Lookup
Your public address, where the network edge places it, which network owns it and whether that network is a home connection or a datacenter — then the same lookup for any proxy exit you paste in. Free, no signup.
- Address read at the edge
- Network table kept on our own server
- No signup
Reading this connection at the edge…
Look up another address
A proxy exit, a server, anything public. Owner, network type and reverse DNS — not location.
Now give every account its own device.
A clean browser is still one browser. Sendwin runs each profile in isolation with its own fingerprint, cookies and proxy, so the accounts you work on never look like they came from the same machine.
- Isolated profiles, each with its own fingerprint and cookies
- A proxy per profile, with the timezone bound to the proxy country
- Windows, macOS and Linux — plus cloud sessions when you need them
The free plan includes 10 minutes of cloud browsing a day.
What an address says before the page loads
Every request you make carries a source address, and the site on the other end knows three things about it before your page has even loaded: roughly where it is, who it belongs to, and what kind of network that owner runs. The last one is the part most people miss. A home broadband line, a mobile carrier and a cloud server all hand out perfectly valid addresses, but a site that scores risk treats them very differently — an account that only ever signs in from a hosting range looks like software, whatever the browser in front of it says.
This page shows you exactly that view. Your address is read at the network edge, the country (and the city, where the edge publishes it) comes from the same place, and the owning network is resolved against a routing table kept on our own server, so the lookup never hands your address — or your proxy's — to a third-party API. Paste any other public address, such as the exit of a proxy you are evaluating, and the same table answers for it. The one thing it cannot do for another address is place it on a map: the table knows who owns a block, not where each address in it is being used, and it does not pretend otherwise.
Residential, hosting, unknown: how the network type is decided
Every routed address belongs to an autonomous system, a numbered network run by one organisation, and the registry publishes a short description with each number. The type shown here comes from two rules applied to that record. A curated list of well-known cloud and hosting providers — the large public clouds, the big dedicated-server and VPS companies, the content networks — decides first. If the number is not on it, the description is read for the words hosting companies and internet providers use to name themselves. The row always says which rule fired, because the answer is a strong hint rather than a verdict: a block can be resold, a telecom can run a cloud, and a name can say nothing at all, which the page reports as unclassified rather than guessing.
What the edge knows about location, and what it does not
The country is read from the network edge on every request. City, region and coordinates are published by the edge too, but only where that data is switched on, so the page states its precision — city or country — instead of showing a blank city as though it were unknown. A country-level placement is reliable; a city-level one is an estimate that can land a connection in the next town or the wrong side of a time zone boundary. Both are about the address, never about you: the edge sees a source address and nothing else.
Proxy headers and the anonymity verdict
When a proxy forwards a request it may add headers on the way — Via, X-Forwarded-For, Forwarded and a dozen less common names. The page lists any that arrived, with the edge's own bookkeeping already removed, and reduces them to one word. Transparent means a header carried another public address, so the site sees both the exit and whatever is behind it. Anonymous means proxy headers arrived but revealed no other address: the proxy is visible, the origin is not. No headers at all is reported as direct, and that word covers two cases the outside cannot separate — a plain connection and a proxy that adds nothing, which vendors call elite.
Where each answer comes from
- 1
Read the address at the edge
The page asks our server how this connection looks from outside. The address and the country come from the network edge, which sees the real source of the request.
- 2
Look the block up offline
The address is matched against a routing table on our own server, updated weekly, which names the network, its registered country and — by rule — its type. No third party sees the address.
- 3
Compare with this browser
The browser's time zone and language are read here and set beside the address. A clock and a language that fit the country are what a site expects; a mismatch is what it notices.
Other free checks
An address is one signal. These read the others a site compares it with.
- WebRTC Leak TestCheck if WebRTC exposes your real IPRun the check
- Timezone Leak TestDoes your clock match the country of your IP?Run the check
- HTTP Headers TestSee the headers your browser sends, and whether they agree with JavaScriptRun the check
- Proxy CheckerClean up a proxy list before you import itRun the check
IP address FAQ
Residential versus datacenter, what a location can and cannot say, and what the server keeps.
Every site you open records it, and most of them use it for more than routing. It places you in a country for content and pricing, it links sessions that share it, and it feeds reputation scores that ask how many accounts, how much abuse and what kind of network sit behind the same address. That last question is why the network type on this page matters more than the number itself.
From the network that announces it. Hosting providers and internet providers register their address blocks under their own names, and most of them say what they are in the description. The page checks a list of well-known cloud and hosting networks first, then reads the description for the words each kind of company uses, and shows you which rule applied. It cannot see how a specific address is being used today, so a residential block that has been resold to a proxy service will still read as residential — that is the limit of any name-based check, ours included.
Because they answer different questions. The registered country is where the network operator is registered, and a US cloud provider runs servers in Frankfurt and Singapore under the same registration. The location comes from the edge's placement of the address itself. When the two disagree for a hosting network, the location is the one to believe; for a consumer ISP they almost always agree.
No lookup is written anywhere. The server reads the request, answers it and forgets it; the only thing it keeps in memory for a while is the reverse-DNS name of an address, which is public data, so a second visitor asking about the same address gets a faster answer. Rate limiting counts requests per address for a minute, the same way the other tools here do, and that counter is not a log.
Any public address, yes — that is what the second box is for, and the usual reason is checking a proxy's exit before trusting it with an account. You get the network, its type, its registered country and its reverse-DNS name. You do not get a location, because our table does not hold one, and private or reserved addresses are refused because there is nothing routed to look up.
The name an address's owner has attached to it. Internet providers tend to encode the line type and the region — a dynamic cable customer in one city looks very different from a static business line — and hosting providers tend to encode the server or the product. Many mobile carriers publish no name at all. It is one more clue about what kind of connection an address is, readable by anyone, so it is shown here.
Because the address and the browser answer the same question independently. The address says which country the connection exits in; the browser's clock says which zone it thinks it is in. A site comparing the two sees a US exit with a Kyiv clock as a connection that is not what it claims, and no amount of proxy quality fixes that. The row treats same-country differences gently — many countries span several zones — and only calls a different-country pairing a contradiction.
A profile carries its own proxy, and the time zone, locale and language follow that proxy's country automatically, so the address and the browser tell the same story without anyone setting it by hand. Open this page inside a profile to see the agreement rows pass.
Still have questions? Talk to us →
How to read the network type
Network type is a classification of the network's registered name against a list and a set of words, and the row always says which rule produced it. It is a strong hint about how a site will score the address, not a statement about how the address is used today. Location comes from the network edge and is about the address, not the person. Nothing here compares you with other visitors, because we hold no such data and would not print a figure we cannot measure.
A proxy per profile, with the browser to match.
Sendwin binds each profile's time zone, locale and language to its proxy's country, so the address and the browser tell the same story every time it opens. Free for 30 days on Windows, macOS and Linux.
30-day free trial · $0 today · cancel anytime — your profiles stay on your machine