Network data that cannot reach a real host
Pasting a real IP address into documentation, a screenshot or a test can send traffic somewhere it should not go. The network generators default to the ranges standards bodies set aside for exactly this:
- IPv4 from
192.0.2.0/24,198.51.100.0/24and203.0.113.0/24(RFC 5737), and IPv6 from2001:db8::/32(RFC 3849) — the IP address generator can also produce private and public-shaped addresses when a test needs them. - Email addresses on
example.comand the.exampleTLD (RFC 2606), via the email generator. - MAC addresses with the locally administered bit set, so they never claim a manufacturer's OUI — see the MAC address generator.
Telemetry, logs and schedules
- The server log generator writes access and application logs in common formats, for testing parsers, log shippers, dashboards and alert rules without exporting production logs.
- The user-agent string generator covers desktop and mobile browsers and crawlers, which is what device-detection, analytics and bot-filtering code needs.
- The HTTP status code generator produces status codes with realistic error bodies for exercising retry and error-handling paths.
- The cron expression generator produces valid schedules with a plain-English explanation of each.
- The domain & URL generator produces brand-style domains, deep URLs with query strings and fragments, and optional internationalised hosts for testing URL parsers. These look like real businesses and may well be registered, so use
example.comwherever a link must never resolve. - The git commit generator, session ID generator and coordinates generator cover changelog tooling, auth fixtures and maps.
Session IDs and tokens here are for fixtures only. They come from a seeded generator, which makes them reproducible and therefore predictable — never use one as a real secret. Reserved ranges for test data lists every reserved block with its RFC.