Double-broker check — spot fraud before you tender

Q: What is double-brokering?

Double-brokering is when a carrier tendered a load by a broker re-tenders that load to a different carrier without authorization. The cargo ends up under the control of a party the original broker has not vetted and has no contract with, which is the mechanism behind most modern freight-theft cases.

Q: Is double-brokering illegal?

Re-brokering a load without proper broker authority is a violation of FMCSA regulations and exposes the carrier to OP-1 enforcement. FMCSA has been increasing penalties since 2023, but the enforcement gap (30–90 days) is wide enough that real-time vetting is still the only reliable defense.

Q: Can KnowHaul guarantee a carrier won't double-broker?

No — and any tool that claims to should be treated with suspicion. What we can do is surface the precursor patterns we see in confirmed incidents (MC reuse, identity flips, dormant reactivations, address mismatches) so you can make an informed call before tendering. A clean verdict means we couldn't find any of the high-correlation precursors, not that the carrier is incapable of fraud.

Q: How fresh is the fraud-signal data?

Authority status, insurance filings, and registration changes refresh within 24 hours of the public filing posting. Inspection-driven signals (equipment footprint, lane activity) refresh within the hour. We don't rely on a third-party fraud feed — every signal is derived from primary FMCSA data.

Q: Do I need an account to run a double-broker check?

No. Single-carrier double-broker checks are free with no per-search fee or signup. Bulk export and API access (for brokerages running 100+ tenders/day) require an account.

Paste a DOT or MC number. KnowHaul rolls up dormancy reactivation, domicile-footprint mismatch, implausible fleet growth, and paper-carrier signals into a single fraud verdict — derived from the FMCSA filings, refreshed nightly.

FAIL0/100

Double-brokering-specific risk — may differ from this carrier’s overall fraud score on its profile.

High-confidence signal(s) on file. Do not tender without resolving these signals. This does not mean the carrier committed fraud — it means the risk is too high to tender without further verification.

VANNER INC

DOT 3048083 · MC 48378 · IL

High risk

Multiple double-broker precursor signals are firing, or a dormant-then-reactivated authority is on file. Vet carefully before tendering.

Triggered signals (58)

vin_under_multiple_mcstruck VIN 3AKJHHDR1LSLH8523data as of 2026-05-19
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 1FUJHHDR4LLLK2088data as of 2026-05-11
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR9RSUY6031data as of 2025-10-15
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR2SSVS7301data as of 2025-09-25
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR5JSJR0847data as of 2025-03-25
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHFG8LSLR8509data as of 2026-02-04
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 1FUJHHDR0PLUK5448data as of 2025-08-07
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 1FUJHHDR0PLUK5451data as of 2026-05-26
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 1FUJHHDV5LLKT6981data as of 2026-05-23
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 1FUJHHDR6PLUK5454data as of 2026-05-13
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR0KSKE2043data as of 2025-12-17
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR0LSLK1475data as of 2026-02-16
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR0SSVS7300data as of 2026-03-25
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR6RSUY6021data as of 2026-04-25
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 1XKYDP9X6NJ133237data as of 2025-01-31
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR7NSMZ0282data as of 2026-02-24
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR5TSWN2634data as of 2026-06-04
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDRXRSUY6023data as of 2025-11-21
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR3NSNC6335data as of 2026-04-30
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR6RSUK8376data as of 2026-04-03
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 1M1AN4GY9KM010143data as of 2026-04-12
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR5LSLG5144data as of 2026-03-24
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 1XKYD49X1KJ225575data as of 2025-03-26
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR9PSNV1439data as of 2026-04-16
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR5MSMU3640data as of 2025-03-21
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR0LSLZ0540data as of 2025-11-30
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDRXLSLM5556data as of 2026-03-12
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR9PSNK1230data as of 2026-04-17
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR3LSME5767data as of 2026-05-18
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR2PSNK1229data as of 2025-01-24
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR3MSMC0708data as of 2026-03-19
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR4KSKB3533data as of 2025-09-18
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR4NSNC6330data as of 2026-04-24
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR9NSNC6338data as of 2025-12-03
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR7RSUK8371data as of 2026-02-10
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR0NSND8006data as of 2026-05-23
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR6KSKD2309data as of 2026-02-03
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR0RSUY6032data as of 2026-05-23
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHFG4RSUM6791data as of 2025-09-24
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDRXTSWN2645data as of 2026-05-08
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR5LSLG4950data as of 2026-02-06
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR9LSLM9677data as of 2025-11-01
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHFGXRSUM6794data as of 2026-04-16
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR7SSVW5087data as of 2024-08-24
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR4SSVW5077data as of 2025-11-11
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3AKJHHDR6SSVS7303data as of 2025-05-30
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 4V4NC9EH5PN337085data as of 2024-12-11
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 4V4NC9EH9LN200516data as of 2026-04-28
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 4V4NC9EH2HN987297data as of 2025-08-29
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 4V4NC9EH7RN659231data as of 2026-04-24
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 4V4NC9EJ8SN660591data as of 2026-04-07
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 4V4NC9EJ9HN962643data as of 2025-08-20
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 4V4NC9EHXSN686462data as of 2026-05-03
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 4V4NC9EH6NN318980data as of 2026-04-06
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 3HSDZTZR1MN861430data as of 2025-06-27
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 4V4NC9EJ5MN285097data as of 2026-01-13
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 4V4NC9EH1SN686463data as of 2026-04-17
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.
vin_under_multiple_mcstruck VIN 4V4NC9EH2LN241022data as of 2025-10-08
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.

What to verify before you tender

Confirm dispatcher email domain matches the company name
Free email domains (gmail, outlook, yahoo) combined with a brand-new MC is the highest-correlation pair in our incident data. If the domain doesn't match the company name, verify identity by a second channel before tendering.
Cross-check the phone area code against the registered address state
Re-brokering operations frequently answer from a number whose area code doesn't match the carrier's registered address state. Alone it's not conclusive — paired with one other signal, it's worth a live callback.

View full carrier profile →

What is double-brokering? How do these signals work?(expand)

Want the full primer? Read the guide: What is double-brokering?.

Double-broker check — spot fraud before you tender

Double-brokering happens when a carrier re-tenders your load to someone else without permission — usually to a freshly-issued MC with no track record. By the time the cargo is missing, the original MC is already dormant. KnowHaul checks every name and DOT against the patterns we see in real double-broker incidents: MC reuse, identity flips, dormant authority that reactivated in the last 90 days, and physical-address mismatches.

Quick Answer

Type the carrier's name, DOT, or MC into the search box. KnowHaul cross-checks the MC against four fraud-precursor patterns in under a second and surfaces a risk verdict alongside the carrier's authority, insurance, and inspection footprint.

9,000+

Fraud signals tracked

<1s

Verdict latency

90 days

Reactivation window

What double-brokering actually looks like

Double-brokering isn't an exotic crime ring — most cases are a small carrier or dispatcher with a phone, a clean-looking MC, and a willingness to re-tender. The cargo is usually electronics, tires, or food-grade freight that liquidates fast. The broker doesn't find out until the consignee calls asking where their truck is.

Three patterns we see weekly

(1) An MC under 90 days old answers a posted load by phone and asks for the rate confirmation by email rather than over the load board. (2) The dispatcher's email domain doesn't match the company name on file. (3) The MC was recently revoked, reinstated, and is now operating under a slightly different DBA — the same person, a different paper trail.

Fraud signals we watch for

KnowHaul's rules engine scores every MC against signals that public FMCSA records don't combine for you. None of these are individually conclusive — they're precursors. The verdict combines all of them with the carrier's own inspection record.

Signal	Why it matters	How we derive it
MC age	Brand-new MCs are over-represented in confirmed double-broker incidents	FMCSA registration date vs today
Dormant-then-reactivated	A reactivated authority is the easiest way to skip a fresh review	Authority history from the L&I register
Identity-flip pattern	Same physical address + new legal name = a likely re-shell	Address + name overlap across FMCSA registrations
Address mismatch	Carriers re-brokering loads often answer from a virtual office	Cross-reference FMCSA address vs phone area code + inspection state
Equipment vs cargo claim	A carrier with zero reefers shouldn't be booking refrigerated lanes	VIN-decoded equipment from roadside inspections

Why public records won't flag this directly

FMCSA fields like 'authority status' tell you whether a carrier can legally haul today — they don't tell you whether the entity is recycled paperwork from a previously-banned operator. We compute the precursor patterns from raw filings rather than relying on the public verdict.

How to run a check on a tender

There are two ways to verify a carrier before a tender. The single-carrier check is the right call for almost everyone; the bulk export is for brokers running 100+ tenders a day.

Method	When to use it	Latency
Single-carrier lookup	You have one MC to vet before tendering this load	<1 second
Lane-driven shortlist	You want to start from carriers that already run your lane	<2 seconds

What FMCSA's own data doesn't flag

OP-1 enforcement is improving, but the gap brokers care about is real-time: FMCSA can take 30–90 days to update a carrier's status after a complaint. KnowHaul fills that gap by computing the precursor patterns from the raw filings the same day they post, rather than waiting for an enforcement verdict.

Same-day data refresh

Operating authority, insurance, and registration changes refresh within 24 hours of the public filing posting. Inspection-driven signals update inside the hour.

Pro Tips

Treat any MC under 90 days old as elevated risk. Not all new MCs are bad actors — but every confirmed double-broker incident we've reviewed involved an MC less than three months old. Ask for a second proof of operation before tendering.
Confirm the dispatcher's email domain matches the legal name. Free email domains (gmail, outlook, yahoo) are common for legitimate small carriers, but a domain that doesn't match the company name AND a brand-new MC is the highest-correlation pair in our incident data.
Cross-check the phone area code against the FMCSA physical address. Re-brokering operations frequently answer from a number whose area code doesn't match the registered address state. It's not conclusive on its own — combined with one other signal, it's worth a callback.

Frequently Asked Questions

What is double-brokering?

Double-brokering is when a carrier tendered a load by a broker re-tenders that load to a different carrier without authorization. The cargo ends up under the control of a party the original broker has not vetted and has no contract with, which is the mechanism behind most modern freight-theft cases.

Is double-brokering illegal?

Re-brokering a load without proper broker authority is a violation of FMCSA regulations and exposes the carrier to OP-1 enforcement. FMCSA has been increasing penalties since 2023, but the enforcement gap (30–90 days) is wide enough that real-time vetting is still the only reliable defense.

Can KnowHaul guarantee a carrier won't double-broker?

No — and any tool that claims to should be treated with suspicion. What we can do is surface the precursor patterns we see in confirmed incidents (MC reuse, identity flips, dormant reactivations, address mismatches) so you can make an informed call before tendering. A clean verdict means we couldn't find any of the high-correlation precursors, not that the carrier is incapable of fraud.

How fresh is the fraud-signal data?

Authority status, insurance filings, and registration changes refresh within 24 hours of the public filing posting. Inspection-driven signals (equipment footprint, lane activity) refresh within the hour. We don't rely on a third-party fraud feed — every signal is derived from primary FMCSA data.

Do I need an account to run a double-broker check?

No. Single-carrier double-broker checks are free with no per-search fee or signup. Bulk export and API access (for brokerages running 100+ tenders/day) require an account.

Vet your next tender

Paste an MC, DOT, or carrier name. Get a fraud-signal verdict in under a second.

Run a check Read the double-brokering guide