The NHTSA VIN decoder: what it returns, and where it stops

Two things share the name. There is a web page where you type a VIN and read a table, and there is an open interface that returns the same information as structured data. They are fed by the same records: what manufacturers file with the agency about the vehicles they build for this market.

Neither needs an account, a card or a key. That is unusual enough to be worth stating plainly, because a great deal of the paid VIN industry is built on top of it. When a free decoder tells you the make, model, engine and plant of a car, it is very often reading this and re-presenting it — which is fine, and worth knowing when you are deciding what a service is actually charging you for.

Two numbers describe the tool better than a paragraph does, and both are queryable.

The first explains why a decode looks sparse. The response has a slot for restraint types, plant details, engine configuration, weight ratings and dozens more — but a slot is only filled if the manufacturer filed that detail for that vehicle. Blank fields are usually unfiled data rather than absent equipment, and reading them as absent equipment is the most common way people misuse the result.

The second is the argument against every printed decoder chart in existence. 12,340 makes is not a list anybody memorizes or reprints; the charts that circulate cover perhaps a few dozen mainstream marques and fail silently on the rest, returning something plausible rather than nothing.

Here is the part that is genuinely hard to find. Every decode comes back with a result code, and the agency publishes the complete catalog of them. Most consumer decoders show you the decoded fields and quietly discard the code — which throws away the only field that tells you how much to trust the rest.

Read them as three groups rather than fifteen items. Code 0is the clean result. Codes 1 through 5 are about the number having something wrong with it that the decoder can sometimes work around. Codes 7, 9 and 10 are not about the number at all — they are about the vehicle, and they are the ones worth stopping on.

Most result codes describe a problem with what you typed. Three describe a problem with what you are looking at, and on a page about buying a car those are the important ones.

None of the three means the vehicle is stolen or fraudulent. All three mean the thing in front of you is not the ordinary US-market motor vehicle a buyer usually assumes, and the difference has consequences for titling, registration and insurance that are worth resolving before money moves rather than after.

Code 7 in particular has an innocent explanation most of the time. It appears on vehicles that predate the modern standard, and on vehicles built for other markets. Our pages on classic trucks and imported cars cover those two cases in detail.

Codes 9 and 10 are worth quoting in full, because both cite the statute and both say something more precise than a summary would.

A glider is a vehicle assembled from a new body and chassis around a used powertrain. The agency’s position, stated in the error text itself, is that such a thing is not a motor vehicle under 49 U.S.C. § 30102(a)(6) and cannot carry a VIN meeting 49 CFR Part 565. If you are being sold something described as a new truck and the decoder returns this, the two statements are not compatible.

This is the one that catches buyers of side-by-sides, utility vehicles and similar machines. The number on the machine looks like a VIN and is not one, because the manufacturer did not certify the product to the Federal Motor Vehicle Safety Standards. It is not a defect — the machine was never meant for the road — but it decides whether the thing can be registered, and our ATV VIN lookup covers what applies instead.

The middle band of codes all concern the ninth character, which is not part of the vehicle’s description at all. It is a check digit — a value computed from the other sixteen characters so that a single mistyped or transposed character produces a number that fails arithmetic.

The practical value is in code 1. A VIN copied off a listing, a text message or a photograph is the most common source of a failed check digit, and the fix is almost always to read the number off the vehicle again rather than to distrust the vehicle. Where a number read carefully off the car itself still fails, that is a different and more serious conversation — see VIN cloning.

The mechanics of the calculation, and the reason three letters never appear anywhere in a VIN, are on how to read a VIN.

The catalog is easier to read against real results. Below are three numbers put through the live interface, chosen because each returns a different code.

Notice how much survives a partial number. Eight characters and a wildcard still returned the make, the model, the manufacturing company and the vehicle type — enough to confirm you are looking at the vehicle an advertisement claims, though not enough for the model year, which lives in position ten.

The third row is the one worth internalizing. Four populated fields out of 154 is not a broken tool. It is the decoder reporting that this number predates the system it searches, which is exactly what codes 6 and 7 say together.

People searching for the federal decoder usually want one VIN decoded. The interface behind it answers a wider set of questions, and several of them are more useful than a single decode when you are checking a listing rather than a car.

The middle two are the ones that settle arguments. Asking which models a make filed in a given model year is how you test whether a nameplate existed when a listing says it did — the check behind our Lincoln and Pontiac pages. Asking which identifiers a manufacturer filed is how you find out that some marques file none at all, because they are divisions rather than companies.

This is the limit that matters most, and it is structural rather than a gap somebody intends to fill. The agency’s vehicle data describes what manufacturers built. It does not describe what happened to any particular car afterward.

• Any accident or damage history
• Any title brand — salvage, flood, rebuilt or lemon
• Any odometer record
• Any theft or recovery record
• Who owns the vehicle, or who has owned it
• What the vehicle is worth

Those records exist, but they are fed by states, insurers, salvage yards and auction houses rather than by manufacturers, and they live in different systems with different access rules. A clean decode with result code 0says the number is consistent and recognized. It says nothing whatever about the car’s past.

The decoder rewards a little discipline, mostly around where the number comes from.

1. 1Take the VIN off the vehicle, not the advertisementWindshield base and door-opening label, compared character by character. Most failed check digits are transcription errors from a listing.
2. 2Read the result code before the fieldsCode 0 means the rest is trustworthy. Anything else changes how much weight the decoded fields carry.
3. 3Treat blank fields as unfiled, not absentA missing transmission or horsepower value usually means the manufacturer did not file it, not that the car lacks the feature.
4. 4Check the recalls in the same sittingCampaigns are matched to the VIN, the remedy is free, and it is the highest-value thing you get for nothing.
5. 5Then go and buy the historyThe build record cannot answer the questions in the list above. That is a separate search and the one worth paying for.