IP geolocation
Enter an IP — or check your own connection — to see the country, city, ISP and VPN/proxy status behind it, plotted on an interactive map. Built for fraud screening, compliance and localization.
IP location result is ready below.
104.23.197.229
Approximate address
Columbus, Ohio, 43215, United States of America
Estimated from IP location data
This is the public IP of your current connection. Enter any other IP above to look it up.
BinCheck API
This free website lookup accepts 6–8 digit BINs and shows core issuer fields only. The BinCheck API returns clean, complete JSON — up to 11-digit BIN/IIN, premium issuer flags, bank contacts, and full BIN+IP match data.
An IP address is the return address of every online request. Geolocating it tells you the country, region and city a visitor, customer or order is connecting from, the network and ISP behind it, and whether the connection is masked by a VPN, proxy or data center — a fast read on where someone really is, before you trust, ship or personalize.
Every device on the internet is reachable through a public IP address, and that address is allocated to a network operator in a known place. Geolocation databases map the address to a country, region, city, approximate coordinates and time zone, plus the ISP or hosting provider that owns the range. This tool runs that lookup in one step and plots the result on a map.
Location alone is a hint, not a verdict: a customer can travel, an office can route through a central gateway, and a VPN can move a connection to another country entirely. That is why the result also flags anonymized traffic — so "where the IP says it is" and "whether that location can be trusted" stay two separate, visible questions.
The result leads with a map and a plain-language location summary, then breaks the record into three groups: where the IP is, the network behind it, and its proxy / reputation status. Here is what each field means.
| Field | Group | What it tells you |
|---|---|---|
| Country | Location | The country the IP resolves to — the most reliable field |
| Region & city | Location | Finer location within the country (accuracy varies) |
| Coordinates | Location | Approximate latitude / longitude, plotted on the map |
| Postal / ZIP | Location | Approximate postal code for the area |
| Time zone & local time | Location | The connection's time zone and current local time |
| ISP / carrier | Network | The internet provider or carrier that owns the IP |
| ASN | Network | Autonomous System number — the network's routing identity |
| Proxy / VPN flag | Proxy | Whether the IP is a known anonymizer |
| Data-center flag | Proxy | Whether the IP belongs to a hosting provider, not a home ISP |
| Threat / usage type | Proxy | Reputation and how the range is typically used |
Fields map 1:1 to the JSON the IP geolocation API returns. Location fields are best-effort estimates; the proxy fields describe the connection, not the person.
IP geolocation is reliable at the country level and good to city level for most consumer connections, but it is an estimate, not a GPS fix. Knowing where it is strong and where it is soft keeps you from over-trusting a single data point.
| Field | Typical accuracy | Caveat |
|---|---|---|
| Country | High | Rarely wrong for un-proxied consumer IPs |
| Region / state | Medium–high | Softer for mobile and shared carrier ranges |
| City | Medium | Can resolve to a nearby hub or the ISP's registered city |
| Coordinates | Approximate | Area-level, not a street address or a device GPS fix |
| Behind a VPN / proxy | Reflects the exit, not the user | Location is the anonymizer's, not the person's |
| Mobile / carrier-grade NAT | Low–medium | One gateway can serve a whole region |
Treat the location as a strong signal to weigh, not a precise address. Accuracy is highest for fixed-line consumer connections and lowest for mobile carriers, corporate ranges and anonymized traffic.
Where a request comes from is a business signal you already receive on every visit — geolocation just makes it legible. From stopping cross-border card fraud to charging the right tax, honoring content licenses and speaking the customer's language, the same lookup pays off across the whole funnel.
Where a request originates is one of the oldest fraud signals there is. An order shipping to one country but connecting from another — or arriving over a VPN, proxy or data-center IP — is worth a second look before you authorize or fulfil. Geolocating the IP lets you hold the risky ones for review instead of eating a chargeback: the lost goods, the sale, and a $15–$100 dispute fee.
Streaming rights, promotions, betting and regulated products are sold by territory. Resolving the visitor's country lets you show, hide or gate content to stay inside your license and local law — and keep the audit trail that proves you did.
VAT, sales tax and sanctions screening all turn on jurisdiction. A location read gives you a first-pass answer to "which rules apply to this customer" before checkout, so pricing and compliance start from the right place.
Meet visitors where they are: default to their currency, surface the right language, route them to a regional support queue and show local delivery options. Small relevance wins early in the funnel compound into conversion.
Know which regions your visitors and clicks actually come from, catch campaigns whose "local" traffic is really a data center, and clean geo bots out of your analytics so the numbers you optimize against are real.
When a ticket, chargeback or abuse report lands, the IP's location, ISP and proxy status is instant context — corroborating a customer's story, or explaining why a login looked off, without a back-and-forth.
A location is only as trustworthy as the connection behind it. The lookup screens the IP against a VPN/proxy database and flags data-center ranges, because a masked connection can place itself anywhere it likes.
| Signal | Why it matters |
|---|---|
| Proxy / VPN detected | The visitor is deliberately masking their true location |
| Data-center IP | Genuine consumers rarely browse or pay from a hosting provider |
| Country ≠ shipping / account country | A classic cross-border fraud and abuse pattern |
| Threat-listed IP | The address has a history tied to abuse or attacks |
| High-risk usage type | The range is associated with scraping, spam or automation |
No account, no install. Enter any IP — or check your own connection in one tap — and get the map, address and full record back in about a second, all resolved server-side.
Paste any public IPv4 or IPv6 address — from an order, a log line or a sign-up — or tap "Use my IP" to look up your own connection instantly. No account, no full personal data.
The IP is resolved to a country, region, city and approximate coordinates, matched to its ISP/ASN, screened against a VPN/proxy database and reverse-geocoded to a readable address — all on our servers.
The location drops onto an interactive map that zooms to the point, with the address, network and proxy status laid out beside it so you can decide what to do with the visit.
The tool above is powered by the same endpoint our API serves. When you need location on every request — inside checkout, a risk engine, analytics or a content gate — the IP geolocation endpoint returns the country, region, city, coordinates, ISP and proxy flags as one JSON response.
We treat accuracy and privacy as features, not fine print. Here is where the data comes from, what the location really measures, and what happens to the IP you enter.
Location is resolved from self-hosted IP2Location geolocation and IP2Proxy VPN/proxy tables plus ASN/ISP registry data, with an optional OpenStreetMap reverse-geocode for the readable address. No request is bounced to a third-party lookup from your browser — the lookups run on our servers.
Geolocation maps an IP to where its network is registered and typically served, which is close to — but not the same as — where a person physically is. It is accurate to the country for almost every un-proxied IP and to the city for most, and it explicitly flags VPNs and proxies so you know when the location is the anonymizer's, not the user's.
The IP you enter is used only to run the lookup. It is checked for location and reputation, not logged against you or tied to an identity. An IP is network routing data, not a name or an account.
Data sources · updated
This IP location tool returns best-effort geolocation, network and reputation data for an IP address. Location is an estimate, not a precise or verified address: accuracy varies by connection type, VPNs and proxies relocate the apparent location, and databases are never 100% complete. It maps an IP to an area and a network, not to a named person — only the ISP can link an IP to a subscriber, and only under lawful process. Use the result as one signal among several for risk, compliance and localization decisions, and submit only IPs you are permitted to check.
IP geolocation is the process of mapping an IP address to a real-world location — country, region and city — along with the network operator behind it. It works because IP ranges are allocated to providers in known places. It is widely used to detect fraud, apply regional rules, localize content and understand where traffic comes from.