Can you tell if a used car's check-engine codes were cleared?

The scan can show a reset pattern—not who caused it

Readiness monitors record whether supported emissions self-tests have completed since diagnostic memory was reset. If several supported monitors are incomplete while the dashboard light is off and no stored emissions codes are returned, the vehicle has not yet supplied a fully tested clean result.

That pattern is consistent with several explanations: someone cleared codes, the battery was disconnected or replaced, controller power was lost, a module was replaced, recent service reset memory, or the vehicle simply has not met the conditions needed to complete its monitors. The pattern does not identify which explanation is true.

Describe the evidence neutrally. Say that the self-tests are incomplete or that memory appears to have been reset. Do not accuse a seller, dealer, or repairer without independent proof of who acted, when, and why.

• Observed fact: the exact code channels, MIL command, and readiness states returned now.
• Plausible paths: code clearing, battery or controller power loss, service work, or unmet monitor conditions.
• Still unknown: who reset memory, why it changed, and whether a fault will return.
• Next proving test: preserve this scan, obtain service context, and compare later evidence after safe normal operation and an independent inspection.

Record the whole standardized OBD snapshot

With permission, scan before anyone clears codes or disconnects the battery. Record commanded check-engine-light status, stored and pending emissions codes, permanent codes when the vehicle supports them, every supported readiness monitor and its state, available freeze-frame data, communication result, protocol, reported VIN when available, date, and displayed mileage.

Keep supported, incomplete, unsupported, and not checked separate. An unsupported monitor is not an incomplete test. A module that the adapter never accessed is not clear. A generic OBD scan mainly covers the standardized emissions path; it does not establish that ABS, airbag/SRS, stability control, body, hybrid, or every manufacturer controller was checked.

Save the first result even when it looks quiet. A timestamped baseline lets the buyer compare what changes after a permitted cold start, road test, inspection, or later scan without rewriting the original evidence.

Permanent codes can help, but absence proves little

On vehicles that support permanent emissions DTCs, those records are designed not to disappear merely because a scan tool cleared ordinary codes or the battery was disconnected. The onboard system clears a permanent code only after it verifies the relevant fault is no longer present under its own criteria.

A permanent code can therefore preserve useful context after an ordinary clear. Its absence does not prove memory was never cleared: support varies, not every event creates a permanent code, and a vehicle may already have completed the verification needed to remove one.

Missing freeze-frame data is also not proof of tampering. Availability and code association vary. Report what the vehicle actually returned rather than treating an empty field as evidence of intent.

Use the road test to gather evidence, not force a drive cycle

There is no universal number of miles, starts, or minutes that makes every monitor complete. Enabling conditions vary by vehicle and monitor and may involve temperature, fuel level, load, speed, soak time, or a fault that prevents completion.

If the owner permits a normal road test and the vehicle is safe to operate, compare the saved pre-drive and post-drive results. A pending code, returning warning, monitor result, abnormal temperature, rough operation, charging problem, or communication change may be more informative than the first quiet screen.

Do not attempt an improvised drive cycle that conflicts with traffic law, weather, warning-light guidance, or the vehicle's condition. Use exact manufacturer information or a qualified professional when a specific completion procedure is necessary.

Pause the purchase when the evidence cannot be completed

A scan is one part of a pre-purchase decision. Pair it with an independent mechanical and structural inspection, a cold start when practical, service and title records, open-recall research, tire and brake measurements, leak and underbody checks, and application-qualified hybrid or EV testing when relevant.

If the seller will not allow an independent inspection, refuses a reasonable repeat scan, cannot explain a recent battery or repair event, or pressures you to decide while supported monitors remain broadly incomplete, treat the uncertainty as unresolved risk. That is a reason to pause—not proof of fraud.

Urgent warning lights, severe rough running, overheating, oil-pressure warnings, fuel odor, smoke, braking or steering changes, or unsafe vehicle behavior require the owner's manual and qualified help. Do not continue a road test merely to complete diagnostic evidence.