Random IP Generator
Generate random IPv4 and IPv6 addresses.
Random IP Generator
Generate random IPv4 and IPv6 addresses for testing, mock data and documentation. Choose public routable addresses, private LAN addresses, reserved documentation ranges, completely random values or hosts inside your own CIDR subnet. Results can be unique and IPv6 output can be compressed with the :: notation.
Address types
| Type | IPv4 | IPv6 |
|---|---|---|
| Public | any routable address, reserved blocks skipped | global unicast 2000::/3 |
| Private | 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 | unique local fd00::/8 |
| Documentation | 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24 | 2001:db8::/32 |
| Any | full 32-bit space | random 128-bit value with a global prefix |
| Custom CIDR | hosts inside your subnet | – |
Why generate random IPs?
- Testing – feed firewall rules, rate limiters, geo-IP lookups and log parsers with varied input.
- Mock data – fill user tables, access logs and analytics dashboards with plausible addresses.
- Documentation – the documentation ranges are safe to publish in tutorials and RFC-style examples.
- Network planning – sample host addresses inside a subnet before assigning them.
IPv6 compression
IPv6 addresses have eight groups of four hex digits. RFC 5952 shortens them by removing leading zeros in each group and replacing the longest run of zero groups with ::. Turn off compression to get the full 39-character form, which is easier to sort and align.
Addresses are generated locally in your browser with a secure random generator. To look up a real address, use IP to Hostname; for hardware addresses use the Random MAC Generator.
Frequently Asked Questions
Which addresses count as public?
Public IPv4 results skip all special-purpose blocks: 0.0.0.0/8, private ranges (10/8, 172.16/12, 192.168/16), carrier-grade NAT 100.64/10, loopback 127/8, link-local 169.254/16, documentation and benchmark ranges, and multicast/reserved space from 224.0.0.0 upward. Public IPv6 results come from the global unicast block 2000::/3.
Are these real devices?
A random public address may belong to a real server. Do not scan or attack addresses you do not own. For examples in documentation, choose the Documentation type – those ranges (192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24 and 2001:db8::/32) are reserved and never routed.
How does the custom CIDR option work?
Enter a network such as 10.20.0.0/16. Every result lies inside that subnet. For prefixes up to /30 the network and broadcast addresses are skipped, so you only get usable host addresses.