About

Registration forms collect personal data you may not want to disclose. Providing real information to untrusted websites exposes you to spam, phishing, and identity correlation attacks. This generator produces structurally valid but entirely fictitious identities: names drawn from demographic frequency tables, addresses with format-correct ZIP codes, Luhn-valid card numbers on non-issuer BINs (prefix 4 test ranges), and SSNs in the 900 - 999 reserved block. Every field passes typical form validation regex without referencing any real person.

The tool supports multiple nationalities and genders. Generated phone numbers follow E.164 formatting conventions. Email addresses use plausible username patterns combined with common domain suffixes. Note: these identities will not pass KYC or government verification. They are intended strictly for form testing, UI development, and privacy-preserving signups on low-trust platforms. Pro tip: always check a site's Terms of Service before using generated data for registration.

Formulas

Credit card numbers are validated using the Luhn algorithm. Given a card number sequence, the checksum is computed as follows:

n∑i=1 d_i′ ≡ 0 (mod 10)

Where d_i′ is obtained by doubling every second digit from the right. If the doubled value exceeds 9, subtract 9. The check digit d₁₆ is chosen so the total sum is divisible by 10.

Password entropy is calculated as:

H = L ⋅ log₂(N)

Where L = password length, N = size of the character pool (lowercase + uppercase + digits + symbols = 94). A 12-character password yields H ≈ 78.7 bits.

UUID v4 generation uses 122 random bits with version nibble set to 0100 and variant bits to 10, yielding 2¹²² ≈ 5.3 × 10³⁶ unique identifiers.

Reference Data

Field	Format / Standard	Example	Validation
Full Name	First + Last (cultural)	James Mitchell	Alpha + spaces
Email	RFC 5321	[email protected]	Regex pattern
Phone	E.164 / national	+1 (555) 234-8901	Digit count
Date of Birth	ISO 8601	1987-03-14	Age 18 - 85
SSN	AAA-BB-CCCC (US)	912-45-6789	900 - 999 prefix (non-real)
Credit Card	16 digits, Luhn-valid	4532 0151 2345 6781	Luhn checksum = 0 mod 10
CVV	3 digits	847	Numeric, 3 chars
Address	Street, City, State ZIP	742 Oak Ave, Portland, OR 97201	Format match
Username	Alphanumeric + underscore	james_m87	Regex [a-z0-9_]
Password	Mixed case + digits + symbols	kX9#mPq2!vL	Entropy ≥ 60 bits
UUID	RFC 4122 v4	a3f4b2c1-...	Hex + hyphens
MAC Address	IEEE 802	4A:3B:2C:1D:0E:FF	6 hex octets
IP Address	IPv4 dotted decimal	192.168.45.12	0 - 255 per octet
User Agent	HTTP header string	Mozilla/5.0 (Windows...)	Standard format
Blood Type	ABO + Rh	A+	8 valid types
Height	cm / ft-in	178 cm / 5'10"	Range 140 - 210
Weight	kg / lbs	76 kg / 168 lbs	Range 45 - 140
Company	Name + suffix	Vertex Solutions Inc.	Dictionary
Job Title	Role string	Senior Data Analyst	Dictionary
Zodiac Sign	Western astrology	Pisces	DOB-derived
Favorite Color	Hex + name	#7C9EE5 (Soft Blue)	Valid hex

Frequently Asked Questions

No. The card numbers pass Luhn validation (checksum mod 10 equals 0), but they use test BIN prefixes that do not correspond to any real issuing bank. They will be rejected by any payment processor. They are suitable only for form validation testing.

Names are assembled by randomly combining entries from frequency-ranked first name and surname dictionaries. The probability of matching a real individual with the exact same name, address, and date of birth is astronomically low. SSNs use the 900-999 area number range, which the SSA has reserved and never issued to real persons.

The North American Numbering Plan reserves the 555 prefix (specifically 555-0100 through 555-0199) as fictional numbers. Using this range ensures the generated number cannot reach a real subscriber, preventing accidental harassment.

Age follows an approximate normal distribution centered around 32 years with a standard deviation of 12, clamped to the 18-85 range. This produces a realistic demographic spread rather than uniform randomness, which would over-represent elderly and very young adults equally.

Yes. All dictionaries and algorithms are embedded in the client-side code. No network requests are made during generation. The tool functions identically with or without an internet connection.

The pool includes 26 lowercase, 26 uppercase, 10 digits, and 32 special characters (94 total). A 16-character password from this pool yields approximately 104.9 bits of entropy, exceeding the NIST SP 800-63B recommendation of 80+ bits for high-security applications.