Random names, emails, phones, SNILS, INN, Russian passport. Checksum validation, GOST 7.79 transliteration, JSON / CSV / SQL export. Test data only — not PII.
All data is generated fully at random — nothing corresponds to real people. INN and SNILS pass their respective checksums (Russian FNS / PFR algorithms), but they aren't real documents. Use only for testing, development, learning and populating mockups.
Transliteration & validation
GOST 7.79
email from name · SNILS with checksum
Email and login are built by transliterating the name via GOST 7.79-2000 system B. SNILS is generated with a valid checksum per the PFR algorithm. Individual INN (12 digits) uses the FNS algorithm with two check digits.
Export
JSON/CSV/SQL
cards → JSON → CSV → SQL INSERT
Three export formats: JSON — for API mock data and fixtures, CSV — for import into Excel/databases, SQL — ready INSERT statements to populate a test DB. CSV delimiter is comma (configurable).
Famous IT people
Special mode
Gates · Jobs · Musk · Torvalds · Lovelace
In 'Famous' mode — real names from IT and business (for testing directories and autocomplete). Other fields (email, SNILS, INN) remain random and unrelated to the real people.
04
Frequently asked questions
Press generate and you get a full set: name, gender, date of birth, address, phone, email and documents. The list of fields is configurable, personas can be produced in batches, and the batch exports as JSON, CSV or a ready SQL insert for seeding a test database.
No. Values are assembled at random from lists of common names, surnames, cities and occupations; no database of real individuals is involved. A coincidence with a living person is possible the way namesakes coincide, but the fields within one persona are not linked to each other in any way.
It might be, and you should not call it. The operator code comes from a list of genuine Russian prefixes while the remaining digits are random, so the number can belong to an actual subscriber. Use it to test input masks and formats, never to send a message or place a call.
You should not. It exists for testing and demonstration — filling a form during development, showing an interface in a screenshot, seeding a training database. Registering with invented details breaks the terms of most services and leaves you locked out when account recovery asks for them.
So that development databases never hold real personal data. Production data in test environments is a classic source of leaks: those databases are protected less carefully and end up on laptops and in shared folders far more often. Synthetic records remove that risk completely.
No. Everything is assembled in your browser from word lists shipped inside the page, with no network request at all. Generated personas are stored nowhere and cannot be reproduced — close the tab and the batch is gone. Only the name of the opened tool is sent, for a popularity counter.