randarium
Test Data

Fake Identifier Generator

Create realistic-looking but non-functional test identifiers in various formats: account numbers, Ethereum addresses, tracking numbers, tax codes, license plates, VINs, and invoice numbers. Perfect for form and data validation testing. This data is test-only and not real.

Also known as: test id · dummy identifier · mock id

seeded · synthetic data

Output

No output yet — set your options and hit .
About this tool, tips & examples

What it does

The Fake Identifier Generator creates format-correct but non-functional identifiers of many shapes: account numbers, Ethereum-style addresses, parcel tracking numbers, tax codes, license plates, VINs, and invoice numbers. Generate up to 10,000 per run, seeded for reproducible fixtures — values that look right and validate structurally, but reference nothing real.

Common use cases

  • Form validation testing — inputs that pass (or deliberately fail) the format checks for VINs, tax IDs, and account numbers.
  • API mocking — realistic identifier fields in mock responses and contract tests.
  • Database seeding — plausible reference numbers for orders, shipments, and vehicles in demo environments.
  • Documentation — example identifiers that can’t collide with a real customer’s data.

Settings

  • Type — account numbers, Ethereum addresses, tracking numbers, tax codes, license plates, VINs, or invoice numbers.
  • Identifiers — 1 to 10,000 per run, exportable as text, CSV, or JSON.
  • Seed — identical seed + settings regenerate the identical list.

Privacy note

Everything is generated locally in your browser and never uploaded. These are test-only dummy values: correctly shaped, but not issued by any authority — no real accounts, vehicles, shipments, or taxpayers behind them.

FAQ

Will these pass validation? They follow each format’s structure and conventions, so pattern-based checks generally pass. Checks that verify existence against an authority (a carrier’s tracking API, a tax registry) will fail — useful for testing both branches.

Could one match a real identifier by accident? For long formats it’s vanishingly unlikely; for short ones (plates) coincidence is possible. Either way, treat every value as fictional and display-only.

What about credit cards, IBANs, or ISBNs? Those have dedicated generators with proper check-digit handling — see Random Credit Card, Random IBAN, and Random ISBN.