IP Space Classification

Bogon / Reserved IP Checker

Check whether an IP or CIDR falls into bogon, private, documentation, multicast, transition, or other special-use address space before you allow, route, or publish it.

Bogon Detection

Flags private, link-local, documentation, benchmark, and other non-global ranges.

IPv4 and IPv6

Works with both families and handles single IPs as well as CIDRs.

Reference Context

Shows the relevant RFC or special-use classification for each match.

Examples

This tool runs entirely offline using built-in special-use range definitions, so it is fast and deterministic.

Normalized input
10.0.0.1/32
Family
ipv4
Bogon status
Yes
Routability
Non-global

Primary category

Private-Use

This input fully lands in a known special-use or non-global range.

Matching Special Ranges

Inside
Private-Use
Non-global
10.0.0.0/8

RFC 1918 private IPv4 space for internal networks.

RFC 1918

Why this matters

Filtering, routing, and ACL decisions often depend on whether an address is globally routable or only valid in a special scope.

Common mistake

Documentation or RFC1918 addresses often leak into configs, screenshots, or firewall changes and then silently fail in production.

Operational payoff

A quick offline classification helps avoid bad allowlists, route leaks, NAT confusion, and broken examples.

À propos de cet outil

The Bogon / Reserved IP Checker classifies IPv4 and IPv6 inputs against common special-use ranges such as RFC 1918 private space, documentation prefixes, multicast, link-local, transition ranges like Teredo and 6to4, and other reserved blocks. This is useful when reviewing ACLs, route advertisements, customer reports, screenshots, or troubleshooting notes to confirm whether an address is actually supposed to appear on the public internet. Because the logic is based on static special-use ranges, the tool is fast, deterministic, and suitable for landing-page SEO around private IP, bogon, documentation range, and reserved address checks.

Comment utiliser

  1. Enter an IP address or CIDR.
  2. Review the normalized value, bogon status, and routability summary.
  3. Inspect each matching special-use block and its RFC reference.
  4. Use the result to fix ACLs, route lists, or example data before deployment.

Fonctionnalités

  • IPv4 and IPv6 special-use classification
  • Bogon, private, documentation, multicast, transition, and benchmark detection
  • Works with single IPs and CIDRs
  • Shows overlap versus full containment for larger ranges
  • Runs offline with deterministic results

Cas d'utilisation courants

  • Reviewing firewall allowlists and deny lists
  • Checking whether a customer-reported IP is globally routable
  • Validating example addresses in docs and screenshots
  • Preventing RFC1918 or documentation ranges from leaking into production configs

Détails techniques

This checker compares the input to a curated list of well-known IPv4 and IPv6 special-use ranges.

Examples include:

  • RFC 1918 private IPv4 space such as 10.0.0.0/8
  • Documentation space such as 192.0.2.0/24 and 2001:db8::/32
  • Transition prefixes such as 2002::/16 and 2001::/32
  • Multicast, loopback, link-local, and benchmark ranges

Bogon and Reserved Space FAQ

Is every reserved range a bogon?

In practice many special-use ranges are treated as bogons on the public internet, but the exact operational meaning depends on context.

Why is CGNAT marked non-global?

Carrier-grade NAT space is shared-use space for providers and should not appear as normal public address ownership.

Can a CIDR partially overlap special-use space?

Yes. When a larger CIDR covers both special and public ranges, the result is marked as partial or mixed.

Does public mean globally reachable?

Not necessarily. It means the input did not match a known special-use range. Reachability still depends on routing and policy.