Vehicle recall records
Recall campaigns reported 2010-01-01 through 2026-06-19. Fonteum groups public rows by make, model, campaign, component, and year.
Source:NHTSA Safety RecallsSnapshot 2026-06-24PUBLIC RECALL RECORDS
Search loaded NHTSA vehicle recall rows and CPSC product recall rows. Results are public-record matches by name, not a private owner or VIN report.
Is my car under recall?
Fonteum can show whether loaded NHTSA public recall records list a make or model. That is not a VIN-specific status. If a record matches, use NHTSA's official VIN tool for a vehicle-level check, and review the listed campaign, component, report date, and remedy text.
Try a vehicle make/model such as Ford F-150, or a product brand such as Polaris. Product-brand matches rely on CPSC manufacturer/brand fields, which are partial.
Recall campaigns reported 2010-01-01 through 2026-06-19. Fonteum groups public rows by make, model, campaign, component, and year.
Source:NHTSA Safety RecallsSnapshot 2026-06-24Recalls dated 1973-06-08 through 2026-06-18. Manufacturer/brand names are partial and cover the named-firm subset.
Source:CPSC Consumer Product Safety RecallsSnapshot 2026-06-24A make or model match means loaded NHTSA public recall records list that vehicle name. It does not say a specific VIN is affected. Use NHTSA's official VIN tool for a vehicle-level check after reviewing the campaign, component, report date, and remedy text.
The lookup searches loaded NHTSA vehicle safety recall rows and loaded CPSC product recall rows. NHTSA rows are grouped by make, model, model year, component, and campaign. CPSC rows are product recall records, with brand pages based on the manufacturer/brand field.
CPSC's manufacturer/brand field is populated on 5,419 of 9,862 rows (54.9%). Product-brand searches can also match title, product, and description text, but brand pages use the named-firm subset only.
What’s on file, by the numbers
Platform snapshot · 2026-08-12
Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.
Source authority is record-specific
Use the issuer named on the record.
Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.
Reproducible by design
Inspect the evidence each published figure actually supplies.
Source and date
Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.
Available derivation
Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.
Daily observations
Dated table row-count observations can detect local drift. They do not imply that an upstream publisher released or Fonteum ingested new data that day.
Named medical review
Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.