What is IPv4 vs IPv6?
IPv4 and IPv6 are the two internet addressing schemes. IPv4 uses 32-bit addresses (about 4.3 billion, now exhausted), written like 203.0.113.5. IPv6 uses 128-bit addresses (effectively unlimited), written like 2001:db8::1. Both are in active use, so detection and geolocation must handle each as first-class.
Last updated
IPv4 scarcity drove workarounds like NAT and CGNAT. IPv6 removes the shortage with a vastly larger space, and major VPNs, Tor, and Apple Private Relay all operate over IPv6.
A detection service that only handles IPv4 will silently miss a growing share of anonymizer traffic.
Does a VPN detector need to cover IPv6?
IPv4 and IPv6 are the two internet addressing schemes, and both are in active use. IPv4 uses 32-bit addresses and has run out of space. IPv6 uses 128-bit addresses with effectively unlimited room. A VPN detector needs to cover both. Major VPNs, Tor and Apple Private Relay all operate over IPv6, so a service that only understands IPv4 will silently miss a growing share of anonymizer traffic. It also gives a false sense of safety, because a visitor's IPv6 address may never be checked at all. Geolocation, provider data and network classification have to handle IPv6 as well. IPLogs treats IPv6 as first-class alongside IPv4 across detection, Tor coverage and the dashboard. It detects VPNs, proxies, Tor exits, datacenter addresses, iCloud Private Relay and Cloudflare WARP over both. Send a POST request to https://iplogs.com/v1/check with the address in the request body, using either kind of address. The check is free and needs no API key.
How IPLogs handles it
IPLogs treats IPv6 as first-class across detection, provider lists, Tor coverage, and the dashboard, alongside IPv4.