ICCID checker

Client

ICCIDs label the physical or eSIM profile card. This page mirrors the public Luhn check digit used in E.118 and common operator prints—pair with IMEI check when you are auditing handset plus SIM paperwork together, or generic Luhn for other mod‑10 identifiers.

Privacy: digits are evaluated only inside your browser. There is no carrier, GSMA, or SM-DP+ query—format math only. Treat SIM identifiers like any sensitive operational paste.
?

The ITU‑T E.118 layout follows ISO/IEC 7812 for card identifiers: a Major Industry Identifier (telecom ICCIDs usually start with 89), an issuer/country/account block, then a trailing Luhn mod‑10 check digit using the same doubling rule as many payment PAN validators. Printed cards commonly show 18–22 digits; issuers pin one length profile per range.

Result

Passes Luhn mod 10 on the full 19-digit string.

  • MII (first 2): 89
  • Issuer / account core (between MII and check): 3530012345678901
  • Check digit (last): 1

Common use cases

  • Sanity-check a SIM shipment CSV before uploading ICCIDs into an inventory tool that expects Luhn-valid rows.
  • Compare a camera snapshot of the card against the printed digits your activation portal shows.
  • Explain to support why a single transposed digit fails Luhn even when the issuer prefix looks familiar.
  • Cross-check documentation that cites E.118 without implying live HLR access.

Common mistakes to avoid

  • Assuming MII 89 proves the SIM is activated or financed

    The prefix is standardized for telecom numbering plans—not service status or billing readiness.

  • Rejecting uncommon lengths outside 19–20

    Issuers standardize internally, but this helper accepts pasted samples between documented min/max guards while staying honest about uncertainty.

  • Mixing ICCID up with IMSI or MSISDN

    Those identifiers use different numbering spaces; keep SIM serial fields separate from subscriber directory numbers.

FAQ

Is my ICCID sent to Toolcore servers?

No—all arithmetic happens in your tab.

Does this activate or deactivate a SIM?

No. There is no provisioning API call—only digit cleanup and the Luhn checksum from public specifications.

Why allow up to 22 digits?

Some operator and IoT profiles print longer BCD-friendly fields; the guard rails stay wide enough for common physical reads while rejecting obvious noise.

Common search terms

Phrases people search for that match this tool. See the full long-tail keyword index.

  • iccid validator luhn online
  • sim card iccid checksum check browser
  • e118 iccid validate digits locally
  • telecom iccid mii 89 checker
  • integrate circuit card id luhn mod 10

More tools

Related utilities you can open in another tab—mostly client-side.