Protocol scope and method
This tool checks the common 20-digit shape and displays segments without claiming that administrative or industry codes are assigned correctly.
valid shape = exactly 20 decimal digits.
Diagnostic scenario
Enter a synthetic or redacted device identifier at the exact expected width. Check decimal syntax and expose each business-code segment, then compare region, industry, type and sequence assignments with the project registration data.
How to interpret the result
A syntactically valid digit string is not evidence that the identifier was legitimately assigned, registered or authorized. Code tables can depend on the selected edition and administrative data, and leading zeros are significant.
Input reference
- Device or channel ID
- Example default: Sample input included
Common mistakes
- Using an unredacted production capture with vehicle, credential or network identifiers.
- Using real production identifiers in public diagnostics.
- Treating a successfully parsed sample as standards compliance or interoperability proof.
Before using the result
- Confirm the protocol edition, transport framing and vendor profile before interpreting fields.
- Verify segment meaning against project registration records.
- Keep a redacted known-good and known-bad sample as a regression pair.
Questions to check during diagnosis
Does the GB/T 28181 Device ID Structure Check leave my browser?
No application upload is used. Avoid putting sensitive production data in shareable URLs.
Is this a standards compliance test?
No. Confirm the edition and vendor profile with licensed documents and your target platform.
Offline diagnostic aid. Verify fields, version and vendor extensions before production use.