Can Police Tell If You Have Car Insurance?

What Happens in the Ten Seconds After an Officer Types Your Plate

The critical thing to understand is that in the modern design, the state is not looking your policy up in a state-owned list of insured cars. Alabama’s guide says it plainly: participating insurers do not interface with a state database at all, and the state system “will serve only as a conduit for the query from and the response back to the end-user.”^[1] The question is forwarded to your insurance company and your insurance company answers it.

In Alabama, that routing happens in four steps. The plate the officer types is matched against the state’s registration record, which yields the vehicle identification number — the serial number individual policies are actually written against, 17 characters on any modern vehicle, though Alabama’s guide accepts a non-conforming VIN of another length on an older car so long as it is the authentic one the manufacturer issued under the regulations in place at the time of manufacture. The state then assembles a small request carrying that VIN, the date coverage is being checked for, the policy number if one is on file, and the NAIC company code — the identifier the National Association of Insurance Commissioners assigns to each carrier, which the verification network uses as the routing key that decides whose server receives the message.^{[1] [2]} That four-field workflow is Alabama’s published implementation of the IICMVA model. It is not a description of all 19 verification states: the Kansas Legislative Research Department found state laws vary widely in how much they specify, and while most reference online verification, several reference state-operated databases rather than a live query routed to the carrier.^[4]

The message itself is a Simple Object Access Protocol envelope carrying an XML payload — a structured text format that lets a state dispatch server and an insurer’s cloud application parse the same message without sharing any software. Each participating carrier publishes a Web Services Description Language file, which is the machine-readable contract stating exactly what fields a request must contain and what the reply will look like. The insurance industry’s committee on motor vehicle administration maintains the shared schema versions those files are built against.^{[2] [10]} Kentucky’s reporting guide and South Carolina’s online liability verification guide document the same message structure for their own carriers, which is what makes a national patchwork of state systems interoperable at all.^{[8] [9]}

Transport security is mutual. Under the model guide, carriers use Secure Sockets Layer for mutual authentication, with both sides holding an X.509 public and private key certificate pair, so the insurer proves its identity to the requesting agency and the agency proves its identity to the insurer before any policy data moves.^[2] A forged confirmation cannot be injected into the conversation by an outside party, because an outside party cannot complete the handshake.

Then the clock matters. The industry model guide reports a median response time of roughly five seconds based on historical data from operating states, and Alabama suggests 10 seconds as the outer bound for a usable answer during a stop.^{[2] [1]} Alaska sets a harder service level for its own program: carriers must answer on a 24/7/365 basis with monthly availability of at least 99 percent, and are told to design their services to respond within two seconds of receiving an inquiry.^[7]

The request also carries a transaction type, which is what distinguishes this architecture from a bulk state list. Alabama’s schema includes distinct codes for an accident, a traffic violation, a traffic violation with an accident, a registration renewal, a vehicle registration, and a bodily injury coverage verification.^[1]

Those codes cover the events, but the querying does not stop at events. Alabama states that its revenue department will use the system to periodically verify evidence of insurance on all vehicles subject to verification, including registrations that came back both “confirmed” and “unconfirmed” during registration, traffic stops, or crashes, and that it re-checks every unconfirmed response within 90 days of the original response.^[1] The Kansas Legislative Research Department found eight states — Alabama, Connecticut, Idaho, Illinois, Montana, South Carolina, Tennessee, and Utah — whose statutes authorize verification untied to any event: Alabama and Illinois authorize random verification, Montana requires its rules to provide for random checks, Connecticut authorizes requiring proof at any time and at least monthly, and Illinois requires semi-annual verification.^[4] What the state does not do under this model is keep a copy of your policy between queries.

Why the Paper Card and the State Database Both Failed

Start with what the old system did correctly. A printed insurance card carries the carrier name, the policy number, the VIN, and an expiration date, so an officer reading one learns who wrote the policy and which car it covers. That is genuinely useful information, and it is why states still require the card and still accept it.

What the card cannot carry is the present tense. The document is printed once, at issuance, and then it stops updating. A driver can buy a policy, print the card, register the vehicle, and cancel the coverage the following week, and the card in the glove box will keep asserting coverage until its printed expiration date arrives. The officer holding it has no way to distinguish a live policy from a cancelled one.

The first fix was to move the list. Under the older reporting model, insurers compiled their whole book of business — every active policy — into large files and transmitted them to the state on a schedule, and the state tried to match those files against its registration records. The industry committee that developed the replacement standard argued directly against that design: it forces the transfer and storage of enormous volumes of data that is mostly never referenced, and it should give way to event-based online inquiry instead.^{[3] [2]} The association of state motor vehicle administrators reached the same conclusion in its own study of web-services verification and now maintains insurance verification as a standing program topic for its member agencies.^{[6] [5]}

Batch matching also breaks in a specific and consequential way. The match key is the 17-character VIN, and a single transposed character in an agent’s data entry produces no match at all. The state’s file then contains a registered vehicle with no corresponding policy record, which looks exactly like an uninsured car, and the insured owner receives a compliance notice for a typographical error. Latency compounds it: a policy cancelled on Monday can still appear active in a file transmitted the previous Friday.

Event-based verification removes both failure modes at once by never holding the data. Because the question is asked at the moment it is needed and answered by the company that owns the record, no stale copy sits at the state waiting to be wrong. The model guide is precise about what that buys: online status refers to the information readily available on an insurance carrier’s internal databases at a given point in time, and a carrier can only respond once a policy’s effective date has arrived.^[2] The answer is as current as the carrier’s own file, which is not the same thing as the premium you paid an hour ago. That is the architectural reason the industry moved, and it is why the distinction between a registration record and a coverage record matters so much — a point we take up separately in our research on whether vehicle registration is the same as insurance.

“Unconfirmed” Is Not a Synonym for “Uninsured”

The system returns one of two results: confirmed or unconfirmed.^[1] Confirmed is unambiguous. The carrier found an active personal auto liability policy covering that VIN on the date asked about, and the insurance question is closed.

Unconfirmed means only that the carrier did not return a confirmation. Alabama says so in its own guide: “the term ‘unconfirmed’ does not necessarily mean that there is no insurance available on a policy,” and an unconfirmed response “advises the end-user to rely on the facts presented on the evidence of insurance or other means of proof of insurance.”^[1] The state is instructing the officer to treat the screen as inconclusive and look at the driver’s documents.

Arkansas goes further and puts the disclaimer inside the response text the officer reads. The Eighth Circuit’s 2026 opinion in United States v. Mitchell quotes it verbatim: the system “WAS UNABLE TO VERIFY INSURANCE FOR THIS VEHICLE. VALID INSURANCE POLICIES MAY EXIST THAT ARE NOT AVAILABLE TO THE SYSTEM AT THIS TIME. PLEASE RELY ON INSURANCE INFORMATION PROVIDED BY DRIVER.”^[12]

The reason codes are what turn that ambiguity into something diagnosable. Response codes are optional in the schema, but Alabama strongly encourages carriers to return one so the reason can be communicated to the vehicle owner, and notes that when an unconfirmed response arrives without a code, officials will simply tell the owner to contact their insurer.^[1]

Read the column on the right and the asymmetry is stark. Of twelve published codes, exactly one — code 8, “System Found Unique Key — No Coverage on Date Requested” — reports that the carrier looked and found no coverage. Six describe a malformed or unauthorized request. One says the insurer’s service was simply down. The rest describe a record that could not be matched. An officer who treats “unconfirmed” as equivalent to “uninsured” is collapsing eleven very different conditions into one accusation.

There is also a deliberate mechanism for the mismatch case. Under VIN broadcasting — also called an unknown carrier request — if the VIN in the request matches an insured vehicle but the policy number does not match, the carrier should still indicate that the vehicle is covered, either by returning confirmed or by returning unconfirmed with the specific code meaning the VIN was found but the policy key could not be verified.^[7] That is the system trying to avoid punishing a driver for a clerical mismatch.

The Vehicles These Systems Are Written to Exclude

Online verification is keyed to the VIN, and that single design decision determines everything it cannot do. A personal auto policy is written against specific listed vehicles, so the VIN is a reliable lookup key. A commercial policy is written against a business entity, and the vehicles move in and out of the fleet underneath it.

Alabama states the consequence directly: the system applies only to vehicles covered by personal automobile liability policies, so insurance cannot be verified through it in every situation. Vehicles outside its reach include those covered by fleet, non-owner, and garage policies — a category that expressly takes in rental vehicles and semi-trucks — along with vehicles operating under a certificate of self-insurance. In those cases the unconfirmed response is returned with the appropriate code, and the user is expected to verify the physical evidence of insurance instead.^[1]

The exclusion is not Alabama’s alone, and the Kansas Legislative Research Department put numbers on it: most of the verification states exclude commercial vehicles from these systems. Arkansas, Idaho, Illinois, Kansas, Mississippi, Missouri, Nevada, Oklahoma, Tennessee, Utah, and West Virginia provide that their verification provisions do not apply to commercial vehicles. Illinois, Kansas, Kentucky, Missouri, Tennessee, and West Virginia let insurers of commercial vehicles report coverage voluntarily, so a commercial vehicle in those states may be visible to the system if its carrier opted in. Utah directs commercial insurers to send those records separately, and Alabama and Montana instead authorize a specific insurance card for a commercial vehicle.^[4]

The card itself is built to signal this. Where a card is issued for a commercial policy, it may state “FLEET,” “Commercial,” “Commercial Policy,” or “Commercial Exempt” in place of the vehicle year, make, and VIN; a non-owner policy card may state “NONOWNER POLICY” in their place.^[1] Those words are a message to the officer that the electronic check was never going to work for this vehicle.

The second gap is the small carrier. Standing up a web service that answers every hour of every day is a real infrastructure commitment, so states exempt insurers below a volume threshold and let them report by other means. The Kansas Legislative Research Department’s review found the model act recommends exempting insurers covering no more than 1,000 vehicles in the state, and catalogued where each state actually set the line.^[4]

Add these together and, in the states running these checks, a predictable population of fully insured drivers returns unconfirmed: the rental car driver, the contractor in a fleet truck, the policyholder of a very small regional carrier, and anyone whose insurer’s server happened to be in its maintenance window. Alabama recommends that carriers schedule weekly downtime for Sunday mornings between 4 a.m. and 6 a.m. Central, with daily downtime between 3 a.m. and 4 a.m.^[1] A query that lands inside that window returns unconfirmed no matter how current the policy is.

When No One Types Anything: Automated Plate Readers

Everything above assumes an officer decided to run a plate. Automated license plate recognition removes the decision. New Jersey’s governing directive defines the technology as using optical character recognition on images to read vehicle registration plates and create vehicle location data, deployed either at a stationary location or mounted on a patrol vehicle.^[14]

The reading itself is a pattern-recognition problem. The camera captures a frame, software isolates the rectangle of the plate from the bumper around it, and optical character recognition converts the shapes into alphanumeric text. Everything that degrades contrast degrades the read: rain and fog scatter the infrared illumination, road grime and insect strike distort individual glyphs, and a camera mounted high on a pole sees the plate at an angle that compresses the characters. A misread digit produces an alert on a vehicle that was never on any list.

The alerting layer is where insurance status can enter. Plate reads are compared against watch lists — New Jersey calls them BOLO lists — which may be batch-downloaded from other databases including the National Crime Information Center, the National Insurance Crime Bureau, the Department of Homeland Security, and the state motor vehicle database, and must be refreshed at the start of each shift for mobile readers and at least daily for fixed ones.^[14] A registration suspended for an unresolved insurance lapse is the kind of state motor vehicle record that can reach a list of that sort.

A match is not automatically a basis to stop the car, and the directive says so. An officer alerted that an observed vehicle’s plate is on the list “may be required to make a reasonable effort to confirm that a wanted person is actually in the vehicle before the officer would have a lawful basis to stop the vehicle,” citing a 1996 New Jersey appellate decision holding there was no reasonable suspicion for a stop based on the registered owner’s suspended license unless the driver generally matches the owner’s physical description.^[14] As the next section shows, that is materially stricter than the federal constitutional floor.

The reads do not evaporate either. Under the same directive, plate data is retained for three years and then purged unless tied to an ongoing matter, access to stored non-alert data is limited to enumerated purposes, each access is logged with the user and the date, and every agency’s program is audited annually.^[14] Retention rules are set state by state and agency by agency; New Jersey is one published example, not a national standard.^[18]

Running the Plate Is Legal. Seeing Who You Are Is Regulated.

The reason no warrant is required to query a plate is that a plate is not private. State law requires it to be bolted to the outside of the car and displayed to the world, so reading it is an observation rather than a search.

What a query then reveals about the person is a separate question, and New Jersey answered it in 1998 in State v. Donis, 157 N.J. 44. The framework, which the state’s current plate-reader directive expressly continues to apply, limits law enforcement access to personal identifying information associated with a vehicle’s license plate unless there is a particularized basis for it.^{[14] [13]} The court named exactly what the first step may display: “information regarding only the registration status of the vehicle, the license status of the registered owner, and whether the vehicle has been reported stolen.”^[13] Insurance status is not on that list. The owner’s name, address, and other identifying details stay hidden until something in that first return justifies going further, and Directive 2022-12 continues the Donis framework without enlarging it.^[14] This is state constitutional law in New Jersey, not a national rule.

The federal restriction operates on the database rather than the screen. The Driver’s Privacy Protection Act, codified at 18 U.S.C. § 2721, prohibits a state department of motor vehicles and any officer, employee, or contractor from knowingly disclosing personal information from a motor vehicle record except as the statute permits, and it enumerates fourteen permissible uses.^[15] Law enforcement operates under the first of them, which covers use “by any government agency, including any court or law enforcement agency, in carrying out its functions.”^[15]

Read that clause closely, because the limit is inside it. The permission attaches to carrying out the agency’s functions. A query run to identify the driver of a car during a stop is within it. A query run to look up an ex-partner, a neighbor, or a celebrity is not, and the statute’s remedial provisions make unlawful obtaining or use actionable by the individual whose record was accessed.^[15] The word “personal information” is itself a defined term, carrying a specific list of identifiers rather than a general notion of privacy.^[16]

Enforcement of that boundary is administrative rather than technical: access is logged. New Jersey requires a record of the authorized user accessing stored plate data and the date, requires a justification for non-alert data, and mandates an annual audit certifying compliance.^[14] The verification systems carry a parallel confidentiality layer: Kansas exempts all insurer-supplied data and all verification responses from open records disclosure and deems them privileged and inadmissible in private civil actions, and Idaho, Illinois, Kentucky, Mississippi, Oklahoma, and West Virginia similarly exempt these records from open records provisions.^[4]

Can the Screen Alone Justify Pulling You Over?

An officer may initiate a brief investigative stop on reasonable suspicion, a standard the Supreme Court describes as requiring “a particularized and objective basis” to suspect wrongdoing — considerably less than probable cause, and grounded in the practical considerations of everyday life rather than legal technicality.^[11]

The Court applied that standard to a database hit in Kansas v. Glover, decided April 6, 2020. A deputy ran a pickup’s plate, learned the registered owner’s license had been revoked, and stopped the truck on the assumption that the owner was the one driving — without observing any traffic violation and without seeing the driver. The Kansas Supreme Court held that unconstitutional. The Supreme Court reversed, holding that when the officer lacks information negating the inference that the owner is driving, a stop made after running the plate and learning the owner’s license is revoked is reasonable under the Fourth Amendment.^[11]

The escape hatch is written into the holding. The inference can be dispelled by additional facts; if the officer can see that the driver does not match what the record says about the owner, the commonsense inference no longer stands.^[11] New Jersey’s directive builds that requirement in up front rather than leaving it to litigation.^[14]

An unconfirmed insurance return is a harder case than a revoked license, because the state itself has told the officer the answer might be wrong. Defense arguments follow directly from that: if the system concedes valid policies may exist that it cannot see, an unconfirmed result is not a particularized basis to suspect anything. The federal courts of appeals have nonetheless come down consistently the other way.

Mitchellis worth reading closely because it is recent and because the court declined the easy route. Arkansas law creates a rebuttable presumption that a vehicle is uninsured when the online verification system fails to show current coverage, and the government argued that presumption was enough. The panel said it doubted a state statutory presumption binds a court weighing a federal constitutional question, and decided the case on circuit precedent instead: an “unconfirmed” or “not found” response is sufficiently ambiguous to justify a brief investigatory stop, consistent with precedent allowing officers to detain someone to resolve ambiguous conduct.^[12]

The concurrence is where a driver’s actual leverage sits. Judge Kelly pointed to the Eighth Circuit’s earlier caution in United States v. Hanelthat its holding “should not be interpreted as justifying all warrantless vehicle stops based on ambiguous results from data searches,” because that outcome rested on express factual findings that the database was not inherently unreliable and that the officers were competent in using it. In Mitchellno such findings existed — but the defendant had not challenged the system’s reliability below, so the issue was not properly before the court.^[12] The reliability of a particular state’s verification system is a contestable question of fact, and it is waived if nobody raises it.

State legislatures have also intervened directly. The Kansas Legislative Research Department found that Illinois, Montana, and West Virginia statutes specify no law enforcement officer shall stop a vehicle solely to verify valid insurance, and that the Kansas act prohibits establishing compliance with vehicle insurance laws as the primary cause for a stop.^[4] In those states the federal floor is not the operative rule.

What You Actually Have to Hand Over

Whatever the screen said, the officer will ask for documents, and the verification systems are explicitly designed to be backstopped by them. Alabama lists the acceptable forms of evidence as an insurance card, the current declarations page of a liability policy, a liability insurance binder or legible copy, a certificate of insurance or legible copy, a motor vehicle rental agreement, and electronic evidence of insurance.^[1]

Electronic evidence appearing on that list is the important part for anyone who keeps the card in an app. Acceptance is set state by state rather than federally, so confirm the rule where you drive — but where it is accepted, a card displayed on a phone carries the same eight data elements as the printed one.

Handing an unlocked phone through the window creates a problem the paper card never did, and several states answered it inside the electronic-proof statute rather than leaving it to the Fourth Amendment. Texas Transportation Code § 601.053(d) provides that displaying an image with financial responsibility information on a wireless communication device “does not constitute effective consent for a law enforcement officer, or any other person, to access the contents of the wireless communication device except to view the financial responsibility information.”^[23] California Vehicle Code § 16028(g) is narrower still: where a person provides evidence of financial responsibility using a mobile electronic device, the peace officer “shall only view the evidence of financial responsibility and is prohibited from viewing any other content on the mobile electronic device.”^[22] Those are statutory limits, and they bind in the states that enacted them. The move that works regardless of which statute applies is mechanical: hold the screen up to the window instead of surrendering the phone, and nothing but the card is ever in the officer’s hands. A dead battery or no signal also defeats the app entirely, which is the practical case for keeping a printed copy in the glove box.

The rest of the interaction is choreography the officer has been trained in and you have not. The motor vehicle administrators’ association publishes guidance for drivers on what to do and expect during a stop — pull fully off the roadway, stay in the vehicle, keep your hands visible, and tell the officer before reaching into a glove box or console.^[19] Announcing the reach matters more than it sounds like it should, because the officer approaching the window is reading movement, not intent.

Why States Built This: The Uninsured Population

The Insurance Research Council estimates the uninsured share of motorists from claims data rather than from policy counts — specifically, the ratio of uninsured motorist claims to bodily injury claim frequencies. That methodology matters when reading the numbers, because it measures the uninsured population as it appears in crashes rather than as a census of registered vehicles.^[17]

The shape of that series is the argument for the systems described above. The rate fell for three consecutive years through 2019, then jumped 2.7 percentage points in 2020 and kept climbing, reaching 15.4 percent in 2023 — more than one driver in seven. Fifteen states and the District of Columbia sat above the countrywide rate in 2023; thirty-six states sat below it.^[17]

The spread is the enforcement story. A Mississippi officer works in a state where roughly one driver in four appears uninsured in the claims data; a Maine officer works in a state where the figure is one in eighteen.^[17] The penalties attached to the far end of that distribution are a separate subject, which we cover in our research on whether you can go to jail for not having car insurance.

High-Risk Drivers Are Monitored Continuously, Not at the Roadside

For most drivers, verification is episodic: it happens at a stop, a crash, or a registration transaction. For drivers under a financial responsibility filing, it is continuous, and the trigger is a cancellation rather than a query.

An SR-22 is not a kind of insurance. Oregon’s motor vehicle agency defines it as “a certificate showing that you have motor vehicle liability insurance” — a filing the insurer makes with the state on the driver’s behalf, and one the state will suspend driving privileges over if the driver fails to file it.^[20]

The monitoring runs through the cancellation side of the same arrangement. Nebraska states that where an SR-22 is required, “the insurance company is required to notify the Department of Motor Vehicles if you let your policy cancel or lapse for any reason,” and that the department is then required to take suspension action for an insurance cancellation.^[21]

Trace the chain and the difference from ordinary verification is clear. A missed premium causes the carrier to cancel. The cancellation obligates the carrier to notify the state. The notice obligates the state to act on the driver’s privileges. No officer, no plate query, and no traffic stop appears anywhere in that sequence — the record changes on its own, and the driver may find out when a letter arrives or when a plate reader flags the resulting suspension. Filing periods and reinstatement rules are set by each state; how the underlying premium moves after the conviction that triggered the filing is covered in our research on how much car insurance goes up after a DUI.

If the System Says You Are Uninsured and You Are Not

Produce the evidence at the roadside and let it override the screen. An unconfirmed response instructs the officer to rely on the evidence of insurance the driver presents, so the declarations page, binder, certificate, card, or electronic card is the operative document in that moment.^[1]

Ask your carrier which reason code its service returned. The codes are published, and they separate a data-format defect or an outage from an actual finding of no coverage on the date requested.^[1] A carrier that cannot answer that question is itself part of the problem.

Check whether the VIN on your policy matches the VIN on your registration. The VIN is the matching key, so a single wrong character in either record produces a permanent mismatch that no amount of paying your premium will fix.^[4]

Answer the state’s request for information rather than filing it. Alabama reviews registrations whose insurance could not be verified by sending owners a request for information, and suspends the registration 30 days after notification if the owner does not respond or the response shows the vehicle was uninsured with no valid exemption. Reinstatement costs $200 for a first violation and $400 plus a mandatory four-month registration suspension for a second.^[1] The letter is the cheap moment to fix the record; the traffic stop is not.

Carry a backup for rentals and work vehicles.If you drive a rental, a fleet truck, or anything on a garage or non-owner policy, Alabama’s system returns unconfirmed for those categories by design and most verification states exclude commercial vehicles outright, so the paper in the vehicle is the only thing that will confirm you.^{[1] [4]} The same documentation question arises at the registration counter, which we address in our research on whether you need proof of insurance to register a car.

Common Misconceptions, Corrected

“The state keeps a list of every insured car.” Not under the current model. Alabama states that insurers do not interface with a state database and that the state serves only as a conduit for the query and the response.^[1] The industry committee that wrote the standard argued specifically against storing coverage data in bulk at the state.^[3]

“If the computer says unconfirmed, I am getting a ticket.”The system tells the officer otherwise. Alabama’s guide says the term does not necessarily mean no insurance exists, and Arkansas’s response text instructs the officer to rely on the information the driver provides.^{[1] [12]}

“Every state can check my insurance electronically.”As of May 2025, statutes or regulations in 19 states referenced online verification systems — fewer than half the country. Most of those refer to online verification, but several reference state-operated databases rather than a live query routed to your carrier.^[4] In the other 31 states and the District of Columbia the check still runs through state records and the documents in your vehicle.

“An officer needs a reason to run my plate.”Not to read and query the plate itself. What is regulated is the personal information behind it — New Jersey’s framework withholds identifying details absent a particularized basis, and federal law restricts disclosure from motor vehicle records to enumerated permissible uses.^{[14] [15]}

“A database alert is never enough to stop me.” Under federal appellate law it generally is. Four circuits have held that an inconclusive insurance response supports reasonable suspicion for a brief investigatory stop.^[12] State law can be stricter, and in Illinois, Montana, West Virginia, and Kansas it is.^[4]

“Plate reader data disappears after the shift.” In New Jersey it is retained for three years before purging, with logged access and annual audits.^[14] Retention periods vary by jurisdiction and agency policy.