Don't like ads? Go Ad-Free Today 

Fake IP Address Generator

DeveloperNetworkingRandom

ADVERTISEMENT · REMOVE?

INPUT

IP Version

Range Type

Filtered against RFC ranges (RFC 1918, 6598, 5771, 5737, 3927, etc.)

Range Type

Filtered against RFC ranges (RFC 4193, 4291, 3849, etc.)

Count

Settings

Append CIDR suffix (host /32 or /128)

Unique addresses (no duplicates)

OUTPUT

Client Side

ADVERTISEMENT · REMOVE?

Guide

Fake IP Address Generator

Generate batches of valid fake IPv4 and IPv6 addresses, filtered by RFC range type — private (RFC 1918), public, loopback, multicast, CGNAT (RFC 6598), link-local, ULA (RFC 4193), and documentation. Useful for seeding test data, populating mock APIs, demoing dashboards, or producing example traffic logs without leaking real addresses.

How to Use

Pick the IP version: IPv4 or IPv6.
Choose a range type. Each option maps to a real reserved or routable block defined by IETF / IANA.
Set the count (1–1000). Toggle Append CIDR suffix to add /32 or /128 to each address, and Unique addresses to dedupe results.
Click Generate. Use the copy or download button to grab the list.

Features

IPv4 + IPv6 — switch versions in one click; the range list updates to match.
RFC-accurate ranges — public output is reject-sampled against IANA reserved blocks, so it never falls inside 10/8, 172.16/12, 192.168/16, 100.64/10, 127/8, 169.254/16, multicast, or documentation space.
Bulk generation — produce up to 1000 addresses per run.
CIDR suffix — append /32 (IPv4) or /128 (IPv6) host masks for use in firewall rules, ACLs, or routing tests.
Unique mode — guarantees no duplicate output, with safe handling for tiny ranges like ::1.
Compressed IPv6 — output follows RFC 5952 (longest run of zeros collapsed with ::).
Copy & download — one-click copy or save the list as a plain text file.
100% client-side — generation happens in the browser; nothing is sent to a server.

 FAQ

What makes an IP address private vs public?

Private IPv4 addresses live inside three reserved blocks defined by RFC 1918 — 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. They are non-routable on the public internet, so any organisation can reuse them inside its own network. Public addresses are everything outside these reserved blocks (and outside loopback, multicast, link-local, CGNAT, etc.) and are globally routable through the IANA / RIR allocation system.
What is CGNAT and why does it have its own range?

Carrier-Grade NAT (RFC 6598) reserves 100.64.0.0/10 for ISPs to share a single public IP across many subscribers. It exists because IPv4 ran out of public addresses, and ISPs needed an internal-but-not-private block that would never collide with customer LANs (which usually use 192.168.x.x or 10.x). You will see 100.64–100.127 inside many mobile and fibre networks.
How does IPv6 address compression work?

RFC 5952 defines the canonical IPv6 text format. Leading zeros in each 16-bit group are stripped, and the longest run of consecutive all-zero groups is replaced with a single double-colon (::). Only one :: is allowed per address, and if there are two equally long runs of zeros, the leftmost one wins. This makes addresses like 2001:0db8:0000:0000:0000:0000:0000:0001 collapse to 2001:db8::1.
What are the documentation address ranges and when should I use them?

RFC 5737 reserves 192.0.2.0/24, 198.51.100.0/24, and 203.0.113.0/24 for documentation and examples in IPv4. RFC 3849 reserves 2001:db8::/32 for IPv6. These ranges are guaranteed never to be assigned to real hosts, so they are the correct choice for tutorials, training material, RFCs, and screenshots — using a real customer IP in published examples is a common mistake that can leak information or accidentally point readers at live systems.
Why are some address ranges marked as link-local or multicast?

Link-local addresses (169.254.0.0/16 in IPv4, fe80::/10 in IPv6) are auto-configured for communication on a single network segment and are never routed off-link. Multicast (224.0.0.0/4 in IPv4, ff00::/8 in IPv6) is for one-to-many delivery — protocols like mDNS, OSPF, and IGMP rely on specific multicast groups inside these ranges. Both ranges are reserved and behave very differently from regular unicast addresses, so they are filtered separately from public output.