Transparent implementation and limits
How ICCID Generator works
See how the tools produce and inspect ICCID test data, how results are checked, what stays in your browser, and where the tools' limits begin.
ICCID Generator is an independent utility for developers, QA engineers, telecom operations teams, and learners. It is not a mobile carrier, SIM issuer, activation service, official IIN registry, or standards body.
Who the site is for—and why it exists
The tools support software testing, database fixtures, API validation, interface demos, inventory cleanup, and technical education. They help users create or inspect identifiers without pretending that generated data represents a subscriber, active SIM, or carrier account.
ICCID utilities often blur three different questions: whether a value has the expected structure, whether its checksum is correct, and whether it was actually issued. This site keeps those questions separate. A mathematically valid result can be useful in development, but it is not evidence of issuance, ownership, activation, network access, or account status.
How ICCID test values are generated
The generator builds the current 19-digit E.118 test structure used throughout this site. It requires a 2–18 digit prefix beginning with the telecommunications identifier 89, fills the rest of the 18-digit body from either a browser-random or deterministic seeded digit stream, then calculates the final Luhn check digit.
- Preferred entropy
- Web Crypto random bytes
- Digit sampling
- Reject bytes 250–255 before modulo 10
- Batch uniqueness
Set-based collision removal- Final digit
- Luhn modulus-10 calculation
Unbiased decimal sampling
When Web Crypto is available, random bytes come from crypto.getRandomValues. Values from 250 through 255 are discarded before modulo-10 conversion, so each decimal digit maps from the same number of byte values. Older browsers may use a local compatibility fallback.
Uniqueness and prefix capacity
A Set removes collisions inside the current batch. The generator also checks the remaining suffix capacity before starting, so it rejects a request when a long prefix cannot produce the requested number of unique values.
Reproducible seeded fixtures
Seeded mode fixes the algorithm identifier as iccid-seeded-sha256-v1. The seed is trimmed, normalized to Unicode NFC, encoded as UTF-8, and length-framed with the algorithm identifier and prefix before a four-byte counter is hashed with SHA-256. Digest bytes 250–255 are rejected before modulo 10, matching the unbiased decimal mapping used by random mode.
The requested count is deliberately excluded from the hash input. Therefore, increasing only the count preserves every earlier value in the same order. The public JSON known-answer vectors and CSV known-answer vectors lock the algorithm, normalization behavior, and expected output for independent implementations.
Runtime JSON exports store the normalized seed directly. Runtime CSV exports keep a spreadsheet-safe display column and a separate, lossless Base64url encoding of the normalized UTF-8 seed; decode that field when exact replay matters.
Random mode produces varied fixtures; seeded mode produces intentionally predictable fixtures. Neither mode turns output into issued ICCIDs, security tokens, passwords, authentication keys, or active SIM credentials.
How validation and EF_ICCID decoding work
The bulk validator preserves the original input for reporting, normalizes supported separators, and checks decimal format, the current E.118 19-digit length, the 89 telecommunications industry identifier, the final Luhn digit, and duplicates as separate conditions. A value can pass Luhn mathematics yet fail ICCID conformance when the 89 identifier is absent.
Country and area results are E.164 numbering-resource hints, not a carrier lookup. Issuer boundaries vary, assignments can change, and reliable carrier ownership requires current information from ITU or the relevant national administration.
The decoder converts between printed ICCID digits and the 10-byte EF_ICCID representation defined by ETSI TS 102 221. It handles swapped BCD nibbles and hexadecimal F padding. A conversion result describes representation and structure only; it does not query a device, carrier, or activation database.
How country and area hints are sourced
The active parser uses every geographic and non-geographic calling-code record in the pinned libphonenumber-js 1.13.10 metadata snapshot, published July 30, 2026. That open dataset is a compact rewrite derived from Google libphonenumber metadata. The build records the package version and integrity, preserves the MIT and Apache-2.0 license texts, and generates the browser module and machine-readable resource snapshot from the same checked-in source.
Shared resources stay shared. For example, +1 represents the North American Numbering Plan across 25 listed destinations; the parser does not use later ICCID digits as a telephone area code to guess one country. Likewise, +7, +39, +44, and other shared codes retain all candidate regions.
Non-geographic resources such as +800, +881, +882, +883, and +979 are labeled as services or international namespaces rather than countries. ITU-T E.118.1 is used to interpret 882 and 883 in the global IIN context; digits following that E.164 code remain part of the issuer and account body.
The snapshot does not prove the issuing carrier, current operator, subscriber country, device location, roaming network, assignment, activation, ownership, or network access. It also does not claim to be the live official registry of reserved, spare, reclaimed, or trial E.164 resources.
Read the bundled third-party license notice. The site keeps the high-value generator presets curated separately, so North American and European choices remain first and China is not made the default.
What stays local—and what does not
Generation, checksum calculation, batch deduplication, validation, decoding, barcode rendering, copying, and CSV or JSON creation run in the browser. The ICCID tool modules do not post entered or generated identifiers to this site for processing and do not call a carrier-lookup API.
The pages still retrieve static site files and load Google advertising and consent-related scripts. Those services can make their own network requests under their respective policies; they are separate from the ICCID calculation logic. Google explains how information is used on sites that integrate its services in its partner-sites privacy notice.
It describes the ICCID operations and files you generate—not a claim that the complete web page makes no network requests. Production ICCIDs can still be operationally sensitive; mask them in URLs, analytics, screenshots, support posts, and general logs.
How implementation accuracy is checked
The implementation is covered by automated tests rather than relying only on visible examples. The current suite verifies:
- published Luhn input and output vectors;
- generated length, requested prefix, uniqueness, and checksum validity;
- seed normalization, fixed SHA-256 known answers, deterministic replay, and stable batch extension;
- rejection of invalid prefixes and impossible batch sizes;
- bulk validation, duplicate detection, and diagnostic results;
- all 215 geographic and non-geographic records in the pinned calling-code snapshot, shared-region preservation, strict input handling, and 882/883 issuer-body boundaries;
- printed ICCID and
EF_ICCIDround-trip conversion; - barcode batch limits, structural rejection, normalization, duplicates, and generated example validity;
- input normalization and malformed-value handling;
- canonical URLs, structured data, internal links, sitemap coverage, PWA assets, and service-worker routes.
Random output changes from run to run, while seeded output must reproduce the published order exactly. Every result must satisfy the same structural invariants. Review dates are changed only after a real implementation or technical-content review.
Primary-source policy
Technical claims are checked against standards bodies and official platform documentation whenever possible. Primary sources take precedence over third-party prefix lists, marketing pages, and unsourced carrier claims.
- ITU-T E.118 — ICCID numbering
- ITU-T E.118.1 — global IIN resources
- Google libphonenumber — open calling-code metadata
- ITU — Issuer Identifier Number guidance
- ETSI TS 102 221 — EF_ICCID coding
- ITU-T E.212 — IMSI numbering
- GSMA SGP.29 — EID terminology
- ISO/IEC 15417 — Code 128 barcode symbology
- GS1 — GS1-128 and FNC1 format
- Apple Support — locating an ICCID
- Android Developers — identifier access
Independence and limitations
ICCID Generator is an independent utility and is not affiliated with, endorsed by, or operated by the ITU, ETSI, GSMA, Apple, Google, a mobile network operator, or a SIM manufacturer. Standards and product names belong to their respective owners.
The site cannot confirm whether an ICCID exists, is active, belongs to a person or account, maps to a current carrier, or grants network access. Only the responsible issuer or carrier can confirm those facts.
Methodology and privacy boundaries last reviewed August 12, 2026. The statements on this page describe the published browser implementation and its current third-party page integrations.
Choose the tool that matches the question.
Generate fixtures, validate an imported batch, create Code 128 labels, decode EF_ICCID bytes, audit the checksum, or read the standards-based guide.