Coming next
Designed-but-not-yet-live checks, at a glance.
Today the workbench at /vet runs three checks: FMCSA
QCMobile, USPS address validation, and
Secretary of State (live across
ten states, manual-verify elsewhere). Three more are designed and
in build queue. Each is targeted at a specific dimension of the
Montgomery "ordinary care" standard that the existing FMCSA pull
doesn't reach.
This page exists so you know where the tool is going, not as a promise of dates. Each item below is a placeholder check page — click through for the design intent.
Domain lifecycle
Pulls the carrier's web presence: first Wayback Machine archive date, historical content snapshots, WHOIS creation date, and the WHOIS registrant name when it's not redacted (most US small- business domains are redacted post-GDPR — when it's there, it's gold).
Surfaces chameleon-carrier patterns: domains repurposed from unrelated businesses, web presence appearing the same week a new MC number was issued, domain creation date inconsistent with the carrier's claimed history.
Insurance certificate verification
Two paths. The auto path cross-checks the FMCSA L&I filing against contract minimums on every vetting. The conditional path, when you upload a COI to the workspace, sends a fresh-cert request to the producer named on the ACORD form — the standard broker move that forged COIs cannot survive.
The strongest single piece of paper a broker can put in their file. Designed to be free regardless of where the trucking- insurance industry lands on aggregator APIs.
Owner corroboration
Confirms the contact named on the MCS-150 is a real, identifiable person tied to the carrier — across multiple independent public sources. Pass = four out of ten independent confirmations (SoS officer match, WHOIS registrant, phone reverse-lookup, domain email plausibility, public news, county records, etc.). OFAC SDN screening runs always-on as a hard flag.
The 4-of-10 design is forgiving on purpose: even rural owner- operators can clear the bar through public records + phone + email + a local directory.
Why we don't promise dates
Each check has a different upstream dependency — a state SoS that may or may not have an API, a WHOIS registry that's mostly redacted, an insurance industry currently arguing about who gets to expose their data and how. Ship dates depend on which doors open in what order. The design work is done; the build work is sequenced around upstream cooperation.
What's deliberately not on this list
- Physical / map verification (Google Street View, building photos). Designed, currently on hold. Visual verification is more useful as a user-facing feature than a silent background check, and we'd rather do it right than do it now.
- Driver-level PSP data. Costs money, requires the carrier's consent, $10 a pull. Out of scope for the free public-data tier.
- Paid third-party safety scores. CARRIER411, MyCarrierPortal, similar. We're a free public-data tool. Users with paid subscriptions are free to bring their own; we don't relabel paid feeds.