Draw a few fake records: a name, an example.com email, a score, and a date. Nothing here is a real person.
1
A mock record is fake data with the shape of a real one. It lets a screen or a test run before a service exists. The names on this page come from a fixed list, and the emails use example.com.
Each row has an id, a name, an email, a score from 0 to 100, and a created date in the last 365 days. The bytes come from crypto.getRandomValues. The people are not real.
Count set to 1, then Generate
[
{
"id": 1,
"name": "Ada Martin",
"email": "ada.martin1@example.com",
"score": 42,
"created": "2026-01-03"
}
]Ada Martin
ada.martin1@example.com
Send the emails, or store them as accounts
Keep them in a fixture or on the screen
Generate draws again. The same count does not repeat the same names. The share link is what freezes a sample.
The created field is a calendar date, YYYY-MM-DD, not a time. It is computed from the clock of this device.
There are 8 first names and 8 last names, so repeats show up once the count grows. The number after the last name in the email keeps two Ada Martins apart.
The share link stores the count and the JSON you see, including edits. Opening the link does not draw new rows. Anyone who has the link can read that JSON.
RFC 2606, published in February 1999, reserves example.com, example.net, and example.org for documentation. Mail to those domains is not delivered to a person.
crypto.getRandomValues is the Web Cryptography API. The W3C Recommendation of 26 January 2017 requires the implementation to use a cryptographic random source, not Math.random.