How the database is built
The decoder answers from a database we built and maintain ourselves. This page explains where its entries come from, how they're checked, and where it falls short.
Where the entries come from
Every entry maps a TAC (the first 8 digits of an IMEI) to a device: brand, model and device type. The core of the database is a TAC catalogue we bought outright several years ago and have maintained since. On top of that, we add TACs our own team confirms from real customer orders.
We don't copy spec sites or resell another decoder's answers: TACs seen only through third-party lookup services are kept out of this database. When a TAC isn't in the database, the API says so (found: false) rather than guessing, and the TAC is queued so it can be filled the next time that device turns up in real use.
How entries are checked
- New TACs are added only when our team confirms the device from a real order, never inferred from a similar code or taken from another decoder.
- Every entry carries its provenance internally (bought catalogue or confirmed by us), and only those two kinds are ever served.
- Corrections reported to us are reviewed and, once confirmed, fixed in the database, so every later answer reflects the fix.
How fresh it is
The database grows as our team confirms new devices; the decoder reads it live, with answers cached for up to a day. It currently holds 180,914 TACs across 112,986 models and 6,144 brands. Last changed 7 October 2026.
Known gaps
- Brand-new models. A phone released in the last few weeks may not be in the database until one has been seen.
- Regional variants. Manufacturers often allocate separate TACs per market; a less common regional variant can be missing while its siblings are present.
- Low-volume and unbranded devices. Obscure brands and white-label handsets are covered less consistently than mainstream ones.
- Identification only. The database says what a device is, never whether it is blacklisted, carrier-locked or under warranty.
Corrections
Spotted a wrong model for a TAC? Use “Report this endpoint” on the TAC lookup page and include the TAC and the correct device.
Published by fourzerotwo · last reviewed 11 October 2026