Where I would start: BlueDriver for an occasional buyer who wants guided reports; TOPDON TopScan for deeper supported module scans; ANCEL AD310 as the inexpensive minimum.
What to inspect
Confirmed, pending and permanent codes
Confirmed codes have met the vehicle’s criteria. Pending codes may be early warnings. Permanent codes cannot simply be erased by a scanner and remain until the vehicle confirms the issue is resolved.
Readiness monitors
Multiple “not ready” emissions monitors can occur after a battery disconnect or code clear. That is not proof of fraud, but it is a reason to ask when and why the computer was reset.
Freeze-frame data
Freeze frame captures operating conditions when a fault set. Speed, load, temperature and fuel-trim values can make a code more meaningful.
Full-system modules
An engine-only reader cannot inspect most ABS, airbag, transmission and body modules. A supported all-system scan can reveal a broader electronic history.
A safe inspection sequence
- Scan before the test drive and save the report.
- Check readiness monitors before clearing or changing anything.
- Drive long enough for the vehicle to reach operating temperature.
- Scan again and compare new or pending faults.
- Use findings to inform—not replace—a professional pre-purchase inspection.
What a scanner cannot tell you
It cannot reliably identify structural collision repairs, oil consumption, hidden rust, tire age, mechanical wear or every intermittent fault. It also cannot prove that a seller acted dishonestly. Treat it as one instrument in the inspection.
Etiquette and safety: obtain the owner’s permission, never erase codes on a vehicle you do not own, and do not perform active tests during a casual inspection.
FAQ
Are not-ready monitors always suspicious?
No. A recent battery replacement, repair or legitimate reset can cause them. Ask for context and allow sufficient drive-cycle time.
Is a $40 scanner enough?
It is enough for engine and readiness clues. An all-system scanner provides a broader picture.