Skip to content
VPNDetection
Log inGet a free API key
HomeBogon IPs
Reference

Bogon IP Address Ranges

Bogon IPs are those reserved for special use, e.g. private networking, loopbacks, documentation and testing. They shouldn't appear on the public internet. Ranges that haven't been allocated yet are bogons too.

A bogon address doesn't belong to a host or network on the public internet, so our datasets have nothing to observe there: no VPN, proxy, hosting, Tor, relay or CDN record exists for any address in these ranges.

IPv4 bogon ranges

Reserved by the IETF or IANA, and never routed on the public internet.

16 netblocks
NETBLOCKDESCRIPTIONREFERENCE
0.0.0.0/8"This" networkRFC 1122
10.0.0.0/8Private-use networksRFC 1918
100.64.0.0/10Carrier-grade NATRFC 6598
127.0.0.0/8LoopbackRFC 1122
169.254.0.0/16Link localRFC 3927
172.16.0.0/12Private-use networksRFC 1918
192.0.0.0/24IETF protocol assignmentsRFC 6890
192.0.2.0/24TEST-NET-1RFC 5737
192.88.99.2/326a44 relay anycast addressRFC 6751
192.168.0.0/16Private-use networksRFC 1918
198.18.0.0/15Network interconnect device benchmark testingRFC 2544
198.51.100.0/24TEST-NET-2RFC 5737
203.0.113.0/24TEST-NET-3RFC 5737
224.0.0.0/4MulticastRFC 5771
255.255.255.255/32Limited broadcastRFC 8190
240.0.0.0/4Reserved for future useRFC 1112

IPv6 bogon ranges

The equivalent reservations in IPv6 address space.

32 netblocks
NETBLOCKDESCRIPTIONREFERENCE
::/128Node-scope unicast unspecified addressRFC 4291
::1/128Node-scope unicast loopback addressRFC 4291
::ffff:0:0/96IPv4-mapped addressesRFC 4291
::/96IPv4-compatible addressesRFC 4291
64:ff9b::/96IPv4/IPv6 translation, the NAT64 well-known prefixRFC 6052
64:ff9b:1::/48Local-use IPv4/IPv6 translationRFC 8215
100::/64Remotely triggered black hole addressesRFC 6666
100:0:0:1::/64Dummy IPv6 prefixRFC 9780
2001:2::/48BenchmarkingRFC 5180
2001:10::/28Overlay routable cryptographic hash identifiers (ORCHID)RFC 4843
2001:db8::/32Documentation prefixRFC 3849
3fff::/20Documentation prefixRFC 9637
5f00::/16Segment Routing over IPv6 (SRv6) SIDsRFC 9602
fc00::/7Unique local addresses (ULA)RFC 4193
fe80::/10Link-local unicastRFC 4291
fec0::/10Site-local unicast (deprecated)RFC 3879
ff00::/8Multicast (ff0e::/16 is global scope and may appear on the public internet)RFC 4291
2001:1::/32IETF protocol assignments (2001::/23, outside Teredo)RFC 2928
2001:2::/31IETF protocol assignments (2001::/23, outside Teredo)RFC 2928
2001:4::/30IETF protocol assignments (2001::/23, outside Teredo)RFC 2928
2001:8::/29IETF protocol assignments (2001::/23, outside Teredo)RFC 2928
2001:20::/27IETF protocol assignments (2001::/23, outside Teredo)RFC 2928
2001:40::/26IETF protocol assignments (2001::/23, outside Teredo)RFC 2928
2001:80::/25IETF protocol assignments (2001::/23, outside Teredo)RFC 2928
2001:100::/24IETF protocol assignments (2001::/23, outside Teredo)RFC 2928
::/3Unallocated: outside global unicast (2000::/3)RFC 4291
4000::/3Unallocated: outside global unicast (2000::/3)RFC 4291
6000::/3Unallocated: outside global unicast (2000::/3)RFC 4291
8000::/3Unallocated: outside global unicast (2000::/3)RFC 4291
a000::/3Unallocated: outside global unicast (2000::/3)RFC 4291
c000::/3Unallocated: outside global unicast (2000::/3)RFC 4291
e000::/3Unallocated: outside global unicast (2000::/3)RFC 4291

IPv6 additional bogon ranges

The 6to4 (RFC 3056) and Teredo (RFC 4380) forms of the IPv4 bogon ranges above. They aren't official IPv6 bogons, but they're treated as bogons for the same reason.

32 netblocks
NETBLOCKDESCRIPTIONIPV4 SOURCE
2002::/246to4 bogon0.0.0.0/8
2002:a00::/246to4 bogon10.0.0.0/8
2002:6440::/266to4 bogon100.64.0.0/10
2002:7f00::/246to4 bogon127.0.0.0/8
2002:a9fe::/326to4 bogon169.254.0.0/16
2002:ac10::/286to4 bogon172.16.0.0/12
2002:c000::/406to4 bogon192.0.0.0/24
2002:c000:200::/406to4 bogon192.0.2.0/24
2002:c058:6302::/486to4 bogon192.88.99.2/32
2002:c0a8::/326to4 bogon192.168.0.0/16
2002:c612::/316to4 bogon198.18.0.0/15
2002:c633:6400::/406to4 bogon198.51.100.0/24
2002:cb00:7100::/406to4 bogon203.0.113.0/24
2002:e000::/206to4 bogon224.0.0.0/4
2002:f000::/206to4 bogon240.0.0.0/4
2002:ffff:ffff::/486to4 bogon255.255.255.255/32
2001::/40Teredo bogon0.0.0.0/8
2001:0:a00::/40Teredo bogon10.0.0.0/8
2001:0:6440::/42Teredo bogon100.64.0.0/10
2001:0:7f00::/40Teredo bogon127.0.0.0/8
2001:0:a9fe::/48Teredo bogon169.254.0.0/16
2001:0:ac10::/44Teredo bogon172.16.0.0/12
2001:0:c000::/56Teredo bogon192.0.0.0/24
2001:0:c000:200::/56Teredo bogon192.0.2.0/24
2001:0:c058:6302::/64Teredo bogon192.88.99.2/32
2001:0:c0a8::/48Teredo bogon192.168.0.0/16
2001:0:c612::/47Teredo bogon198.18.0.0/15
2001:0:c633:6400::/56Teredo bogon198.51.100.0/24
2001:0:cb00:7100::/56Teredo bogon203.0.113.0/24
2001:0:e000::/36Teredo bogon224.0.0.0/4
2001:0:f000::/36Teredo bogon240.0.0.0/4
2001:0:ffff:ffff::/64Teredo bogon255.255.255.255/32

Common questions

Read the docs →API reference →Email support →
On this page

Should I filter bogons?

At your network's edge, yes: a packet arriving from the internet with a bogon source address is misconfigured or spoofed, and dropping it is standard practice, as is refusing a BGP announcement of bogon space. Inside your own network private ranges are ordinary traffic, so filter at the border.

00 · No key

Start without signing up.

Paste it into a terminal. No account needed. 1,000 lookups a day per address, answering ip and is_vpn.

curl "https://api.vpndetection.io/146.70.116.130"
{
  "ip": "146.70.116.130",
  "is_vpn": true
}
01 · Free key

Sign up and get 50,000 requests a month.

No card and no sales call: the key is issued on signup.
Every request flags VPN IPs.
Upgrade only when you outgrow the allowance.
Get a free API keySee pricing