Fake Identity Generator for Database Seeding

Populate a database with thousands of realistic, fictional records ready to load straight in.

Updated June 2026

100% fictional
Format-valid test data
Free, no sign-up

Shelia T. Nitzsche

4193 S State Street
Markshaven, Nebraska 03439
United States

✓ Fictional test data — not a real person

Personal

SexFemale

Mother's maiden nameKessler

SSN956-75-XXXXFormat only — never issued, safe for testing.

Geo coordinates32.59843, -96.85127

Phone

Phone305-555-0176

Country codeUS

Birthday

BirthdayJanuary 1, 1978

Age48 years old

Tropical zodiacCapricorn

Online

Email addresssnitzsche22@rhyta.com

Usernameunhealthy1913

Passwordkk2FKCRTRy

Websiteragged-secrecy.org

Browser user agentMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36

Finance

Credit card typeDiscover

Card number6011111111111893Sandbox test number — non-chargeable.

CVV2246

Expires09/31

CurrencyUSD

Physical

Height5' 5" (165 cm)

Weight162.3 pounds (73.6 kg)

Blood typeA-

Hair colorBlack

Eye colorHazel

Tracking numbers

UPS tracking1Z 343 331 45 1169 348 7

Western Union MTCN1512114515

MoneyGram MTCN54790452

Other

Favorite colorred

Vehicle1999 Citroën F-150

License plateRB82ZKH

GUIDfe11be4a-12af-4ef3-9036-052ccd64dd45

This is randomly generated fictional data for software testing, QA, and privacy. It does not describe a real person. Any resemblance to a real individual is coincidental.

Empty tables make for unconvincing demos and untested queries. Seeding a database with realistic fictional records lets you test performance, build representative dashboards, and exercise relationships at scale before any real data exists.

The bulk generator exports up to 100,000 records as SQL INSERT statements, CSV or JSON, with the exact fields you choose. Generation is deterministic, so the same seed reproduces the same dataset — handy for committable fixtures and reproducible CI.

How the generator helps with database seeding: Export up to 100,000 records at once; Ready-to-run SQL INSERT statements, CSV or JSON; Pick exactly which fields to include; Deterministic — reproduce the same dataset from a seed.

What a generated identity gives you for database seeding

Field	Format	Why it's safe
Name	Locale-aware first + last	Randomly combined; describes no real person
Address	Real city + valid ZIP, random house #	Never resolves to a real residence
Phone	Valid national format	US uses the 555-0100…0199 fiction range
Email	name@example-style domain	Format-valid placeholder, not a live inbox
National ID	Country-labeled, masked placeholder	Not a real local-format identifier
Credit card	Luhn-valid	Sandbox test BIN — non-chargeable

Every field is fictional and safe to use for database seeding — it describes no real person and cannot collide with a real identifier.

Frequently asked questions

What format should I use to seed a SQL database?+

Export as SQL INSERT statements to load directly, or CSV/JSON if your tooling imports those. The bulk generator escapes values safely so the SQL is injection-safe.

Other use cases

Popular generators

Free validation tools

Sources

ISO 3166 — Codes for country names and subdivisions — ISO
ITU-T E.164 — International telephone numbering plan — ITU
Universal Postal Union — Addressing and postal code standards — Universal Postal Union