Free tool · No signup · No storage
Carrier email red-flag scanner.
Paste a suspicious carrier email. We extract any MC numbers and verify them live against FMCSA, then scan the text for the patterns brokers see in double-broker and stolen-MC attempts. You get a risk score plus the per-signal breakdown. Free, no signup, we don't store the email.
Live
FMCSA QCMobile on every MC extracted
Same data as the SAFER lookup
~10
Textual fraud signals scanned
Domain, urgency, payment, multi-MC, more
$0
Free, no storage, no signup
Tool, not a lead form
What the scanner is good at — and what it isn't
The scanner reads what's in the email plus what FMCSA says about any MC numbers mentioned. That covers a real majority of carrier-fraud attempts because most stolen-MC and double-broker workflows leave fingerprints in the email body or the FMCSA record. It will not catch every fraud — particularly not the ones where a fully-legitimate carrier (real MC, current authority, clean insurance) accepts the load and then re-brokers it after. For those, the only defense is post-booking monitoring (driver verification 24 hours before pickup, GPS tracking from first mile, check-call discipline).
The signals it scans
- Sender domain. Quotes from gmail.com / yahoo / hotmail aren't auto-disqualifying (legitimate dispatch services use them) but combine with other signals.
- Multi-domain mentions. Several different corporate domains in one email signals dispatch-service relays or, less benign, identity stitching.
- Multiple MC numbers in one quote. The single strongest textual tell for double-brokering or stolen-identity patterns.
- FMCSA authority. Every MC referenced gets a live QCMobile check. Revoked, inactive, or OOS = hard stop.
- Urgency / pressure cues. "Need answer ASAP", "moving today only". Common in legitimate spot-market quotes too — informational only on its own.
- Payment red flags. Upfront comcheck or quickpay demands, refusal of factoring, "direct deposit only" insistence. Disproportionately correlate with carriers that vanish after pickup.
- Missing phone. No driver cell shared at booking is one of the most common late-stage fraud signals.
Use it alongside the rest of the vetting flow
- Free FMCSA lookup — for verifying a single MC or DOT in isolation
- How to vet a carrier — 60-second flow
- 25-point carrier vetting checklist
- 9-step double-brokering prevention guide
- Anatomy of a fraudulent carrier email — the 7-red-flag deep dive
Frequently asked questions
What does this scanner actually check?+
Three layers. (1) Heuristic text signals — sender uses a generic email domain, multiple corporate domains in one message, multiple MC numbers referenced (a classic double-broker tell), urgency / pressure cues, upfront comcheck or quickpay demands, all-in rate phrasing without breakdown, missing driver phone. (2) Live FMCSA QCMobile verification on every MC number it extracts — authority status, OOS, legal name. (3) A weighted risk score rolling it all up.
Is this a definitive fraud detector?+
No — and any tool that claims to be is overselling. The scanner reads textual patterns plus FMCSA data. It will catch most classic stolen-MC and double-broker tells. It will miss inside jobs (a real carrier with valid authority planning to re-broker after acceptance), forged insurance certificates, and any signal that lives outside the email text. Treat the score as one input into your vetting flow, not the answer.
Do you store the email I paste?+
No. The scan runs server-side, the result returns, and the text is gone. We don't log the body and we don't train on it. The MC numbers we extract get cached briefly via the FMCSA client's hourly revalidate, same as the FMCSA lookup tool.
Why is the score 'High' even though the email looks normal?+
A few signals stack fast. An MC that doesn't resolve in FMCSA QCMobile is high-severity (30 points) on its own. A revoked or OOS MC is another 30. So a single email that mentions a defunct MC will score high even without other signals. Read the per-signal breakdown — the label is a sum, not a verdict.
Why is the score 'Low' on an email that feels fishy?+
Many fraud workflows succeed precisely because the email text looks clean. The textual layer is a screening pass, not proof of safety. Always pair this with a direct FMCSA verification, an insurance cert pull from L&I (not from the carrier's email attachment), a driver-name + cell capture before pickup, and a 24-hour-before-pickup driver call.
Where does the same check live inside Keelway?+
Inside the product, this scan runs automatically on every inbound carrier reply — including continuous FMCSA monitoring, insurance verification from L&I directly, double-broker pattern matching against your own historical book, and chameleon-MC reincorporation detection. The free tool here is the one-off screening version of the per-email pipeline.
Want this scan on every reply, automatically?