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 a practical tool for developers and QA engineers who need realistic IP data without touching production systems. Generate addresses in standard dotted-decimal notation and choose between public, private, or any valid range. Private mode constrains output to the three reserved blocks — 10.x, 172.16–31.x, and 192.168.x — useful for simulating LAN traffic or container networking. Public mode excludes loopback, link-local, multicast, and other reserved ranges, giving you plausible internet-routable addresses for geo-IP lookups or rate-limiter tests. Adjust the count to generate as many addresses as your seed script or test fixture needs in one shot.

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 count field to the number of IPv4 addresses you need, from a handful to a large batch.
  2. Select an address type — 'public' for internet-facing IPs, 'private' for LAN ranges, or 'any' for unrestricted output.
  3. Click the generate button to produce your list of random IPv4 addresses instantly.
  4. Copy the output directly into your code, test fixture, config file, or spreadsheet.

Use Cases

  • Seeding a Postgres staging database with thousands of unique fake user IP records
  • Generating mock Apache or Nginx access logs for log-parsing pipeline development
  • Testing firewall ACL rules in Terraform configs against both private and public ranges
  • Populating Jest or Cypress fixtures with varied remote IPs for rate-limiting middleware tests
  • Creating realistic mock client IPs to stress-test geo-IP lookup edge cases and fallback logic

Tips

  • Use the private type when testing Docker or Kubernetes configs — results will stay within realistic LAN subnets like 192.168.x.x.
  • For log simulation, generate a large batch (50+) with 'any' type so your fake log contains a natural mix of client addresses.
  • Combine public addresses with a real geo-IP API call during testing to exercise your app's location fallback paths.
  • When seeding a SQL database, generate your IPs here, paste into a spreadsheet, then use a VLOOKUP or script to pair each IP with a fake user row.
  • If your firewall ACL test needs to cover all three private blocks, run the generator three times with 'private' selected and verify each block appears in results.
  • Avoid hardcoding a single fake IP like 192.168.1.1 across all test cases — repeated IPs can mask bugs that only appear with unique addresses.

FAQ

what's the difference between public and private IPv4 addresses

Private addresses — 10.x.x.x, 172.16–31.x.x, and 192.168.x.x — are reserved for internal networks and never routed on the public internet. Public addresses are globally unique and reachable from anywhere online. Use private mode when simulating LAN or container traffic, and public mode when mimicking internet-facing clients.

can I use randomly generated IPs to test a geo-IP library

Yes, with one caveat: these addresses are syntactically valid but randomly constructed, so a geo-IP database may return arbitrary or no location data. That's actually useful for testing edge cases like unknown regions, empty results, or fallback behavior in your code.

what ranges are excluded when generating public IPv4 addresses

The generator excludes loopback (127.0.0.0/8), link-local (169.254.0.0/16), private blocks (10/8, 172.16/12, 192.168/16), multicast (224.0.0.0/4), and the reserved 0.x block. Every result is a plausible internet-routable address, which matters for routing and CDN tests.