We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Generate IPv4 and IPv6 addresses on demand. Supports specific public/private networks and custom CIDR ranges. Ideal for testing, development, and learning.
IPv4: 32-bit address, e.g. 192.168.1.1
IPv6: 128-bit address, e.g. 2001:0db8:85a3::8a2e:0370:7334
Locally stored history of your last 20 generated IP addresses.
No history yet
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This tool produces sample IPv4 or IPv6 text. It does not look up an address, check whether a device is online, assign an address to a network, or change your own connection. Use generated values in fixtures, mock records, or format-handling tests where you need plausible address-shaped data.
Single mode produces one address and keeps a recent history of up to 20 results. Batch mode produces a selectable list of 1–100 entries with copy and TXT/CSV download options. Each entry is generated independently, so repeated addresses can occur; there is no deduplication control.
IPv4 uses four decimal octets separated by periods. The generator offers unrestricted and A/B/C first-octet presets, private ranges, and a custom network with a CIDR prefix. In custom mode the prefix determines which portion is treated as the network; for example, a /24 leaves the final eight bits for host values. The implementation accepts prefix lengths from /8 through /30 and excludes the network and broadcast endpoints in this mode.
The private option draws from 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16, the private-use blocks specified in RFC 1918. They can be reused within separate private networks and are not globally unique. [RFC 1918 defines these address blocks; checked 2026-09-28.] Other IPv4 presets can optionally exclude private, loopback, and multicast values. Those checkboxes are filters, not a complete test of global routability or assignment status.
IPv6 mode generates eight hexadecimal groups. Choose a full display or a shortened display with zero compression. These options affect the text representation; they do not restrict output to a particular subnet, private-use range, or globally reachable range. A generated string alone does not prove that an address is assigned, reachable, or suitable for routing.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Use single mode for one value and its recent history. Choose batch mode when you need a list; its count control ranges from 1 to 100.
Choose IPv4 or IPv6. For IPv4, select a preset or enter a network and prefix in custom mode. For IPv6, choose full or compressed display.
For applicable IPv4 presets, decide whether to exclude private, loopback, or multicast ranges. Review custom CIDR input before relying on the range.
Regenerate a single value or create the batch. Copy a value, copy the list, or download batch output as a line-separated TXT or a CSV with sequence, address, and version columns.
Use cases
See how the tool fits into real work and everyday tasks.
A developer can populate test records with IPv4 or IPv6 strings and verify that a field accepts the expected address syntax.
Build a small sample table or mock log, then review each address before publishing. For documentation, use reserved example ranges chosen for that purpose instead of implying that a random public-looking value is safe to contact.
Generate private IPv4 examples to discuss the RFC 1918 blocks, then explain separately how a real network assigns addresses and routes traffic.
Q&A
Find concise answers to common questions and confusing cases.
There is no such guarantee. The result is text generated from selected ranges; the tool does not perform a reachability check or query address ownership.
Yes. Entries are generated independently, and batch mode does not remove duplicates.
No. Private-use IPv4 blocks may be reused in different networks. RFC 1918 describes the blocks and their non-global uniqueness; the result is only a sample address.
Notes
Review scope, result limitations, and important precautions before use.
Generated values are test strings. They are not an address lease, IP lookup result, proof of availability, or permission to contact a host.
Do not configure random public-looking values on a production network. Batch generation can repeat values, and exclusions do not verify all special-purpose allocations listed by IANA. Inspect the output and use an appropriate network plan or documented test range for real configuration work.
Related
Discover related tools, collections, and available API capabilities.