Live Postal Code & E.164 Phone Format Validator
Test any postal code or phone number across 24 markets against official regexes, leading-zero integer traps, NFKC normalization, ITU-T E.164 rules, and regulator drama blocks.
Instant Format Probe
Live Postal Code & E.164 Phone Validator
Check any postal string or telephone number against official regex patterns, leading-zero traps, NFKC full-width input, and regulator drama blocks.
PASS · LEADING-ZERO HAZARD
Normalized: 02108 · /^\d{5}(?:-\d{4})?$/
Matches United States regex /^\d{5}(?:-\d{4})?$/. Leading-zero hazard detected: store as VARCHAR/TEXT and quote in Excel CSV (="...").
PASS · E.164 + REGULATOR SAFE
E.164: +13025550142 · NANPA 555-0100..0199 Drama Block
Valid ITU-T E.164 (+13025550142) inside safe test block: NANPA 555-0100..0199 Drama Block.
REST API
Automate Validation via POST /api/v1/validate
curl -sS -X POST "https://addressqa.com/api/v1/validate" \
-H "Content-Type: application/json" \
-d '{"country":"US","postal":"02108","phone":"+1 302-555-0142"}' | jq . 24-Country Regex Cheat Sheet
Official Postal Regexes & Leading-Zero Risk Reference
| Country | Sample | Regex Pattern | Max Len | 0-Prefix Risk |
|---|---|---|---|---|
| US · United States | 19801 | /^\d{5}(?:-\d{4})?$/ | 10 | 02108 |
| GB · United Kingdom | SW1A 1AA | /^(?:GIR 0AA|[A-Z]{1,2}\d[A-Z\d]? \d[A-Z]{2})$/ | 8 | Low |
| JP · Japan | 150-0001 | /^\d{3}-\d{4}$/ | 8 | 064-0941 |
| CA · Canada | M5V 3L9 | /^[ABCEGHJ-NPRSTVXY]\d[ABCEGHJ-NPRSTV-Z] \d[ABCEGHJ-NPRSTV-Z]\d$/ | 7 | Low |
| DE · Germany | 10117 | /^\d{5}$/ | 5 | 01067 |
| FR · France | 75001 | /^\d{5}$/ | 5 | 06000 |
| AU · Australia | 2000 | /^\d{4}$/ | 4 | 0800 |
| TW · Taiwan | 106 | /^\d{3}(?:\d{2,3})?$/ | 6 | Low |
| SG · Singapore | 049315 | /^\d{6}$/ | 6 | 049315 |
| HK · Hong Kong | N/A (empty) | /^$/ | 0 | Low |
| KR · South Korea | 06164 | /^\d{5}$/ | 5 | 06164 |
| NL · Netherlands | 1012 JS | /^\d{4}\s?[A-Z]{2}$/ | 7 | Low |
| ES · Spain | 28013 | /^(?:0[1-9]|[1-4]\d|5[0-2])\d{3}$/ | 5 | 08002 |
| IT · Italy | 20121 | /^\d{5}$/ | 5 | 00187 |
| CH · Switzerland | 8001 | /^[1-9]\d{3}$/ | 4 | Low |
| SE · Sweden | 111 22 | /^\d{3}\s?\d{2}$/ | 6 | Low |
| NZ · New Zealand | 1010 | /^\d{4}$/ | 4 | 0620 |
| BR · Brazil | 01310-100 | /^\d{5}-?\d{3}$/ | 9 | 01310-100 |
| MX · Mexico | 06500 | /^\d{5}$/ | 5 | 06500 |
| IN · India | 560001 | /^[1-9]\d{5}$/ | 6 | Low |
| MY · Malaysia | 50088 | /^\d{5}$/ | 5 | 01000 |
| AE · United Arab Emirates | N/A (empty) | /^$/ | 0 | Low |
| NG · Nigeria | 101241 | /^\d{6}$/ | 6 | Low |
| TR · Turkey | 34710 | /^(?:0[1-9]|[1-7]\d|8[01])\d{3}$/ | 5 | 06420 |
FAQ
Validator FAQ
How does the validator normalize Japanese full-width input like 〒150-0001?
It runs Unicode NFKC normalization, strips leading 〒 markers, folds Unicode dashes to ASCII hyphen-minus, and validates against /^\d{3}-\d{4}$/ while flagging nfkcChanged: true.
Can I invoke this validator programmatically from CI tests?
Yes — call GET /api/v1/validate?country=US&postal=02108&phone=+13025550142 or POST JSON { "country", "postal", "phone" } to https://addressqa.com/api/v1/validate.