Network
- IPv4 address
- 192.0.2.136
- MAC address
- A6:34:67:C8:BA:EC
- Subnet mask
- 255.255.255.0
Random IP & MAC Address Generator
Synthetic network identifiers for mocking request headers, seeding access logs, and exercising rate limiters and geo rules.
Ahmed Rossi
Client
- User-Agent
- Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
- Country
- United States
- City
- Austin
JSON for this record
{
"countryCode": "US",
"country": "United States",
"firstName": "Ahmed",
"lastName": "Rossi",
"fullName": "Ahmed Rossi",
"gender": "Male",
"birthday": "02/08/1979",
"birthdayISO": "1979-08-02",
"streetAddress": "16 Elm St",
"city": "Austin",
"state": "Texas",
"stateAbbr": "TX",
"zip": "78757",
"phone": "+1 (958) 555-0167",
"email": "ahmed.rossi83@example.org",
"job": "Product Designer",
"company": "Forge Innovations",
"nationalId": "666-71-8048",
"nationalIdLabel": "SSN",
"ipv4": "192.0.2.136",
"mac": "A6:34:67:C8:BA:EC",
"userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36"
}Test data only. This record describes no real person. Numbers are drawn from ranges reserved so they can never be assigned, and the address is not deliverable. Using synthetic data to impersonate anyone, open or verify an account, or evade identity checks is prohibited — see the terms.
Every address here comes from a documentation range
RFC 5737 sets aside three IPv4 blocks specifically for documentation and examples: 192.0.2.0/24 (TEST-NET-1), 198.51.100.0/24 (TEST-NET-2) and 203.0.113.0/24 (TEST-NET-3). These are guaranteed never to be routed on the public internet, and the generator draws from them exclusively.
That is a deliberate choice. A randomly generated public IPv4 address always belongs to somebody — putting one in your documentation, a screenshot or a bug report points a reader at a stranger's infrastructure. Using TEST-NET means anything you generate is safe to publish.
MAC address structure
A MAC address is six bytes, conventionally written as colon-separated hex pairs. The first three bytes are the Organisationally Unique Identifier assigned to the hardware manufacturer, and the last three identify the device within that manufacturer's space.
The second-least-significant bit of the first byte marks an address as locally administered rather than globally unique. The generator always sets it, so every MAC produced here is guaranteed not to collide with a real network card — you will notice the first octet is always 02, 06, 0A, 0E and so on.
Frequently asked questions
Are the generated IP addresses routable?
No. Every address comes from one of the three RFC 5737 documentation blocks — 192.0.2.0/24, 198.51.100.0/24 or 203.0.113.0/24 — which are reserved precisely so they never appear on the public internet. That makes them safe to paste into documentation, screenshots and bug reports.
Can I use these to test geolocation?
No, and no generated address could serve that purpose. Documentation ranges have no geographic allocation at all, so a geo database will either return nothing or a default. For geolocation testing you need real addresses from the region you are targeting, which is a different kind of dataset.
Do the MAC addresses belong to a real manufacturer?
They cannot. The generator sets the locally-administered bit in the first octet, which by definition marks an address as not globally assigned. No registered manufacturer OUI has that bit set, so there is no possibility of collision with real hardware.
What is the User-Agent string for?
Mocking request headers when testing server-side browser detection, log parsing, or analytics pipelines. It is a realistic current-format string rather than a randomly assembled one.