piapia123
en

Random IP Generator

Web

Everything runs locally in your browser — nothing is uploaded

Output

Generate random IP addresses in bulk — up to 100 at a time, one per line, ready to paste into a script. ⚠️ First, what these addresses are: they belong to nobody. In public mode the addresses fall inside real public ranges — but that does not make them free. One may well be a real host on a real network. So the use cases here are test fixtures, log scrubbing, placeholders and fake data; do not use them to configure an interface, write an ACL, or treat one as “an address that is safe to allocate”. Finding a genuinely allocatable address is a different problem (it depends on the RIR registries) and is not solved here. How the three ranges differ: - Public — excludes private blocks (10/8, 172.16/12, 192.168/16), loopback, link-local, multicast, CGNAT and the reserved blocks; for IPv6 it draws only from `2000::/3` - Private — IPv4 from the three RFC 1918 blocks, IPv6 from ULA (`fd00::/8`) - Any — fully random across 32 (or 128) bits, so `0.0.0.0`, `::1` and multicast addresses can appear ⚠️ Private mode samples uniformly across blocks, not weighted by address count — `10/8` is 256 times larger than `192.168/16`, so the overall distribution is not uniform. Fine for “a batch that looks like a private network”, but do not use it as a uniform random source. Everything is produced by the browser’s random number generator. No IP database is queried and nothing is sent anywhere.

Features

  • IPv4, IPv6, or a mix of both
  • Public mode excludes private and reserved ranges (loopback, link-local, multicast, CGNAT)
  • Private mode gives RFC 1918 and IPv6 ULA (`fd00::/8`)
  • Up to 100 per run, one per line, ready to paste into a script
  • IPv6 in compressed, full or uppercase notation
  • Generated by the browser’s RNG — no IP database, no network

How to use

  1. Pick a version and a range
  2. Pick how many you need
  3. Click “Generate again” for a fresh batch
  4. Copy the result

FAQ

Can I use a generated public IP directly?
No. It falls inside a real public range and may be a real machine — using it for load testing, allow-listing or configuring an interface can disturb someone else or cause an address conflict on your network. This tool is for fake data: test fixtures, log scrubbing, form placeholders, seeding a test database. Those need “something that looks like an IP and will not collide with a real host”, and a random address fits — a real collision is extremely unlikely, and the data is never actually used to send packets.
Why does every address start with 10.x or 192.168.x?
Because you selected the private range. That is deliberate — there are only three private blocks (`10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`), so the same few prefixes keep appearing. Switch to public or any for more variety. “Any” includes reserved ranges, so `127.0.0.1` and multicast addresses like `224.x` can show up.
Can I use these to test an IP geolocation feature?
Yes, but be aware that no real result can be found — a random address has no location, so the lookup will most likely return “unknown” or something obviously wrong. For that kind of test, the blocks reserved for documentation are a better fit: IPv4 `192.0.2.0/24`, `198.51.100.0/24`, `203.0.113.0/24` (RFC 5737) and IPv6 `2001:db8::/32`. Those never appear on a real network — they exist precisely for docs and examples.

Related tools