Form fixture
- Input
- test form → required identifier field
- Expected output
- U.S. passport number → plausible synthetic value
Use it when a form needs to accept U.S. passport number without depending on real data.
U.S. passport number in privacy-first sandboxes
U.S. passport number in privacy-first sandboxes
This page focuses on using synthetic U.S. passport number in test scenarios. The goal is plausible data without touching real identifiers or implying official validation.
How to use synthetic U.S. passport number safely
- The tool generates synthetic U.S. passport number following synthetic 9-digit numeric format. That is enough for masks, fixtures and contract tests that depend on plausible format.
- there is no promise of a public checksum or Department of State issuance.
- Use it for travel-form tests, simulated KYC and payloads that do not verify real documents. Do not send the value to real verification, official registration, credit, employment, KYC or government services.
Useful test scenarios
Local rule test
- Input
- mask / prefix / check digit
- Expected output
- accepted locally → never treated as verified identity
The local rule covers synthetic 9-digit numeric format; it does not cover official lookup or registry existence.
Full tool FAQ
There is no simple public checksum to validate issuance from the number alone.
Frequently asked questions
Is synthetic U.S. passport number a real document?
No. It is a test value with plausible format or digits, without lookup in official databases.
What is the key limitation when using U.S. passport number in tests?
there is no promise of a public checksum or Department of State issuance.
How can privacy risk be reduced?
Generate the value in the browser, do not store it in URLs or logs, and ensure analytics receives only action metadata, never the identifier.