Short answer

Use the brand, marketed name, model code, battery identifier, and charger name. A notice may concern an accessory or component.

Search more than the retail name

Use the brand, marketed name, model code, battery identifier, and charger name. A notice may concern an accessory or component.

Check the right jurisdiction

Search regulators where the product was sold. U.S. and EU databases cover different markets and are not worldwide clearance.

Interpret no match correctly

No match as of a stated date means only that the performed search found none. Follow any later official warning.

Prepare more than one search term

Write down the brand, marketed name, exact model code, regional suffix, battery identifier and bundled charger name. Recall notices sometimes name a component, accessory or manufacturing batch instead of the retail phone family. Keep serial and IMEI private unless an official manufacturer checker explicitly requires them in a secure first-party form. Search spelling variants and older brand names, then open the notice rather than relying on a search-result snippet. Compare affected identifiers, sale dates, images and remedy details with the actual unit. A keyword resemblance is a candidate, not a confirmed match.

Use the jurisdiction where the product was sold

CPSC covers the United States, Safety Gate covers European Union alerts, UK OPSS publishes United Kingdom product safety reports and Health Canada covers Canada. A phone imported from another market may appear only in that market’s regulator or manufacturer channel. Search each relevant official source independently and record the date. DevLifeCheck’s standard empty result wording is intentionally narrow: no matching notices in the monitored jurisdictions on the stated date, not a worldwide safety clearance. Regulators can publish later, and a notice can be difficult to find under a distributor or accessory name.

Confirm, quarantine or reject a candidate

A confirmed match needs the official notice ID, exact affected identifiers, jurisdiction, hazard, remedy and reviewer rationale. If the name matches but the model or batch is unclear, mark it for review instead of publishing a positive recall. If the official notice names a different product, record why the candidate was rejected so it is not repeatedly rediscovered. Never infer that every device in a family is affected. Pixel 6, Galaxy S21 and iPhone variants can have multiple regional codes; the physical model must intersect the notice scope before the public record can show a confirmed match.

Follow the remedy, not a generic repair tip

The regulator or manufacturer may direct owners to stop use, stop charging, return an accessory, install an update, obtain a replacement or contact a specific service program. Do not improvise a battery repair or continue shipping a damaged lithium-ion product when the notice says otherwise. Preserve the receipt and photograph public identifiers if needed. If there is smoke, fire or immediate danger, move away and contact local emergency services. A recall remedy can change over time, so revisit the official URL rather than copying old instructions into a static checklist.

Document a no-match result honestly

List the databases, queries, exact model and date checked. Say: ‘No matching notices in CPSC, EU Safety Gate, UK OPSS, or Health Canada on [date]. That is not a worldwide safety clearance.’ Do not write ‘no recalls exist’ or ‘fully safe.’ Explain any feed limitation, unavailable regional source or identity ambiguity. A material new notice belongs in revision history with a human-readable summary. Routine rechecking without a changed result can update an internal job timestamp, but it should not create a misleading public freshness event or replace the original evidence capture.

Limits of automated recall feeds

Official feeds can lag web notices, omit older archives, change identifiers or publish free text that does not match a retail name. Automated ingestion should therefore create candidates, not silently declare product matches. Exact-identity checks, jurisdiction locks and reviewer rationale remain necessary. If a feed is unavailable, disclose the missing source rather than presenting a four-jurisdiction result. A later notice should update the device record and changelog without rewriting the historical checked date. Readers facing an immediate symptom such as smoke, swelling or overheating should follow emergency and manufacturer guidance even when the database search returns no candidate.

Worked examples from the catalog

Use the model identifier and jurisdiction together; a marketed name alone is not enough. These records show how the method is applied to real evidence.

How this guide was produced

DevLifeCheck separates manufacturer commitments, regulator notices and editorial interpretation. The editor checks the linked primary sources, records the applicable model and region, and avoids turning a missing date into an estimate.

Primary sources

01
Consumer product recalls

U.S. Consumer Product Safety Commission · checked Sep 2026

Open ↗
02
Safety Gate alerts

European Commission · checked Sep 2026

Open ↗

Related guidance

Important

Device support and safety information can change. Recheck the linked manufacturer and regulator evidence before making a purchase or safety decision.