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:
"Marseille"
region:
"Provence-Alpes-Côte d'Azur"
latitude:
43.29695
longitude:
5.38107

What is there? Unknown.

IPinfo Places

name:
"CEPAC Vélodrome"
category:
"stadium"
ssid:
"OrangeVelodrome"
latitude:
43.2698
longitude:
5.3959

Building-level context

Coverage

58 Venue Categories, and Growing

58

venue categories

2.7M

tagged venue IPs

240

countries

Travel & lodging

  • hotel IconHotel449.6K
  • campground IconCampground35.1K
  • airport IconAirport17.3K
  • travel_agency IconTravel Agency9.6K
  • bus_station IconBus Station8.1K
  • car_rental IconCar Rental5K
  • train_station IconTrain Station4.8K
  • subway_station IconSubway Station2.2K
  • ferry_terminal IconFerry Terminal871

Workspace

  • business_services IconBusiness Services121.9K
  • conference_center IconConference Center4.5K
  • coworking_space IconCoworking Space1.9K

Dining & nightlife

  • restaurant IconRestaurant294.8K
  • bar IconBar95.8K
  • coffee_shop IconCoffee Shop93.7K
  • nightclub IconNightclub5.6K

Shopping

  • retail IconRetail246.7K
  • grocery_store IconGrocery Store163K
  • home_improvement IconHome Improvement61.4K
  • convenience_store IconConvenience Store61.2K
  • mall IconShopping Mall51.2K
  • pharmacy IconPharmacy34.7K
  • market IconMarket8.7K

Automotive

  • car_services IconCar Services53.2K
  • car_dealer IconCar Dealer38.4K

Entertainment venues

  • casino IconCasino10.7K
  • theater IconTheater9.1K
  • stadium IconStadium5.3K
  • music_venue IconMusic Venue4.6K
  • cinema IconCinema4K
  • entertainment_venue IconEntertainment Venue3.7K
  • event_venue IconEvent Venue1.1K
Use cases

Put Places Context to Work

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

Observed, Then Matched

A venue tag has to get two factors right. The network has to be observed, and it has to be connected to the right place.

  • Observed from device data

    Places starts with the Wi-Fi networks that devices are connected to, including the SSID each network broadcasts. These observations provide a direct signal about the network and where it was seen.

  • Matched to a known venue

    Those observations are matched against public venue records, including OpenStreetMap, to identify the corresponding place, its name, and its category.

  • Verified by multiple signals

    Strong matches draw on evidence such as the venue operating the network's ASN, an SSID that identifies the venue, or an observed location that falls within the building footprint.

  • Refreshed as new evidence arrives

    We collect device observations continuously. When new evidence points an IP at a different venue, the mapping follows.

Venue Context at the Network Level

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

Already Built Into Your API

Places is included in IPinfo Core and Max, so venue context is returned in the same API call you already make. The granularity of the venue detail depends on the product.

Sample response

$curl https://api.ipinfo.io/lookup/90.85.9.13?token=$TOKEN
{
  "is_place": true,
  "place": {
    "name": "CEPAC Vélodrome",
    "category": "stadium",
    "ssid": "OrangeVelodrome",
    "latitude": 43.2698,
    "longitude": 5.3959
  }
}

See what's included in each

Pick a product 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

Get Places data through IPinfo Core and Max API responses, or access the full dataset as a custom file delivery for your own infrastructure.

Via API

Choose a product

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 included dataset.
See Bundle Pricing
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

58 categories · 2.7M IPs

Across 240 countries

Get started

Start Building With IPinfo Places

Go beyond geographic location with venue context that identifies the places associated with public Wi-Fi IPs. Access Places through IPinfo API products, or talk to our team about bringing the full dataset into your own infrastructure.

58 venue categories

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

2.7M tagged venue IPs

Every one matched to a specific venue, with coverage expanding as new data is observed.

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.

Grounded in observed network data

Venue tags are verified through Wi-Fi networks observed in device data, then matched to public venue records and confirmed by other supporting signals.

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 start from the Wi-Fi networks observed in device data, then get matched against public venue records such as OpenStreetMap, rather than from third-party or inferred location data.

    Strong matches draw on further evidence — the venue operating the network's ASN, an SSID that identifies the venue, or an observed location inside the building footprint — and we collect observations continuously, so the mapping follows when new evidence arrives.

  • 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 observed 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.