beta

API

Every page is built from these endpoints. Send an API key as Authorization: Bearer vpndb_…; create one under Account.

This page

GET /api/v1/meta

curl -s -H 'Authorization: Bearer vpndb_EXAMPLE_NOT_A_REAL_KEY' \
  '/api/v1/meta'

All endpoints

GET /api/v1/ip/{ip}Who operates an address
GET /api/v1/ip/{ip}/historyEvery week of an address
GET /api/v1/prefix/{cidr}Any range, and who is inside it
GET /api/v1/prefix/{cidr}/addressesEvery address of a prefix, in a window
GET /api/v1/prefix/{cidr}/timelineHow a prefix was probed, day by day
GET /api/v1/asn/{asn}A network and its providers
GET /api/v1/asn/{asn}/networksEvery prefix of a network
GET /api/v1/org/{id}A company and all its networks
GET /api/v1/org/{id}/networksEvery prefix of a company
GET /api/v1/country/{cc}The infrastructure located in a country
GET /api/v1/countriesEvery country at a glance
GET /api/v1/service/{tag}A provider's profile
GET /api/v1/service/{tag}/networksEvery network a provider exits from
GET /api/v1/servicesEvery provider at a glance
GET /api/v1/torThe Tor network at a glance
GET /api/v1/tor/relaysEvery running Tor relay, for detection
POST /api/v1/bulkMany addresses at once
GET /api/v1/searchResolve free text
GET /api/v1/suggestSuggestions as you type
GET /api/v1/metaThe dataset
GET /api/v1/openapi.yamlThis specification
GET /api/v1/sourcesWhere the data comes from
API documentationOpenAPI specification
Sign in

Entities

The Tor network

Tor exits and relays from the Tor Project's own data: where Tor leaves, who runs it, and Tor over VPN.

Tor in the header shows where Tor traffic leaves the internet: every exit address with its network, country and prefix, by its share of all Tor exit traffic; the relays by hosting network; and a list of every running relay to match connections against. The data is the Tor Project's own — the relay list, fetched hourly, and the daily exit lists since November 2024 — placed with our routing and country tables. Both are public domain (CC0).

The map

The map shades each country by exit traffic — its share of all Tor exit traffic, where Tor users' traffic actually leaves — or, switched over, by exit addresses, how many there are. The two differ: the United States hold the most exit addresses, the Netherlands and Germany carry more of the traffic. Each country's tooltip gives both. Countries are where DB-IP locates each exit address. A click on a country — on the map or in the country table — narrows the page to it: the figures, the exit networks and prefixes, the relays and the exits reached through a VPN are then that country's, and shares remain shares of all Tor exit traffic. The line under the map says which country is chosen, links its country page, and clears the choice.

An address, a network, a prefix

An address that is or was a Tor exit answers as one: type TOR, no provider, the days it exited Tor traffic month by month, and the relays running there with their role and port. A network or prefix holding Tor exits or relays shows them in a Tor box, even where no VPN or proxy provider is known in it.

Tor over VPN

Some VPN providers route single servers into Tor (ProtonVPN's Tor servers, NordVPN's Onion over VPN). Our probing through such a server leaves from a Tor exit. That is Tor traffic of the VPN's customer, not an exit of the VPN: a sighting while the address was a Tor exit (its days on the Tor Project's exit lists, gaps in those lists of up to 60 days, and 30 days either side) counts for no provider anywhere — not in the attribution, not in the networks and figures of the provider, not in interpolation. It is shown as reached via instead.

Detection

A connection from inside your network to a relay's address and port is a Tor client, or software that brings its own Tor. Every running relay counts, not only exits: the guards are the first hop of every client. The list is on the Tor page as CSV and through GET /api/v1/tor/relays. At large hosters relays share their networks with ordinary customers: match address and port, never the whole network.