Methodology

Where the data comes from, and what it can and cannot see.

Everything on this site comes from one source: the recall database of the National Highway Traffic Safety Administration (NHTSA), the federal record of vehicle safety recalls. We do not buy data, scrape dealer sites, or mix in third-party recall lists.

How the data updates

Every night, we ingest NHTSA’s latest recall data: new campaigns, remedy updates, owner-notice mailings, expansions, and supersessions (where a newer notice replaces an older one). Each change is recorded with a date, so every recall page shows not just the current record but what has changed on it since it was published.

What “complete data” means

A campaign gets a record page here only when it has everything needed for a useful page: a defect description, a consequence, a corrective action, a report date, and at least one affected vehicle. Campaigns missing any of that are held back — deliberately. A page with gaps in it would be worse than no page: it could look like a clean bill of health when it is really just missing data.

Every page also carries the record’s dates: when it was reported to NHTSA, when we first tracked it, and when it last changed.

How the VIN check works

When you check a VIN, two things happen. First, the VIN is decoded (year, make, model) and run through NHTSA’s VIN-specific recall lookup. Second, the result is matched against our local copy of the NHTSA database, which adds the plain-English summary and the change timeline.

There are two kinds of result, and the page tells you which one you got:

VIN-specific. NHTSA’s VIN lookup returned a result, so the matches are filtered to recalls that apply to your specific VIN.
Model-level. NHTSA’s VIN lookup returned nothing, so the check fell back to matching your vehicle’s year, make, and model. That means “vehicles like yours are covered by these recalls” — confirm with your dealer whether your specific VIN is included.

Why the fallback exists

NHTSA’s VIN lookup has coverage gaps. We verified this directly: it returned no recalls for a test VIN that had 13 model-level recalls in the database. An empty VIN lookup does not mean a clean vehicle — it can mean the lookup has no record for that VIN yet. That is why the check never treats an empty VIN lookup as “no recalls” and silently drops the model-level matches. When the VIN lookup is empty, you get the model-level result, labeled as such.

What the site cannot see

Service campaigns and warranty fixes. Only federal safety recalls are in the NHTSA database. A dealer service campaign or a warranty extension will not show up.
Very recent recalls. A recall announced in the last day or so may not have VINs assigned yet, so the VIN lookup may miss it.
Manufacturer reporting gaps. Not every manufacturer reports the same way, and older recalls are not always in the lookup.
Whether a recall was already repaired. The check shows open recalls for the vehicle type. Whether your specific vehicle was already fixed is between you, your dealer, and the manufacturer’s records.

“No open recalls found” means no open federal recalls were found right now — not that the vehicle never had one, and not a guarantee.

Plain-English summaries

The short version, What / Why it matters / What to do, and the remedy line on each record page are our plain-English rendering of NHTSA’s record. The facts come from NHTSA; the wording is ours, written to be readable. Every page links to the official NHTSA record so you can check the original.

Corrections

If a record looks wrong, email [email protected] with the campaign number and what looks off. Corrections are checked against NHTSA’s record. We never edit NHTSA’s facts — but we do fix our own plain-English summaries and display bugs, and we say so on the page when a correction changes what it says.