Supported document type
Detect tampered and deepfake Vehicle Registration
A vehicle registration document is checked more often than it is read closely, which is what makes it worth forging. The usual edit is a single field: a VIN that does not belong to the car on the driveway, or a keeper name changed so a vehicle can be financed, insured, or sold by someone who has no right to it. Everything else on the document is genuine, so it survives a glance. TamperCheck reads it forensically and names the field that moved.
API slug: vehicle_registration
Last updated:
What a genuine vehicle registration document contains
A registration document is the state's record of a specific vehicle and the person responsible for it. It carries the VIN or chassis number, the registration plate, the registered keeper's name and address, and the vehicle's own description: make, model, engine capacity, colour, and the date it was first registered. Issue and expiry dates sit alongside the issuing authority's stamp, and most jurisdictions add a hologram or security overlay to the substrate itself.
The VIN is the field that anchors everything else. It appears on the document, stamped into the chassis, and on the manufacturer's plate, and it encodes the make, model year, and plant of manufacture in its own structure. A VIN that fails its own check digit, or that decodes to a different vehicle than the one described three lines below it, is a contradiction the document cannot explain away.
How vehicle registration document forgeries are made
VIN substitution
The VIN is changed so a registration document describes a different vehicle, usually to give a stolen or written-off car a clean documentary history. The replacement often fails its own check digit, or decodes to a make and model year that contradict the vehicle description printed on the same page.
Keeper name and address edits
The registered keeper is overwritten so a seller appears to own a vehicle they do not, or so a finance application matches the applicant's name. This is the edit behind most private-sale fraud, and it changes only a few characters on an otherwise authentic document.
Vehicle description mismatch
Make, model, colour, or engine capacity are adjusted to match the car actually being sold, without the VIN being touched. The result is a document whose two halves describe different vehicles.
Date extension
Issue and expiry dates are moved to make a lapsed registration read as current. Cheap to attempt, and frequently missed by reviewers who check that a date is present rather than that it is consistent with the issue date and the document's own file metadata.
Hologram and security overlay reproduction
A genuine security overlay shifts in hue across the card as it catches light. Photographed or reprinted, it flattens into a static pattern that no longer varies the way the real thing does.
Fully synthetic registrations
Generated end to end from a template rather than edited from a real document. Every field is internally consistent, so cross-checks pass, and these are caught by generation signatures and substrate analysis instead.
What TamperCheck checks on a vehicle registration document
TamperCheck runs 200+ forensic checks across three layers and returns a risk score from 0 to 100 with plain-English findings tied to specific regions of the document. These three carry the most weight on this document class.
Security print, foil, and hologram analysis
A genuine security overlay or guilloche background behaves differently from a printed picture of one. A reproduction loses the structure that made the feature a security feature in the first place, and that loss is measurable even when the copy looks convincing on screen.
Embossed seal analysis
A physically embossed seal deforms the paper it sits on. A seal that was scanned and reprinted is flat, and the two separate cleanly under analysis even when they are hard to tell apart by eye.
Stamp authenticity and placement
Stamps are assessed for whether the ink was impressed onto the page or printed as part of it, and for whether the impression was placed digitally after the fact.
And many more checks
The three above are the layers that carry the most weight on a vehicle registration document. Every upload runs the full suite of 200+ checks regardless of document class, spanning file structure and metadata, pixel-level forensics, font and text rendering, optical and print characteristics, provenance signals, AI-generation signatures, and many more checks.
Who verifies a vehicle registration document, and why
Motor finance lenders, insurers, and used-vehicle buyers. In each case the document is being used to unlock money, access, or a legal status, which is exactly what makes it worth forging.
How to verify a vehicle registration document in 4 steps
Check the fields against each other
Read VIN and registration number, registered keeper, and vehicle details together rather than one at a time. Forgers typically change one value and leave the rest of the document describing the original.
Inspect the file metadata
Open the document properties and look at the producer, creation date, and modification date. A document produced by a consumer PDF editor, or created long after the date printed on its face, is worth a closer look.
Ask for a second document
Request a corroborating document from the same issuer or an adjacent period. Forgery effort concentrates on one file, so inconsistencies surface as soon as there are two to compare.
Run a forensic check
Manual review catches obvious edits but not field-level pixel manipulation or synthetic generation. TamperCheck runs 200+ forensic checks on a vehicle registration document and returns a risk score from 0 to 100 within seconds, at $0.50 per document.
Frequently asked questions
How do I verify a vehicle registration document?
Decode the VIN and confirm it matches the make, model year, and engine details printed on the same document, then check it against the VIN stamped on the vehicle itself. Confirm the keeper name matches the person selling or financing the car, and that issue and expiry dates are consistent with one another. A forensic check then covers the security overlay and the file behind the scan.
How can you tell if a V5C is fake?
The reliable signals are internal contradictions rather than appearance: a VIN that fails its check digit, a vehicle description that does not match what the VIN decodes to, or a security overlay that photographs as a flat pattern. TamperCheck also compares every printed field for font and alignment consistency, which exposes fields that were added after the fact.
What software detects vehicle registration fraud?
TamperCheck analyses registration documents through a single REST endpoint. Upload a PDF, scan, or phone photo and receive a JSON verdict with a risk score from 0 to 100 and findings tied to specific regions of the document. Pricing is $0.50 per document, with no subscription or minimum.
Can an AI-generated vehicle registration be detected?
Yes. A generated registration is internally consistent, so field cross-checks pass on it. It is caught instead by generation signatures and by substrate analysis: the noise and compression characteristics of generated imagery differ measurably from a real document photographed or scanned, and a printed security overlay does not behave like an applied one.
TamperCheck analyses vehicle registration uploads with a hybrid forensic and AI pipeline tuned for this document class. Upload endpoints accept PDF and common image formats; class is inferred automatically. See the API & MCP documentation for authentication, async jobs, and webhooks.