Articles · Identity

What's new in Identity tools

Telecom format checks, GS1 product codes, securities ids, and UUID validation expanded in recent batches. Use this map when you have an acronym or digit string—not when you need a live registry lookup.

Identity tools generate and validate IDs you paste from tickets, spreadsheets, or device logs. Recent batches added telecom and supply-chain format checks, UUID validation, and GS1-style product identifiers—all local, with no registry lookup unless a page says otherwise.

Generate and validate core IDs

  • Open the Identity hub for UUID v4/v7, ULID, Nano ID, and MongoDB ObjectId in one place.
  • UUID validator — bulk-check version and variant bits on pasted GUID lists.
  • E.164 phone normalize — strip formatting and validate ITU-style lengths.

Telecom and device identifiers

Product, location, and government codes

Financial, media, and securities ids

For SSH fingerprints, color checks, and print-size helpers from an earlier batch, see identity, color, and media checks. For picking UUID vs ULID vs Nano ID, see UUID, ULID, ObjectId, or Nano ID?

Common use cases

  • Validate a column of IMEI or ICCID values from a support export before importing.
  • Check GTIN or UPC check digits on a SKU list without a spreadsheet macro.
  • Bulk-validate UUID version bits on log extracts.

Common mistakes to avoid

  • Expecting format checks to confirm ownership

    Checksum pages verify shape and math—they do not query carrier, publisher, or government registries.

  • Confusing ID generators with secrets

    UUID and Nano ID generators make public identifiers—do not use them alone for session tokens or passwords.

FAQ

Why is IMEI under Protocol in search but Identity here?

Some checksum tools appear in both browsing contexts; the href is the same—open whichever tab you are already using.

Do these tools upload identifiers?

Client-labeled pages process pasted text locally in your browser tab.