Bulk IMEI Checker
For when it is not one phone. Paste a list, get a table of blacklist and lock verdicts, download the CSV — free, no account.
What the bulk checker does before it checks anything
Three things happen locally before a single request leaves your browser. The list is parsed for anything that looks like an IMEI, so a column pasted out of a spreadsheet with headers and notes in it works fine. Duplicates are collapsed, because a list of trade-ins almost always contains the same handset twice. And every number is run through its check digit, so the ones that cannot possibly be valid are flagged immediately rather than wasting a lookup.
What is left is queued and checked one at a time, with a pause between each. The pause is the part that matters: the databases behind these lookups throttle bursts, and a tool that fires twenty requests at once gets most of them rejected. Paced, the same twenty finish reliably in about a minute.
Who this is for
Repair shops and trade-in desks assessing a batch before quoting. Resellers who have bought a lot and need to know which units are worth listing. Anyone who has been handed a spreadsheet of handsets by a departing employee. In each case the question is the same as for a single phone — is it blocked, is it locked, is it the model it claims to be — just repeated, and with the answers in a form you can file.
The results table shows each IMEI with its device, blacklist verdict and lock verdict, and the CSV export carries the same columns plus a plain-language status so a colleague can read it without knowing what a blacklist is. Every check also lands in your local history, so nothing is lost if you close the tab.
A note on what a clean batch does and does not prove
A clean result is a statement about right now. Handsets that were financed can be reported months later when the original account defaults, so a pallet that checks clean today can still develop blocks — this is the single most common way volume buyers get hurt. Where you can, establish that devices are paid off as well as unflagged, and keep the CSV: a dated record of the status at the time of purchase is exactly what a dispute needs.
Questions about this tool
How many IMEIs can I check at once?
Twenty per batch. The tool de-duplicates the list, drops anything that cannot be a valid IMEI, then runs the rest one at a time with a few seconds between them. That pacing is deliberate: the lookup databases rate-limit bursts, and a queue that respects them finishes faster than one that gets throttled halfway through.
Is the bulk checker free?
Yes, like everything else here. There is no account, no card and no per-lookup charge. The only limit is the pacing, which exists to keep the upstream databases answering rather than to sell you a faster tier.
What format should my list be in?
Whatever you have. Paste one IMEI per line, or a comma-separated row, or a column copied straight out of a spreadsheet — the parser pulls every 14-to-16 digit run it can find and ignores the rest, so labels and serial numbers mixed into the list do no harm.
Can I export the results?
Yes. When the run finishes, the download button produces a CSV with one row per IMEI: the number, the device the databases identified, the blacklist verdict, the lock verdict and a plain-language status. It opens directly in any spreadsheet.
What happens if one IMEI fails?
The queue carries on. A number that errors or times out is marked as such in the table and the run continues to the next one, so a single bad entry never costs you the whole batch. You can re-run just the failures afterwards by pasting them back in.
Does the bulk checker store my list?
The list itself is never uploaded anywhere as a list — each IMEI is checked individually through the same endpoint the single checker uses, and the table lives in your browser until you leave the page. Results are also added to your local check history so you can find them again.