UK Name & Persona Generator
A UK name generator produces fictional British personas by combining common forenames and surnames at random.
Names are drawn from forenames and surnames that are common across the United Kingdom and combined at random, so a persona is a coincidence of two ordinary names rather than a real individual. Email addresses use example.com, which RFC 2606 reserves for documentation and testing, so generated addresses cannot deliver mail.
Options
| Name | Type | Default | Description |
|---|---|---|---|
count | integer | 10 | How many records to return, from 1 to 1000. |
seed | integer | — | Optional. Any integer. The same seed with the same options always returns the same records. |
Use cases
- User fixtures: Populate test accounts and demo records with plausible British names.
- Character-set testing: Include names with apostrophes and diacritics to catch encoding and escaping bugs.
- Screenshots and documentation: Illustrate an interface without exposing a real customer.
REST API
GET /api/v1/names/random
curl "https://ukaddressgenerator.org/api/v1/names/random?count=10"
{
"status": "success",
"count": 1,
"data": [
{ "firstName": "Aisha", "lastName": "Campbell", "fullName": "Aisha Campbell", "jobTitle": "Test Analyst", "email": "aisha.campbell42@example.com", "username": "aishacampbell318" }
]
}
Frequently asked questions
- Could a generated name match a real person?
Common names combined at random will sometimes coincide with a real person’s name. No personal data is used to produce them, and the accompanying addresses and contact details are fictional.
- Are the email addresses real?
No. They use example.com, a domain reserved by RFC 2606 that cannot receive mail.
Building believable British test personas
Names, encoding and the cases that break systems · 200 words
1. Names are a character-set test
British names include apostrophes (O'Brien), hyphens (Featherstonehaugh-Smith), diacritics (Siân, Ffion) and non-Latin origins across a diverse population. Systems that strip or reject these characters fail for real users, and the failure is usually discovered in production.
Include awkward names in fixtures deliberately. If a name with an apostrophe breaks your SQL, the bug is an injection vulnerability, not a data problem.
2. Why random pairing is safe
Personas combine common forenames and surnames at random. Because both are common, a generated name will occasionally coincide with a real person's — but no personal data was used to create it, and the address, telephone number and email attached to it are all fictional or reserved.
3. Reserved domains for email
RFC 2606 reserves example.com, example.org and example.net for documentation and testing. Nothing can be delivered to them, which makes them the correct choice for generated email addresses — unlike a made-up domain, which someone may later register.
curl "/api/v1/names/random?count=10&seed=42"
More questions
- Are titles such as Mr, Ms and Dr included?
No. Titles are a separate design decision and often better handled as an optional free-text field, since fixed lists exclude people.