RFC 5737 reserves 192.0.2.0/24, 198.51.100.0/24 and 203.0.113.0/24 for documentation, and RFC 3849 reserves 2001:db8::/32 for the same purpose in IPv6. Nothing in those ranges routes anywhere, which makes them the only truly safe addresses to paste into a test.
What you can control
- Documentation ranges by default, so a leaked fixture cannot point at somebody's server.
- Full IPv6 support, including the compressed
::form that trips up naive parsers. - CIDR suffixes for testing subnet logic, with sensible prefix lengths per version.
- Optional ports weighted toward the ones that actually appear — 80, 443, 8080.
Testing ideas
- Safe by default. Documentation ranges (RFC 5737, RFC 3849) can never route, so they are safe in screenshots, docs and fixtures.
- Validation. Mix IPv4 and IPv6 to test fields and database columns that silently assume IPv4.
- CIDR and ports. Append CIDR suffixes and ports to test allow-list parsers and log formatters.
- Private ranges. Generate RFC 1918 addresses to test SSRF protection that must refuse internal targets.
What this is not
The arbitrary-public option generates addresses that may belong to a real network. Use documentation ranges unless you specifically need addresses outside them.