Operating-system and browser privacy relays.

The database's schema and metadata are documented carefully. Multiple formats are available, including CSVGZ and MMDB.

One call gets you the current Relay IP build. Every official client wraps it three ways — straight to disk, a signed link you hand to your own runner, or bytes in memory — and each verifies the published checksum before it hands the build back.

download(path)

Streams the current build to disk and verifies the published checksum before it returns.

url(expires)

A time-limited signed link — hand it to your own downloader, a job runner or a CDN pull.

bytes()

The build in memory, for pipelines that never touch a filesystem.

build()

Build id, published time, row count, byte size and all four checksums.

format

csvgz, or mmdb where Relay IP publishes it.

since(build)

Poll the build id first and fetch only when it changed; an unchanged poll costs nothing.

PythonNode.jsGoPHPJavacURL

from vpndetection import Client
 
client = Client(os.environ["VPNDETECTION_API_KEY"])
db = client.database("relay_ip_v1", format="csvgz")
 
db.download("relay_ip_v1.csv.gz")   # to disk
url = db.url(expires=3600)     # signed link
blob = db.bytes()              # in memory
 
db.build().published           # last build

download.pypip install vpndetection

Also available for C#, Ruby, Rust, Swift, Erlang, Zig and Perl. See all on GitHub →

Getting your hands on it.

Where Relay IP earns its place in a risk stack — and what each of these decisions needs from the data rather than from a score.