Bogon IP Addresses

Sheharyar Malik
By Sheharyar Malik Senior Software Engineer
Posted on December 6, 2024 | 3 min read
Bogon IP Addresses
Back to All Posts

Bogon IP Addresses

Bogon IP Addresses are the set of IP Addresses not assigned to any entity by Internet Assigned Numbers Authority (IANA) and RIR (Regional Internet Registry). This unallocated address space is called the bogus space. Bogons also include reserved private address and link-local address ranges (Martian Packets). IANA might assign Bogon IP addresses to an entity or RIR with the passage of time.


Here are the bogon IP address ranges:


IPv4 Bogon Ranges

NetblockDescription
0.0.0.0/8"This" network
10.0.0.0/8Private-use networks
100.64.0.0/10Carrier-grade NAT
127.0.0.0/8Loopback
127.0.53.53Name collision occurrence
169.254.0.0/16Link local
172.16.0.0/12Private-use networks
192.0.0.0/24IETF protocol assignments; contains more-specific exceptions. Do not block the whole /24 without honoring the IANA registry.
192.0.2.0/24TEST-NET-1
192.168.0.0/16Private-use networks
198.18.0.0/15Network interconnect device benchmark testing
198.51.100.0/24TEST-NET-2
203.0.113.0/24TEST-NET-3
224.0.0.0/4Multicast
240.0.0.0/4Reserved for future use
255.255.255.255/32Limited broadcast

IANA marks two addresses inside 192.0.0.0/24 as globally reachable: 192.0.0.9/32 (Port Control Protocol anycast, RFC 7723) and 192.0.0.10/32 (TURN anycast, RFC 8155). Derive operational filters from the current IANA IPv4 Special-Purpose Address Registry, not this simplified table.


IPv6 Bogon Ranges

NetblockDescription
::/128Node-scope unicast unspecified address
::1/128Node-scope unicast loopback address
::ffff:0:0/96IPv4-mapped addresses
::/96IPv4-compatible addresses
100::/64Remotely triggered black hole addresses
2001:10::/28Overlay routable cryptographic hash identifiers (ORCHID)
2001:db8::/32Documentation prefix
fc00::/7Unique local addresses (ULA)
fe80::/10Link-local unicast
fec0::/10Site-local unicast (deprecated)
ff00::/8Multicast (Note: ff0e::/16 is global scope and may appear on the global internet.)

IPv6 Additional Bogon Ranges

NetblockDescription
2002::/246to4 bogon (0.0.0.0/8)
2002:a00::/246to4 bogon (10.0.0.0/8)
2002:7f00::/246to4 bogon (127.0.0.0/8)
2002:a9fe::/326to4 bogon (169.254.0.0/16)
2002:ac10::/286to4 bogon (172.16.0.0/12)
2002:c000::/406to4 bogon (192.0.0.0/24)
2002:c000:200::/406to4 bogon (192.0.2.0/24)
2002:c0a8::/326to4 bogon (192.168.0.0/16)
2002:c612::/316to4 bogon (198.18.0.0/15)
2002:c633:6400::/406to4 bogon (198.51.100.0/24)
2002:cb00:7100::/406to4 bogon (203.0.113.0/24)
2002:e000::/206to4 bogon (224.0.0.0/4)
2002:f000::/206to4 bogon (240.0.0.0/4)
2002:ffff:ffff::/486to4 bogon (255.255.255.255/32)
2001::/40Teredo bogon (0.0.0.0/8)
2001:0:a00::/40Teredo bogon (10.0.0.0/8)
2001:0:7f00::/40Teredo bogon (127.0.0.0/8)
2001:0:a9fe::/48Teredo bogon (169.254.0.0/16)
2001:0:ac10::/44Teredo bogon (172.16.0.0/12)
2001:0:c000::/56Teredo bogon (192.0.0.0/24)
2001:0:c000:200::/56Teredo bogon (192.0.2.0/24)
2001:0:c0a8::/48Teredo bogon (192.168.0.0/16)
2001:0:c612::/47Teredo bogon (198.18.0.0/15)
2001:0:c633:6400::/56Teredo bogon (198.51.100.0/24)
2001:0:cb00:7100::/56Teredo bogon (203.0.113.0/24)
2001:0:e000::/36Teredo bogon (224.0.0.0/4)
2001:0:f000::/36Teredo bogon (240.0.0.0/4)
2001:0:ffff:ffff::/64Teredo bogon (255.255.255.255/32)

These 6to4 and Teredo rows are derived from the IPv4 table above. The 192.0.0.0/24 rows can stay whole: the block's two globally reachable exceptions, 192.0.0.9 and 192.0.0.10, are PCP and TURN anycast addresses, not 6to4 routers or Teredo servers.

Related Articles

VPN Detection False Positives: Stop Fraud, Not Customers
VPN Detection False Positives: Stop Fraud, Not Customers

A VPN flag can be right about the address and still wrong about the customer. See where VPN detection false positives come from, the context that separates a privacy-minded customer from a fraudster, and how to measure the good users your rules turn away.

Posted on November 4, 2026
Read More: VPN Detection False Positives: Stop Fraud, Not Customers
How Should You Use an IP Threat Score?
How Should You Use an IP Threat Score?

Set IP threat score rules per action, learn which flags should change the answer, and test it all in shadow mode. IPGeolocation.io returns one of the most detailed security responses in one call: 27 fields behind every score.

Posted on October 23, 2026
Read More: How Should You Use an IP Threat Score?
Residential Proxy Detection: How It Works, Why It's Hard
Residential Proxy Detection: How It Works, Why It's Hard

Residential proxies make automated traffic look like real households, which is exactly why IP reputation checks miss them. Here is how detection actually works: provider attribution, network and behavior signals, live connection analysis, and confidence scores instead of binary blocks.

Posted on July 27, 2026
Read More: Residential Proxy Detection: How It Works, Why It's Hard
What Is VPN Detection and How Does It Work?
What Is VPN Detection and How Does It Work?

VPN detection identifies traffic routed through VPN servers before it reaches your app. Here is how the two signal families work, what they miss, and what to do with a positive result.

Posted on July 27, 2026
Read More: What Is VPN Detection and How Does It Work?
iCloud Private Relay vs Cloudflare WARP, Explained
iCloud Private Relay vs Cloudflare WARP, Explained

iCloud Private Relay and Cloudflare WARP both hide a visitor's real IP address, but they are built for different jobs and hide it in different ways. Private Relay protects Safari browsing, DNS queries, and unencrypted HTTP app traffic through a two-hop relay system. WARP is a whole-device tunnel through Cloudflare's network. Both keep the user near their real region, and, as you will see below, our detection API flags both as relays. If you run a website, an app, or a fraud pipeline, you meet b

Posted on July 23, 2026
Read More: iCloud Private Relay vs Cloudflare WARP, Explained
IP Geolocation Data: Built, Not Guessed
IP Geolocation Data: Built, Not Guessed

A lot of weak "IP geolocation data" is just a WHOIS guess dressed up with marketing. Here is how we actually build ours, layer by layer, from registry data and geofeeds to active measurement and verification, and how accurate it really is.

Posted on July 13, 2026
By Mudassar Tariq
Read More: IP Geolocation Data: Built, Not Guessed

Subscribe to Our Newsletter

Get the latest in geolocation tech, straight to your inbox.