Keelway
Sign in Book a demo Get Keelway free
Carrier
M01Carrier TMS M02Invoice & Collections Agent M03Track & Trace M04Email Agent M05Voice Agent
Broker
M01Broker TMS M02Fraud AI · CarrierVet M03Track & Trace M04Email Agent M05Voice Agent
Integrations PricingSign in
Identity verification · Fraud signals · Inbox-native

Identity fraud arrives by email. Verify it there.

Nobody steals a load by walking into your office. They email you — from a domain one character off a real carrier's, quoting under a hijacked authority, sounding exactly like the hundred legitimate carriers in the same inbox. Keelway runs identity checks on every inbound carrier email, at the moment it lands, before anyone can book the wrong "carrier."

< 2s
identity + FMCSA check per inbound email
Keelway infrastructure, 2026
< 600ms
Fraud Shield server-side screen (beta)
Keelway product data, 2026
21
risk rules in the free CarrierVet extension
CarrierVet, 2026
Domain

Does the email match the registration?

Sender domain checked against the carrier's FMCSA-registered contact information, plus domain-age signals. A nine-day-old domain claiming to be a twelve-year-old carrier is the classic spoof tell.
Identity

Does the authority match the claim?

MC-DOT consistency checks, and flags when a dispatcher quotes from a different authority than the carrier they claim to represent — the standard double-broker setup.
History

Is this authority what it says it is?

Chameleon detection: authorities registered within the past 90 days with identity overlap to previously revoked ones. Fresh paper, old operator — flagged before the first booking.
Score

One number, reasons attached

Identity signals combine with FMCSA authority, insurance, and safety data into the 0–100 trust score on every reply. Every score expands to its contributing signals — no black box.

Frequently asked questions

What is carrier identity verification?+
Carrier identity verification is confirming that the party you're about to book is actually the carrier they claim to be — not a fraudster borrowing a legitimate USDOT, a spoofed email domain impersonating a real company, or a chameleon operator running a fresh authority after a revocation. It goes beyond checking that an authority is active; it checks that the person emailing you is connected to that authority.
How does carrier identity fraud actually work?+
The common plays, all covered in trade press reporting on freight fraud: a fraudster spoofs or slightly misspells a legitimate carrier's email domain and quotes on loads under that carrier's identity; a hijacked authority — login credentials or contact records taken over, sometimes after an ownership change — books loads that then get re-brokered or stolen; and chameleon carriers open fresh authorities to shed the history of a revoked one. What the plays share is the entry point: every one of them arrives in a broker's inbox as an ordinary-looking carrier email.
Why is the inbox the right place to verify identity?+
Because that's where the impersonation happens. A network-layer identity check verifies the carrier entity; it doesn't see that the email in front of you came from a domain registered nine days ago that almost matches the real carrier's. Verifying at the inbox means the check runs on the actual artifact of the fraud — the email — at the moment of contact, on every inbound carrier, including the ones you'd never think to check manually.
What identity signals does Keelway check?+
On every inbound carrier email: whether the sender's domain matches the carrier's FMCSA-registered contact information; email-domain age; whether the MC/DOT quoted matches the identity claimed in the email; chameleon patterns — authorities registered within the past 90 days with identity overlap to previously revoked ones; and dispatchers quoting from a different authority than the carrier they claim to represent. Signals combine into the 0–100 trust score with reasons attached. The Fraud Shield add-on ($199/mo, in beta) layers deeper checks — phishing patterns and rate-con interception alerts — scored server-side in under 600 ms (Keelway product data, 2026).
What should I do when an identity flag fires?+
Don't book, and don't tip your hand by replying to the flagged email. Verify out-of-band: call the carrier at the phone number on their FMCSA registration — not the number in the email signature — and confirm they actually quoted your load. Check the domain character-by-character against the registered contact. If the carrier is real but the email isn't, you've just caught an impersonation; let the real carrier know. Flags in Keelway move the thread to a review queue where you can override with a note or decline and log why.
Is identity verification enough by itself?+
No — it's one layer of three. Identity verification confirms who you're talking to. Vetting confirms the carrier is fit to haul — authority, insurance, safety history. Monitoring confirms all of it stays true between quote and delivery, which is why Keelway re-checks at acceptance and at pickup. A broker running all three layers from the inbox catches most of what shows up; any single layer alone has documented blind spots.
The fraud is in the email. So is the check.

Verify every carrier at the moment they email you.

Related