What you can generate
Four modes:
- IPv4 public: globally routable addresses. Excludes private RFC 1918 ranges (10.x, 172.16.x, 192.168.x), loopback (127.x), link-local (169.254.x), and multicast/reserved (224+).
- IPv4 private: addresses inside RFC 1918 private ranges. What you’d see on home/office LANs.
- IPv4 any: any 32-bit address, no filtering. Includes reserved and special-purpose ranges.
- IPv6: full 128-bit addresses formatted as 8 groups of 4 hex digits.
Generate 1 to 500 at a time. Output is plain text (one IP per line), copy-paste friendly.
When to use
- Test data: filling a database with realistic-looking IP addresses for development/testing.
- Mock logs: generating fake access logs, IDS alerts, or audit trails for demos.
- Fuzzing/security tests: random inputs for IP-parsing code in your apps.
- Network class education: showing students what IPs in different RFC 1918 ranges look like.
- Filling UI mockups: realistic-looking placeholder data instead of “1.2.3.4” everywhere.
What “public” actually means here
A “public” IPv4 address in this generator is one that’s not in a private, loopback, link-local, or multicast range. That’s a more useful filter than just “any non-private,” because:
- Loopback (127.0.0.1 etc.) doesn’t leave the local machine
- Link-local (169.254.x) is for auto-configuration
- Multicast (224+) is for one-to-many delivery, not unicast
- 0.0.0.0/8 and 240+ are reserved
The remaining space, about 88% of the IPv4 address space, is what you can encounter as a real public address on the internet. The generator picks uniformly from that range.
IPv6 caveat
The IPv6 output is fully expanded (e.g., 2001:0db8:0000:0000:0000:0000:0000:0001). Real IPv6 addresses are typically written in compressed form (2001:db8:1) using : for runs of zeros. Both forms refer to the same address; the expanded form is unambiguous and easier to compare/sort.
If you need compressed IPv6, run the output through any IPv6 normalizer.
What this is NOT
- Not real IPs from anyone’s network. These are randomly generated. No one’s traffic, no one’s identity.
- Not an IP scanner or recon tool. Doesn’t make any network requests.
- Not for security operations that need real adversarial data, use real captured traffic for that.
Frequently asked questions
Are the IPs evenly distributed? Yes, uses crypto.getRandomValues for uniform random bytes. Public mode rejects bytes that fall into excluded ranges; rejection sampling keeps the distribution uniform within the public space.
Why does the same IP show up sometimes? With 500 picks from a billion+ address space, duplicates are statistically rare but possible (birthday paradox). For 100 picks, expect zero duplicates.
Can I generate IPs in a specific subnet? Not in this tool, it picks across the whole space. For specific subnets, you’d want a dedicated CIDR-range tool that lets you pick the network prefix.
Are private IPs really private? RFC 1918 private ranges aren’t routed on the public internet. Many networks use them, so they’re not unique, your home router might use 192.168.1.1, and so does your neighbor’s. The “privacy” is just that they don’t exist in the global routing table.