USPS tracking format
ClientValidate common USPS tracking patterns.
USPS 22-digit format OK
Nearby workflows on Toolcore
- UPS tracking format — Validate UPS 1Z tracking pattern. when another identifier column uses a different checksum ruleset.
- FedEx tracking format — Validate common FedEx tracking numbers. when another identifier column uses a different checksum ruleset.
- Luhn checksum (mod 10) — Paste a digit string (spaces ignored)—pass or fail Luhn for PANs, IMEI-style IDs, and test vectors; browser-only. when another identifier column uses a different checksum ruleset.
- GTIN checksum (EAN / UPC) — Paste GTIN‑8, UPC‑A (GTIN‑12), EAN‑13, or logistic GTIN‑14 digits—ISO GS1 modulus‑10 parity without GS1 lookup—browser-only. when another identifier column uses a different checksum ruleset.
About this tool
Catch typos before carrier lookup.
Common use cases
- USPS tracking format for quick local checks without uploading data.
- Copy results into tickets, docs, or classroom notes.
Common mistakes to avoid
Unexpected input shape
See the intro and how-to notes for accepted formats.
FAQ
Is processing local?
Yes—this runs entirely in your browser.
Agent prefill?
Use q or qb for the main text field when supported.
More tools
Related utilities you can open in another tab—mostly client-side.
UPS tracking format
ClientValidate UPS 1Z tracking pattern.
FedEx tracking format
ClientValidate common FedEx tracking numbers.
Luhn checksum (mod 10)
ClientPaste a digit string (spaces ignored)—pass or fail Luhn for PANs, IMEI-style IDs, and test vectors; browser-only.
GTIN checksum (EAN / UPC)
ClientPaste GTIN‑8, UPC‑A (GTIN‑12), EAN‑13, or logistic GTIN‑14 digits—ISO GS1 modulus‑10 parity without GS1 lookup—browser-only.