Skip to main content

The category

IP geolocation tells you where. Places tells you what.

Most IP data stops at a city and a set of coordinates. IPinfo Places identifies the venue behind the IP address and tells you what kind of place it is — the context that turns a point on a map into a real-world location.

Standard IP geolocation

city:
"Romulus"
region:
"Michigan"
latitude:
42.22226
longitude:
-83.3966

What is there? Unknown.

IPinfo Places

name:
"Detroit Metropolitan Airport"
category:
"airport"
ssid:
"Detroit Airport Wi-Fi"
latitude:
42.2086
longitude:
-83.3531

Building-level context

Coverage

56 venue categories, and growing

56

venue categories

2.1M

tagged venue IPs

237

countries

Transit & Travel

  • in_flight IconIn-Flight21.4K
  • in_transit IconIn Transit20.6K
  • airport IconAirport9K
  • travel_agency IconTravel Agency8.8K
  • bus_station IconBus Station7.4K
  • car_rental IconCar Rental4.3K
  • train_station IconTrain Station3.7K
  • subway_station IconSubway Station2.1K
  • ferry_terminal IconFerry Terminal761

Accommodation

  • hotel IconHotel347.1K
  • campground IconCampground25.5K
  • mobile_home_park IconMobile Home Park218

Entertainment & Nightlife

  • casino IconCasino9.2K
  • music_venue IconMusic Venue6.5K
  • theater IconTheater6.1K
  • nightclub IconNightclub6.1K
  • cinema IconCinema4K
  • entertainment_venue IconEntertainment Venue3K
  • event_venue IconEvent Venue840

Sports & Recreation

  • gym IconGym39.2K
  • sports_center IconSports Center34.2K
  • golf_course IconGolf Course9K
  • stadium IconStadium4.9K
  • water_park IconWater Park4.7K
  • theme_park IconTheme Park2.8K
  • ski_resort IconSki Resort2K

Attractions & Culture

  • museum IconMuseum10.9K
  • library IconLibrary7.2K
  • attraction IconAttraction3.3K
  • zoo IconZoo664
  • botanical_garden IconBotanical Garden409
  • aquarium IconAquarium281

Food & Drink

  • restaurant IconRestaurant265.5K
  • bar IconBar84.1K
  • coffee_shop IconCoffee Shop77.1K

Use cases

Real-world context, applied

Venue-level context adds precision to targeting, identity, and risk enrichment.

  • Ad tech & audience targeting

    Attribute traffic to place types like airports, hotels, and stadiums. Power contextual targeting and location analytics without relying on device GPS or cookies.

  • Enrichment, identity & risk

    Feed granular venue signals into your own models. Sharpen lending-risk scoring, fraud detection, and identity resolution with the place behind each IP.

  • Cybersecurity

    Distinguish public venue networks like libraries and airports from private ones. Speed up triage, enrichment, and allowlisting with venue context.

Why IPinfo

They guess. We measure.

Most location data is inferred from third-party sources and stitched-together registries. Places tags are verified through ProbeNet, IPinfo's internet measurement platform, so a venue tag reflects a network we observed rather than one we assumed.

  • Active measurement, not inference

    Probes observe how a network actually behaves, from real points of presence.

  • Global coverage

    A worldwide point-of-presence footprint validates venue tags across regions.

  • Continuously re-verified

    Measurements refresh, so a venue tag tracks the network as it changes.

The measurement network

1,390+ points of presence across 170+ countries, measuring the networks behind the venues we tag.

It's about places, not people

Places identifies venue networks — the Wi-Fi and infrastructure at a hotel, an airport, or a stadium — not individuals. It contains no personal data and no PII. You learn what kind of place an IP belongs to, never who is behind it.

Integration

No new endpoint. It's in your bundle.

The Places API is included in IPinfo Core and Max, returned in the same API call you already make. No new endpoint, no second request — and the depth of the venue detail follows your tier.

Sample response

$ curl https://api.ipinfo.io/lookup/206.121.37.170?token=$TOKEN
1
2
3
4
5
6
7
8
9
10
11
{
ip:"206.121.37.170",
is_place:true,
place:{
name:"Detroit Metropolitan Airport",
category:"airport",
ssid:"Detroit Airport Wi-Fi",
latitude:42.2086,
longitude:-83.3531
}
}

Depth scales with your tier

Pick a tier to see exactly what its response carries, all in the same API call.

Choose a bundle tier to sample
See Pricing

Access

Two ways to get Places

Want it in your API responses? It is in the bundles. Want the dataset as a file for your own infrastructure? That is a separate, custom offering — the API bundles do not include it.

Via API

Get a bundle

Places is built into IPinfo Core and Max and returned in the same API call you already make — no new endpoint. Enrich one IP or many in batch, alongside geolocation and every other dataset in the bundle.
As a file

Talk to sales

Need the full dataset as a file to run inside your own infrastructure? That is a custom offering, scoped and sold separately. Our team will work out the delivery with you.

API access

IPinfo Core and Max

Included in the bundle, no separate request

File access

Custom offering

Scoped with sales, not part of the bundles

Coverage

56 categories · 2.1M IPs

Across 237 countries

Get started

Start building with IPinfo Places

Places is live and built into IPinfo Core and Max, returned in the API call you already make. Start from a plan, or talk to us about the dataset as a file.

56 venue categories

From airports and hotels to stadiums, transit stations, and retail, with new categories added as the taxonomy grows.

2.1M tagged venue IPs

Every one matched to a real-world venue, with coverage expanding as new measurements land.

API in the bundle

Included in Core and Max via the API. Need it as a file instead? That is a custom offering — contact sales.

Built on active measurement

Venue tags are verified through IPinfo's own internet measurement platform, not third-party guesswork.

See Pricing

FAQ

Frequently asked questions

  • No. Places is part of the IPinfo Core and Max bundles and comes back in the same lookup you already make — there is no second endpoint and no second request.

    It works in batch too, so you can enrich many IPs with venue context alongside geolocation and the rest of the bundle.

  • New Core and Max subscriptions include Places.

    If you already have one of those bundles, Places is opted into for your account, and the venue attributes then appear in the responses you are already requesting.

  • The response says so plainly: the venue flag is false and the venue object is empty. Most IP addresses are not public venue networks, so this is the common case.

    That means you can branch on the flag rather than guessing from a missing field.

  • No. Places describes venue networks — the Wi-Fi and infrastructure at a hotel, an airport, or a stadium — and contains no personal data and no PII.

    You learn what kind of place an IP address belongs to, never who is behind it.

  • Venue tags come from ProbeNet, IPinfo's own internet measurement platform, rather than from third-party or inferred location data.

    Measurements refresh on a schedule, so a tag tracks the network it describes and is retired when that network changes.

  • Yes, deliberately. Categories that describe people at a school, a place of worship, or a medical facility are withheld from the dataset we publish.

    The taxonomy on this page is the full set we make available, and it grows as new categories are measured and reviewed.

  • Yes, as a custom offering scoped with our team. The API bundles are API-only and do not include the file.

    Contact sales and we will work out the coverage and delivery your infrastructure needs.