Have feedback, a feature request, or found a bug? I'd love to hear from you.
VIN Inspector Pro is built and maintained by Vatsal Mishra, a Machine Learning Software Engineer based in Chicago. Whether you've got an idea for a new feature, ran into an issue, or just want to share how the tool helped you avoid a bad deal, don't hesitate to reach out.
I personally read and respond to every message. Typical response time is within 24 hours.
Yes. If you share the VIN you entered (and the key results you’re unsure about), I can help you understand what the report is indicating and which next steps make sense—like whether to schedule an open recall, what types of inspection items to prioritize, or how to interpret mileage risk signals. I can’t replace a mechanic, but I can help you translate the data into a practical decision checklist before you meet a seller.
All vehicle data comes from official U.S. government sources: NHTSA for recalls, safety ratings, complaints, and VIN decoding; the EPA for fuel economy figures; and NMVTIS-approved providers for title history. We do not make up or estimate safety data.
No. VINs are queried against the NHTSA API in real time and not stored on our servers. Photos uploaded to the Photo Inspector are sent directly to the AI model for analysis and are not saved or retained after the session ends.
Please email us with the VIN you searched and a description of the issue. NHTSA data is occasionally incomplete for certain vehicle trims or model years — if you notice a discrepancy, we want to know so we can handle it better. We take data accuracy seriously.
Absolutely — feature requests are welcome and genuinely considered. Past user suggestions have led to the addition of crash test ratings, the Photo Inspector tool, and the stolen vehicle check section. Send your idea to the email above.
If you reach out, the best messages are the ones that include context. Whether you’re trying to avoid a bad deal or you’re reporting a problem, these are the areas we can help with most effectively:
If a VIN can’t be parsed, returns unexpected results, or fails for specific model years, send the VIN plus what you expected to see. This helps me reproduce the issue and fix it.
If something looks “off,” tell me what part of the report surprised you (recalls, mileage integrity, title info, or safety ratings). Sometimes the raw data has edge cases, and I can explain what the source likely contains and how to interpret it.
Examples include clearer explanations, better decision checklists, new guide content, accessibility improvements, or export/share options for reports. The goal is always the same: help buyers act on the data.
If you run a site, tool, or community that could benefit buyers (or help validate report workflows), send a short overview of your idea. I’m happy to discuss integrations and best practices.
When you message, please include: the VIN you searched (or the slug/page you’re viewing), what you expected, and what you observed. That small amount of detail dramatically speeds up response time and improves the quality of help you receive.
VIN Inspector Pro was built out of frustration with the used car market. Paid vehicle history services charge $40+ per report, while the same core data — recalls, safety ratings, complaints — is freely available from the U.S. government. This tool makes that data easy to access for any buyer, for free.
The project is maintained by a single developer. Your feedback directly shapes what gets built next. If the tool helped you avoid a bad deal or negotiate a better price, I'd genuinely love to hear about it.