Updated · Built and checked by the PlinzoTools team, formulas tested against published sources
Generate random, well-formed IPv4 addresses -- any range or private-only.
Click Generate to create new IP addresses.
This tool generates random, well-formed IPv4 addresses for test data or examples -- optionally restricted to the private (RFC 1918) ranges, which are reserved for internal networks and never routed on the public internet.
Choose how many to generate and pick a range: Any (public or private) or Private (RFC 1918) only. In Any mode each of the four octets is fully random from 0 to 255, so the result can include loopback (127.x), multicast, reserved, or private addresses -- it is not limited to the public range. Click Generate for a fresh batch.
RFC 1918 reserves 3 blocks for private networks: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. These addresses are never assigned to public internet hosts, making them a safe, realistic choice for test/example data that shouldn't accidentally resemble a real, reachable address.
For subnet math on any of these generated addresses, see the Subnet Calculator.
The range setting has two choices. "Private (RFC 1918) only" picks one of the three private blocks at random and then fills in the remaining octets. For the 10.x block all three trailing octets are random. For the 172 block the second octet is kept between 16 and 31, matching 172.16.0.0/12. For the 192.168 block the last two octets are random. "Any" simply draws four independent random octets from 0 to 255, so it is not restricted to public addresses.
Because "Any" is fully random, some results will land in ranges that are not ordinary public host addresses. Loopback addresses starting with 127, link-local addresses in 169.254, multicast addresses from 224 upward, and the private blocks themselves can all appear, as can addresses ending in .0 or .255. If your test data must look like a normal internet host, scan the batch and discard anything that looks special, or use the private option and treat the results as clearly internal. Also remember that a public-looking result might belong to a real organisation, so never use generated addresses for scanning, probing, or blocklists.
Pick private when you are writing documentation, tutorials, or screenshots about a home or office network, since these addresses signal "internal" to anyone reading. Pick any when you are testing a parser or validator and want the widest variety of octet values, including edge cases like very small or very large numbers. For a log-analysis demo, a mix of both, generated in two batches and merged, gives a more believable dataset.
Once you have a sample address, paste it into a subnet calculator with a prefix such as /24 to see its network and broadcast addresses, or run it through an address validator to confirm the format handling in your own code.
They're randomly generated within valid IPv4 format rules -- an address from the "Any" mode could coincidentally match a real assigned address (or land in a loopback, multicast, or private block), since this tool doesn't check against any registry; "private range" addresses are guaranteed to fall within the RFC 1918 blocks that are never publicly routable.
For test data meant to represent internal/LAN devices, or when you want to guarantee the generated address can't be mistaken for or resolve to a real public host.
Not with this tool -- it generates IPv4 addresses only; for IPv6 format validation, see the IP Address Validator.
Yes, in private mode the address always falls inside 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16.
Any mode draws every octet at random with no exclusions, so loopback, multicast, and other special-purpose ranges can appear.
Up to 200 per click. Larger numbers are reduced to 200.
Reference: MDN Web Docs