About Random IP Address Generator
This random IP address generator produces IPv4 or IPv6 addresses for testing, documentation and log samples, without ever touching a real network. Choose between a public-looking address that avoids the obviously reserved ranges, or a private RFC 1918 address for IPv4 (the familiar 10.x, 172.16-31.x and 192.168.x blocks) or a locally-assigned ULA address for IPv6, and generate up to a hundred at a time.
When you would reach for this
Populating log samples for documentation
Fill an example server log, dashboard screenshot or API response with plausible IP addresses instead of a real one that might identify an actual machine or user.
Testing IP validation and parsing code
Generate a batch of both IPv4 and IPv6 addresses to confirm your regex, CIDR-matching or geolocation-stub logic handles both formats correctly.
Building a network diagram or lab exercise
Private-range addresses give a training document or lab exercise realistic-looking internal IPs without accidentally referencing a real production subnet.
Seeding a firewall or access-control rule test
Generate a mixed batch of addresses to verify allow and deny rules behave correctly across a range of source addresses.
How to use it
- 1
Choose the IP version: IPv4 or IPv6.
- 2
Set How many addresses to generate, up to 100 per run.
- 3
Pick the Address range: Public-looking for general-purpose test data, or Private for addresses shaped like an internal network.
- 4
Click Generate and copy or download the list.
What 'public-looking' actually means here
The generator avoids the most obviously reserved IPv4 blocks — 0.x, 10.x, 127.x (loopback), 169.254.x (link-local) and the 172.16-31.x and 192.168.x private ranges — when building a 'public-looking' address, so the result resembles an address that could plausibly be routed on the open internet. It does not check the result against IANA's actual allocation records or any regional registry, so a generated address might still be unassigned, might be inside a range reserved for a purpose not filtered out here, or might coincidentally belong to a real, live host. None of that matters for its intended use as test data, but it does mean the output should never be treated as verified or safe to actually contact.
Why the private ranges look the way they do
RFC 1918 carves out three IPv4 blocks explicitly excluded from public routing: 10.0.0.0/8, a single block of over 16 million addresses often used by large organisations; 172.16.0.0/12, a mid-sized block spanning 172.16.x through 172.31.x; and 192.168.0.0/16, the smallest and most familiar block, used by nearly every home router. IPv6's equivalent is the Unique Local Address (ULA) range, fd00::/8, defined in RFC 4193, which this generator's private-scope IPv6 option draws from, giving addresses that look correctly scoped to a private network without any chance of colliding with a real public IPv6 allocation.
Tips
- Use private-range addresses for anything meant to represent an internal network in a diagram or lab exercise — public-looking addresses can be mistaken for real external hosts.
- Generate a mixed batch across both IPv4 and IPv6 when testing parsing code, since the two formats trip up naive regex differently.
- Never use a generated address to actually configure, ping or scan anything — it exists purely as text data, not a verified real or empty address.