Skip to main content
Back to Numbers generators

Numbers

Random IPv4 Address Generator

Used by developers, writers, and creators worldwide.

A random IPv4 address generator is the fastest way to get correctly formatted, range-accurate IP addresses for test data, mock configs, and network simulations. Pick a count, choose your address type — public, 192.168.x.x, 10.x.x.x, or 172.16.x.x — and copy the results straight into your script or fixture file. No cleanup needed. Each private range serves a distinct purpose. The 192.168.x.x range mirrors home and small-office networks. The 10.x.x.x range fits large enterprise flat networks. The 172.16.x.x range is common in cloud VPCs and virtualized environments. Public addresses work for geolocation tables, rate-limit testing, and log mocks where globally routable IPs are expected. Use whichever range matches the architecture you are actually simulating.

Loading usage…

Free forever — no account required

How to use

  1. Choose your options above
  2. Click Generate
  3. Copy your result

Detailed instructions

  1. Set the Number of Addresses field to how many IPs you need, up to 50.
  2. Open the Address Type dropdown and select Public, 192.168.x.x, 10.x.x.x, or 172.16.x.x based on your network context.
  3. Click Generate to produce the list of random IPv4 addresses.
  4. Review the output and click Copy to transfer all addresses to your clipboard.
  5. Paste directly into your test script, config file, CSV, or log fixture.

Use Cases

  • •Seeding a Postgres staging database with realistic source IPs for load-testing queries
  • •Populating Apache or Nginx access log fixtures for Splunk or SIEM ingestion tests
  • •Filling Kubernetes network policy test cases with plausible 10.x.x.x pod addresses
  • •Generating varied public IPs to test rate-limiting middleware in an Express or FastAPI app
  • •Creating mock DHCP lease tables in 192.168.x.x space for network documentation demos

Tips

  • →Match the private range to your architecture: use 10.x.x.x for flat enterprise simulations, 192.168.x.x for consumer router contexts.
  • →Generate a batch of 50 and filter by the third octet in a spreadsheet to approximate a specific /24 subnet without a dedicated CIDR tool.
  • →When building fake access logs, combine public IP output with a timestamp generator and a user-agent list to create realistic multi-field entries.
  • →For load testing tools like k6 or JMeter, paste the list into a CSV data file and configure the tool to iterate through it as a variable source IP.
  • →Avoid reusing the same small IP set across many test runs — generate a fresh batch each session to prevent accidental pattern-matching in your test assertions.
  • →If your test framework deduplicates inputs, run two or three separate generations and concatenate them rather than relying on a single large batch.

FAQ

what is the difference between public and private IPv4 addresses for testing

Private ranges (10.x.x.x, 172.16.x.x, 192.168.x.x) are non-routable on the public internet, making them safe defaults for unit tests and CI pipelines — no risk of accidentally hitting a real server. Public addresses are globally routable, so use them only in isolated environments where no outbound requests can escape.

are randomly generated public IP addresses safe to use in test data

They are safe as inert string values in fixtures, log mocks, or seed scripts, but never route actual traffic to them — they may overlap with real-world assignments. If your test environment can make outbound requests, stick to private ranges to avoid unintended DNS lookups or terms-of-service issues.

how do I generate IPs for a specific subnet like 192.168.1.x

This generator randomizes across the full selected private range rather than a locked subnet. Generate a larger batch from the 192.168.x.x range and filter by prefix in your script, or use a dedicated CIDR tool. For most fixture and mock use cases, the full-range output works without subnet pinning.