Developer Random Test Data Generator

Random Test Data Generator

Generate fake names, emails, phone numbers, and addresses for testing forms, seed data, or demos.

All data below is randomly generated and fictional. Phone numbers fall in the 555-0100 to 555-0199 range reserved for fictional use, and every email uses an example domain reserved for testing.
NameEmailPhoneAddress
Patricia Nguyenpatricia.nguyen08@example.net+1 (212) 555-0102587 Elm Drive, Mumbai, MH 400037
Linda Kumarlinda.kumar37@example.com+1 (713) 555-0162720 Highland Street, Austin, TX 83207
John Brownjohn.brown56@example.com+1 (512) 555-0119147 Oak Street, Austin, TX 17635
Linda Davislinda.davis45@example.net+1 (212) 555-0126650 Cedar Lane, Springfield, IL 74731
Carlos Müllercarlos.muller88@example.org+1 (202) 555-0188860 Maple Ave, Springfield, IL 86594
Arjun Silvaarjun.silva67@example.net+1 (212) 555-0144911 Cedar Lane, Mumbai, MH 400068
Mary Nguyenmary.nguyen24@example.net+1 (202) 555-0114911 Elm Drive, Bengaluru, KA 560092
Sofia Kumarsofia.kumar36@example.org+1 (312) 555-0188507 River Road, Mumbai, MH 400067
Arjun Davisarjun.davis79@example.org+1 (312) 555-0170562 Highland Street, Portland, OR 73831
John Smithjohn.smith16@example.org+1 (415) 555-0147208 Park Avenue, Mumbai, MH 400086

How to use this tool

Set the number of records (up to 50) and click Generate. Click Copy JSON or Copy CSV to grab the records in the format your project needs.

What one record looks like

{
  "name": "Siobhán O'Brien",
  "phone": "+1 (312) 555-0147",
  "email": "siobhan.obrien42@example.org",
  "address": "418 Cedar Lane, Mumbai, MH 400053"
}

Copy JSON gives an array of objects like this one. Copy CSV gives the same four fields with a header row, every value in double quotes, so the commas inside an address and the apostrophe in O'Brien can't split a column. Postal codes follow each country's pattern: a 6-digit PIN for Mumbai and Bengaluru, M5V 2T6-style codes for Toronto, M1 4BT-style for Manchester and 5-digit ZIP codes for the US cities, which is enough to catch a form that only accepts one of those shapes.

Why these values specifically

Names and cities come from a mixed pool (Priya Sharma, Wei Chen, Carlos Silva), and a few names carry accents or an apostrophe: José, Zoë, Müller, O'Brien. Those are the ones that break a form that only accepts A–Z, or a query that isn't escaping quotes. The email for such a name uses a plain version (O'Brien becomes obrien), so the address itself stays valid everywhere. Phone numbers pair a real US area code with a line number from 555-0100 to 555-0199, the only 555 numbers that NANPA keeps reserved for fictional use; other 555 numbers can be assigned to real services.

Frequently Asked Questions

Do the address, phone number and email in a record match each other?

No. Each field is chosen independently, so a record with a Mumbai or Toronto address still gets a US-format +1 phone number, and the email is built from the name plus two random digits at one of the three example domains. That is fine for filling forms and seeding tables, but not for testing validation that checks a phone number against its country.

Are these email addresses real, and could they accidentally send mail somewhere?

No. Every address ends in example.com, example.org or example.net, the three domains RFC 2606 reserves for documentation and testing, so they can never belong to a real person or company. Mail sent to them goes nowhere.

Is this data suitable for realistic load testing?

For functional testing (does the form validate correctly, does the table render), yes. For genuine load or performance testing at scale, you may want a larger, more varied dataset than the 50-record cap here — but for everyday development, QA, and demo purposes, this covers the common case of needing a quick batch of plausible-looking records.

Related Tools

Related Blog Posts