Contact

Validatelist is maintained by a small, independent team. If you spot something wrong, or want to see a new ID type covered, this is the page for that.

Report an error

Found a validator that flags a value incorrectly, cites the wrong format, or links to a dead registry URL? Please tell us. The most useful reports include:

• The validator page (URL or ID type + country)
• The value you tested (or a similar example, if the real one is sensitive — see note below)
• What you expected vs. what the validator showed

Email admin@validatelist.com. A dedicated feedback form may be added to this page in the future; email is the reliable channel for now.

A privacy note on sending examples: because Validatelist never transmits what you type into a validator (see the privacy policy), any value you choose to include in an email is something you are actively sending us, not something the site captured. If a real ID number is sensitive, send a made-up value in the same format instead — that's usually enough to reproduce a formatting or checksum bug.

Suggest a new validator

Want to see a country or ID type we don't cover yet? Send the ID type's name, the issuing country or body, and a link to the official specification or registry if you have one, toadmin@validatelist.com.

Corrections policy

ID formats change when issuing bodies revise their standards, and we won't always catch that the moment it happens. When a correction is confirmed against an official source, we update the validator page directly — there's no separate errata list to check, the live page is the correction. See About & methodology for how validators are built and reviewed.

General questions

For anything else — how a checksum algorithm works, whether Validatelist can be used in another project, press or partnership inquiries — the same address works:admin@validatelist.com.