Step-by-step check of a valid SSN
- Input
- 512-34-9081
- Expected output
- 3 de 3 checagens aprovadas (área, grupo, serial)
Area 512 inside 1-899 and not 666: pass. Group 34 not 00: pass. Serial 9081 not 0000: pass.
Carregando ferramenta… / Loading tool…
SSN validation rules
The central fact about the SSN is what it lacks: no digit computed from the others confirms the number. Structural validity comes entirely from a list of ranges the SSA declared out of use.
Area 512 inside 1-899 and not 666: pass. Group 34 not 00: pass. Serial 9081 not 0000: pass.
The 900-999 range was never used for an SSN; it is exactly the range the ITIN occupies on purpose, which makes the two formats mutually exclusive by construction.
The same area and serial from the first example are enough to show that any single field outside its accepted range invalidates the whole number.
No. Common validation is based on structure and excluded ranges, not a checksum.
No. There is no modulo calculation or weighted sum involved; the only check is confirming area, group and serial fall outside the ranges the SSA never used.
Not since June 25, 2011, when the SSA switched to randomized assignment. The old area-to-state mapping only holds for numbers issued before that date.
Because the SSA reserved that range outside the SSN; it overlaps with the range the IRS uses for the ITIN, which always starts with 9, so a valid SSN never shares its first digit with an ITIN.
The generator automatically remaps it to 667, because 666 sits on the SSA exclusion list and could never come out as a valid number.
Generation happens locally in the browser. Analytics receives only action, status, type and format, never the generated SSN.