For developers, QA, and telecom operations

Bulk ICCID Validator & Checker

Paste up to 500 SIM or eSIM ICCID numbers. Check the current E.118 19-digit length, telecommunications industry identifier, Luhn checksum, country-code hint, and duplicates—all in your browser.

Validator / 01

Validate an ICCID batch

Enter one ICCID per line, or separate values with commas. Spaces and hyphens inside a number are ignored.

0/500

Maximum 500 entries. Input and results stay on this device.

This is a structural check, not a carrier lookup or activation check.

Ready for a batch

Results will include the validation status, country or area hint, actual and expected check digits, duplicate flags, and a clear reason.

Worked example / 02

ICCID checker example: valid vs invalid.

The final digit changes the result even when the other 18 digits are identical. This example makes the validator's format checks easy to verify.

Valid: 8910112345678901238

This value contains 19 digits, begins with the telecommunications industry identifier 89, and passes the Luhn checksum with a final check digit of 8.

Invalid: 8910112345678901234

The body is unchanged, but the final digit is 4. The Luhn calculation expects 8, so the checker reports a checksum failure instead of silently accepting it.

What a pass does not prove

A valid format and checksum do not prove that a SIM or eSIM exists, is active, or belongs to a particular carrier account. Use these results for structural testing only.

Test input Length 89 MII Luhn Expected diagnosis
8910112345678901238 19 Yes Pass Valid 19-digit ICCID format.
8910112345678901234 19 Yes Fail Actual digit 4; expected final digit 8.
891011234567890123 18 Yes — Incomplete for this validator; use the Luhn calculator to generate the final digit.
9910112345678901237 19 No Pass Checksum passes, but the value is outside the 89 telecom ICCID space.
Same valid value twice 19 Yes Pass Each row remains traceable; later occurrences are flagged as duplicates.

CSV evidence: the downloadable report preserves the row number and original input alongside the normalized value, result, country hint, actual and expected check digits, duplicate flag, and diagnostic reason.

What this ICCID checker verifies.

The validator deliberately separates mathematical validity from real-world activation. A correct checksum is useful for QA, but it cannot prove that a SIM exists or belongs to a carrier account.

Industry identifier

Common telecommunications ICCIDs begin with the Major Industry Identifier 89. Values with another prefix are flagged even if their checksum passes.

Length and digits

This mode checks the current E.118 19-digit length. It rejects letters and reports the exact number of digits found for faster test-data cleanup.

Luhn check digit

The final digit is recalculated from the preceding body. Failed rows show the expected digit so developers can diagnose fixture errors quickly.

Reference / E.118

Grounded in the current ITU numbering model.

ITU-T E.118 (09/2025) specifies that the PAN used as the ICCID is 19 digits long and explains the role of issuer identification numbers. For authoritative issuer assignments, use maintained ITU IIN publications rather than a static carrier guess.

FAQ / 04

ICCID validation questions

Clear boundaries for format checks, activation, privacy, and issuer-specific numbering.

What does this ICCID validator check?

It checks that each value contains 19 digits, starts with the telecommunications industry identifier 89, and has the correct final Luhn check digit. It also reports versioned E.164 country, area, or service hints and duplicates; shared resources stay shared.

Does a valid result mean the SIM is active?

No. A valid result only confirms structural format and checksum. It does not prove that a SIM or eSIM exists, is active, or belongs to a particular carrier account.

Can I validate 20-digit ICCIDs?

Current ITU-T E.118 defines a 19-digit PAN. This batch tool validates that length; 18-digit bodies and 20-digit interface values may be investigated with the decoder, but converter acceptance does not make them conformant ICCIDs.

Are pasted ICCIDs uploaded or stored?

The ICCID validation module parses, checks, copies, and creates CSV reports in the browser without sending entered values to this site's processing server. The page still loads site files and Google advertising and consent services; see the methodology page for the exact boundary.