"Compromised" on a CheckMend report means the device's serial has a recorded history event, such as a loss report, theft report, settled insurance claim, or network block, in CheckMend's own database. It is CheckMend's vocabulary, not a GSMA status, and the two databases do not always agree.
- Compromised is CheckMend's umbrella term for a device whose history checks did not all come back clear. It is provider-specific wording, not an industry-wide status.
- CheckMend is powered by Recipero and draws on police, insurer, retailer, recycler, and network records, so it can flag events the GSMA Device Registry never sees.
- A lot can be compromised on CheckMend and clean on GSMA at the same time. That is a data-source difference, not an error.
- For a bulk purchase decision, do not pick one database. Screen the manifest against both and treat any red flag from either as a title or resale risk.
- Get the check date and the exact result vocabulary into the deal terms, so a dispute is about a documented snapshot, not memory.
What is CheckMend?
CheckMend is a device-history checking service operated by Recipero. Where a plain blacklist check asks one question, "is this IMEI flagged as lost or stolen right now," CheckMend runs a serial number against a much wider set of records: police and public loss/theft reports, settled insurance claims, network block data, retailer and recycler records, and its own crowd-reported incidents. Recipero states its datasets cover tens of billions of serial numbered items.
That breadth is the whole point, and it is also why CheckMend results confuse traders. The report is not answering "will this phone work on a network." It is answering "does this device have any recorded history that could affect legal title or resale value." Those are different questions with different answers.
What does "compromised" actually mean?
On CheckMend, a device is described as compromised when one or more of its history checks returns a warning instead of a clear result. CheckMend reports use a traffic-light convention: each individual check comes back green (clear), amber or orange (caution), or red (warning). A report where everything is green is a clean report. A report with red or amber results is what CheckMend's own material calls a lost, stolen, or compromised device.
What a compromised result can be driven by:
- A loss or theft report. Reported by the owner, the police, or another source. This can exist even when no network ever blocked the IMEI.
- A settled insurance claim. If an insurer paid out on the device, the insurer owns it. A buyer of that device does not acquire legal title, which makes this one of the most serious flags for a wholesale buyer.
- A current or historical network block. CheckMend distinguishes between a device that is blocked now and one that was ever blocked and later unblocked.
- Clone or counterfeit indicators. The same serial appearing in multiple devices, or a serial reported as used on counterfeit units.
- Ownership records. A registered previous owner or a corporate asset-monitoring record.
The critical nuance: compromised does not tell you which of these fired. Two compromised units can carry completely different risk, one is an insurer-owned theft payout, the other is a phone with a registered previous owner. Always open the per-check detail before pricing the risk.
Trading this stock yourself? Aikon is a live floor for wholesale electronics: registered companies post buy and sell offers and deal with each other directly. Join free.
CheckMend result vocabulary, decoded
These are the result types a CheckMend report works from, and what each one should mean to a wholesale buyer:
| Result on the report | Severity | What it means for a bulk buyer |
|---|---|---|
| All checks clear (clean report) | Green | No recorded history event in CheckMend's datasets at the time of the check. Snapshot, not a permanent guarantee. |
| Currently blocked | Red | A network has the IMEI blocked due to loss or theft. Unsellable as a working phone in enforcing regions. |
| Lost / stolen report | Red | Reported by an owner, the police, or another source. Title risk even if no network block exists yet. |
| Insurance claim settled | Red | The insurer paid out and owns the device. A buyer does not acquire legal title. Walk away or resolve with the insurer. |
| Ever blocked (since unblocked) | Amber | The IMEI carried a block in the past. Worth questioning: who unblocked it and why. |
| Possible clone | Amber | The same serial appears in more than one device. Genuine phones never share an IMEI, so at most one unit is real. |
| Possible counterfeit | Amber | The serial is reported as used on counterfeit devices. Physical inspection required. |
| Registered owner / asset record | Amber | A previous owner or corporate monitoring record exists. Often benign in used stock, but confirm the seller's chain of ownership. |
Format matters here: run every manifest through a free bulk IMEI format check first, so typos and fabricated IMEIs are caught before you pay for history reports on them.
CheckMend vs GSMA vs carrier blacklist: three different databases
Traders use "blacklisted" loosely, but there are three distinct layers. The GSMA Device Registry is the operator-contributed global list of lost, stolen, and finance-defaulted IMEIs. Individual carrier blacklists are what each network actually enforces. CheckMend is a commercial history database that overlaps both and adds records neither holds.
| CheckMend (Recipero) | GSMA Device Registry | Carrier blacklist | |
|---|---|---|---|
| Who runs it | Recipero, a commercial provider | GSMA, the mobile operator industry body | Each individual network |
| Source data | Police, insurers, retailers, recyclers, networks, owner reports | Flags contributed by member operators | That carrier's own loss, theft, and finance records |
| Question it answers | Does this serial have any recorded history event | Is this IMEI flagged lost, stolen, or unpaid by a contributing operator | Will this specific network refuse service to this IMEI |
| Typical vocabulary | Clean vs compromised, per-check green / amber / red | Clean, flagged, or unknown | Blacklisted or not blacklisted |
| What it can miss | Events never reported into its datasets | Insurance claims with no operator flag, incidents from non-contributing carriers and regions | Everything outside that one network |
| Strongest use | Title and provenance risk on used stock | The contractual clean/flagged trigger in wholesale deals | Confirming usability in a specific destination market |
For the GSMA side of this comparison in depth, see what GSMA blacklist status "clean" means, and use the GSMA status decoder to translate raw check results.
Compromised on CheckMend but clean on GSMA: why it happens
This split is the single most common source of confusion, and it is not a glitch. CheckMend and the GSMA Device Registry are fed by different reporters. A theft reported to the police, or an insurance payout, can sit in CheckMend's records without any operator ever adding a GSMA flag. The reverse also happens: an operator flag can reach GSMA before any record lands in a commercial history database.
Typical reasons a unit shows compromised on CheckMend while GSMA says clean:
- Insurance claim, no operator flag. The insurer settled and recorded the claim, but the network was never asked to block the IMEI. GSMA sees nothing; CheckMend sees an insurer-owned device.
- Police or owner loss report only. A report was filed but the owner never contacted the carrier, so no block was propagated to the registry.
- Historical event, since resolved. An "ever blocked" record persists in history data after the operator flag was removed.
- Non-operator records. Retailer, recycler, or corporate asset records exist only on the commercial side. Operators do not contribute this class of data at all.
Which one do you trust for a bulk lot?
Neither, alone. GSMA answers usability: whether networks in enforcing regions will serve the device. CheckMend answers title: whether someone else may have a legal claim on it. A phone can work perfectly and still belong to an insurer. For a purchase decision, a red CheckMend flag on a GSMA-clean unit is a title problem you cannot see from the registry, and it should be treated as disqualifying until the seller documents provenance.
The distinction also runs the other way. A GSMA flag makes a device commercially dead in enforcing markets regardless of what CheckMend says, because carriers act on the registry, not on commercial history reports. The two checks are complements, not substitutes. This is the same reason a device can be "blacklisted" in one country and usable in another; the glossary entry on blacklisted IMEIs covers that regional asymmetry.
Trader playbook: screening a consignment across both
For a bulk lot, screening is a sequence, cheapest check first, so you never pay for history reports on IMEIs that fail basic validation:
- Get the manifest before money moves. One IMEI per row, with model and grade. A seller who will not produce a manifest before payment is a seller to walk away from.
- Validate format and Luhn first. Run the CSV through the free bulk IMEI check. Typos, duplicates, and fabricated IMEIs surface here at zero cost.
- Run the GSMA-layer check on the full manifest. Through an authorised service, since the registry has no public direct query. Any lost, stolen, or finance flag prices those units at parts tier or removes them.
- Run device history on the survivors. A CheckMend report per unit, or at minimum on a meaningful random sample of a large used lot. Read the per-check detail: an insurance-claim red is a walk-away, an old registered-owner amber may just need a provenance question.
- Physically sample against the manifest. Dial *#06# on random units and compare to the paperwork. A clean pair of database results is worthless if the physical IMEIs do not match the manifest you checked.
- Anchor the deal terms to the check date. Both databases are snapshots. Write "clean per [service] as of [date]" into the terms, keep the result exports, and keep the window between check and payment short.
Counterparty screening matters as much as device screening: a manifest that fails these checks is one of the classic warning signs covered in wholesale electronics fraud and scam patterns. On discovery platforms such as Aikon, where companies find counterparties and then deal directly with each other, this verification workflow is the buyer's own responsibility, so build it into your process rather than treating it as optional.