IP Space Classification
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.
Flags private, link-local, documentation, benchmark, and other non-global ranges.
Works with both families and handles single IPs as well as CIDRs.
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.
Primary category
This input fully lands in a known special-use or non-global range.
RFC 1918 private IPv4 space for internal networks.
Filtering, routing, and ACL decisions often depend on whether an address is globally routable or only valid in a special scope.
Documentation or RFC1918 addresses often leak into configs, screenshots, or firewall changes and then silently fail in production.
A quick offline classification helps avoid bad allowlists, route leaks, NAT confusion, and broken examples.
This checker compares the input to a curated list of well-known IPv4 and IPv6 special-use ranges.
Examples include:
10.0.0.0/8192.0.2.0/24 and 2001:db8::/322002::/16 and 2001::/32In practice many special-use ranges are treated as bogons on the public internet, but the exact operational meaning depends on context.
Carrier-grade NAT space is shared-use space for providers and should not appear as normal public address ownership.
Yes. When a larger CIDR covers both special and public ranges, the result is marked as partial or mixed.
Not necessarily. It means the input did not match a known special-use range. Reachability still depends on routing and policy.