Fake IP address generator — documentation and private ranges

Choose IPv4, IPv6 or both, and pick documentation or private ranges; the tool makes up to 1,000 addresses that are safe for examples, logs, firewall rules and tests because they never point at someone else's server.

Live demo · real result from this tool
Version
Range

Press Generate to create a result.

Processed on your device — nothing is uploaded.

How to use the fake IP address generator

  1. Choose the Version: IPv4, IPv6, or Both, which alternates one of each.
  2. Choose the Range: Documentation (never routed) or Private (RFC 1918 / ULA).
  3. Set How many addresses (up to 1,000) and press Generate.
  4. Copy the list. A note below it names the ranges used.

What it does and when to use it

Network examples need addresses, and real ones cause trouble. The IETF set aside three IPv4 blocks (RFC 5737) and one IPv6 block (RFC 3849) for documentation; routers on the public internet drop traffic to them. Writers, trainers and developers can use them freely in manuals, sample logs, API docs and screenshots.

Private ranges serve a different job. They are what home routers and office networks actually hand out, so they are the right choice when you test firewall rules, parse internal logs or build a demo network map.

For other identifiers in network test data, the fake MAC address generator makes locally administered hardware addresses. For full rows of personal test data, use the bulk fake data generator. If you need random hex for packet payloads, try the random hex generator.

How it works

All numbers come from crypto.getRandomValues.

Option IPv4 IPv6
Documentation 192.0.2.x, 198.51.100.x or 203.0.113.x, with x from 1 to 254 2001:db8: followed by six random groups
Private 10.x.x.x, 172.16–31.x.x or 192.168.x.x, last part 1 to 254 fd plus two random hex digits, then seven random groups (a unique local address)

The last IPv4 part skips 0 and 255, which are often network and broadcast addresses in a /24, so the results look like normal host addresses.

Worked examples

Sample output; yours will differ.

  • IPv4, Documentation: 192.0.2.218, 203.0.113.205, 192.0.2.121, with the note “Documentation ranges: RFC 5737 (IPv4) and RFC 3849 (IPv6).”
  • IPv6, Documentation: 2001:db8:190f:c430:92e4:c87f:1219:1f7f. Every value starts with 2001:db8:.
  • Both, Private: 10.120.87.229 and fdcd:358f:8fe6:14d5:3ab2:b81f:8e77:14fa.

Limits and tips

  • IPv6 addresses are written in full, without :: shortening. Run them through your own formatter if you need the short form.
  • The tool does not remove duplicates. With 3 × 254 documentation IPv4 addresses, repeats are likely in batches of a few dozen or more.
  • No CIDR blocks, ports or reserved ranges other than these are offered.

Frequently asked questions

Why not just make up any IP address?
A random public address almost always belongs to someone. If it ends up in documentation, a sample config or a test that actually sends traffic, you could end up scanning, blocking or blaming a stranger's server. The documentation ranges exist so that never happens.
Which option should I use?
Use Documentation for anything that will be read by other people, such as manuals, blog posts, screenshots and sample logs. Use Private when you need addresses that look like a real office or home network, for example to test subnet rules or a router configuration.
Can these addresses hide my real IP?
No. This tool only writes text. It does not change your connection, and an IP address you type into a form is not where your traffic comes from.
Are private addresses unique?
No. Ranges such as 192.168.0.0/16 are reused on millions of separate networks. That is fine inside one network but means they are meaningless on the public internet.

Written by the ToolsRift team · Last updated

Pages are drafted with AI assistance and checked by automated tests. How we write and check pages.

Was this tool useful?

Report a problem

Start typing to search every tool.

↑ ↓ to moveEnter to openEsc to close