CyberKit

IP & CIDR Reference

Special-use IPv4 and IPv6 ranges from IANA, plus a CIDR quick reference.

Spotting a special-use range at a glance is a fast triage step. Is the beaconing host internal, or does it only look private because it sits in CGNAT space? Is that address in a report real, or a documentation block?

Every block comes from IANA's special-purpose registries.

24 rows.

Special-use IP ranges
RangeNameNote
10.0.0.0/8Private-UseThe largest RFC 1918 block (16.7M addresses): the default range for most enterprise internal networks.
172.16.0.0/12Private-UseRFC 1918 private range, 1.05M addresses: a common Docker/container-network default.
192.168.0.0/16Private-UseRFC 1918 private range, 65,536 addresses: the default on almost every home/SOHO router.
100.64.0.0/10Shared Address SpaceReserved for carrier-grade NAT (CGNAT) between an ISP's customer-facing network and its own NAT devices: routable only within that provider's network, distinct from RFC 1918. Seeing this in a log usually means the traffic traversed an ISP's CGNAT layer, not a private LAN.
127.0.0.0/8LoopbackAny address in this whole /8 (not just 127.0.0.1) loops back to the local host: never appears on the wire.
169.254.0.0/16Link Local (APIPA)Auto-assigned by Windows/most OSes when DHCP fails: seeing this on a host is a strong signal it never reached a DHCP server, not evidence of a specific attack on its own.
224.0.0.0/4MulticastClass D multicast space: 224.0.0.0/24 specifically is reserved for local-network control traffic (routing protocols, mDNS, etc.) that a router never forwards off-segment.
192.0.2.0/24Documentation (TEST-NET-1)Reserved purely for documentation/examples: never routed on the real internet. This site's own fabricated Email Header Analyzer sample uses this range for exactly that reason.
198.51.100.0/24Documentation (TEST-NET-2)Same purpose as 192.0.2.0/24: a second documentation block so an example can show two distinct "networks" without using anything real.
203.0.113.0/24Documentation (TEST-NET-3)The third RFC 5737 documentation block, also used throughout this site's own tool examples (IOC Extractor, Regex Tester) as clearly-fabricated illustrative addresses.
198.18.0.0/15BenchmarkingReserved for testing network-interconnect-device throughput in a lab, so a benchmark can't accidentally flood real internet addresses.
0.0.0.0/8This Network0.0.0.0 itself shows up as a "no specific address" placeholder (e.g. a default route, or a DHCP client's source address before it has one).
255.255.255.255/32Limited BroadcastThe local-segment broadcast address: routers never forward it. Distinct from a subnet's own directed broadcast address (e.g. 10.0.0.255 for a 10.0.0.0/24), which this tool's CIDR & VLAN Calculator computes per-network above.
240.0.0.0/4Reserved (Class E)Historically "reserved for future use" and still not assigned for general internet use: seeing it as a real source/destination in traffic is unusual and worth a second look.
::1/128LoopbackIPv6's single loopback address: the equivalent of IPv4's whole 127.0.0.0/8, but just one address here.
::/128Unspecified AddressThe IPv6 equivalent of 0.0.0.0: a placeholder meaning "no address," e.g. a host that hasn't configured one yet.
fe80::/10Link-Local UnicastEvery IPv6 interface auto-assigns one of these: routers never forward them off-segment, and they're always present alongside any other address a host has.
fc00::/7Unique Local Address (ULA)IPv6's rough analog to RFC 1918 private space, not globally routed, but (unlike IPv4 private ranges) the /48 below it is meant to be pseudo-randomly generated so two organizations' ULA ranges essentially never collide if networks are later merged.
ff00::/8MulticastIPv6 has no broadcast at all: anything that would be a broadcast in IPv4 (e.g. "all routers," "all nodes") uses a well-known multicast address in this block instead.
2000::/3Global UnicastThe block real, internet-routable IPv6 addresses are allocated from: most real-world IPv6 traffic you'll see in a log starts with "2" or "3".
::ffff:0:0/96IPv4-Mapped AddressEmbeds a real IPv4 address in the low 32 bits (e.g. ::ffff:192.168.1.1). How a dual-stack socket API represents an IPv4 peer to IPv6-aware code. This tool's CIDR & VLAN Calculator (IPv6 mode) parses this exact form.
64:ff9b::/96NAT64 Well-Known PrefixThe standard prefix a NAT64 gateway prepends to an embedded IPv4 address (e.g. 64:ff9b::192.168.1.1) to let an IPv6-only host reach an IPv4-only destination.
2001:db8::/32DocumentationThe IPv6 equivalent of the RFC 5737 TEST-NETs: this site's own IPv6 tool examples use addresses from this range.
3fff::/20DocumentationA second, newer documentation prefix (allocated 2024) alongside 2001:db8::/32. Added because 2001:db8::/32 examples were increasingly showing up as real-looking addresses in generated/AI-assisted content.

Related

All references