Fake Load Posting Checklist

How this comes up in practice

A load posting that uses a legitimate broker's MC number and company name requires only publicly available information to create. The contact email in the posting may differ by one character from the real broker's domain. Responding to that email — or sending a carrier packet to it — means the packet goes to whoever created the posting, not to the actual broker. The verification that prevents this: checking the contact email domain character by character against the broker's real domain from a prior confirmed source, and calling the broker's main office to ask whether they created this specific posting. A posting is a lead to investigate; it is not itself verification of the poster's identity.

What a load board posting can and can't establish about a broker

A load board posting establishes that someone created an account and posted a load. It doesn't establish that person is authorized to act for the broker entity named in the posting. The fraud works because everything in a posting that a legitimate broker could provide — a real MC number, a plausible rate, a recognizable shipper location — is also available to a fraudster with access to public FMCSA records and knowledge of normal freight lanes. For adjacent verification steps, compare this with Load Board Scam Red Flags, How to Verify a Freight Broker, and Too-Good-To-Be-True Rate Signals.

The verification step that most carriers skip is confirming that the posting came from someone with actual authority to represent the named broker. The posting creates the impression of authorization; the confirmation call creates actual evidence of it. Responding to a posting without that call means sending documents or pickup details to whoever controls the account, not necessarily to the broker named in it.

This checklist puts the identity verification step before any response to the posting, because the order matters: a carrier packet sent to a fraudulent account can't be unsent. Verifying the broker's identity through a contact established independently of the posting — then responding — keeps the cart in the right order.

Verifying the identity behind a load board posting before responding

A fake load posting can be created in minutes using a legitimate company's name and MC number. The posting may include a real shipper location, a plausible rate, and an email domain that differs from the legitimate broker's by one character. The goal is to get a carrier to send a packet, respond with driver details, or take a load without completing the identity verification that would catch the misrepresentation.

The verification that matters isn't checking the load board's records — it's confirming the broker identity through a channel that was established independently. The posting should be treated as a lead to verify, not as the verification itself.

Records to check before responding to an unfamiliar posting

Load board review treats the post as a lead that still needs identity verification. In this guide, that starts with broker identity, rate, lane, shipper details, contact domain, and packet requests.

Capture the account, posting details, rate, lane, domain, and packet request before the post is edited or removed. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

What to save from a posting before acting or sending documents

For fake load posting checklist, the useful record is usually the one that shows where broker identity, rate, lane, shipper details, contact domain, and packet requests first entered the file.

That record is stronger when it sits beside the dated lookup, the original message, and a note from the posting account owner or independently confirmed company contact. It is weaker when it has been renamed, cropped, forwarded without headers, or separated from the transaction timeline.

Questions that verify the posting's actual origin before any contact

Hold the booking, dispatch, pickup, or payment decision when the file depends on a new contact path, revised document, missing official record, or mismatch that no one has explained.

The pause should be narrow and written down: the field that does not line up, the source used to check it, and the person or channel that must answer before the work continues.

What a real MC number in a posting doesn't confirm about who created it

Save screenshots early because load board details and message threads can disappear after the other party changes course. In this guide, that starts with broker identity, rate, lane, shipper details, contact domain, and packet requests.

The useful file shows how the posting identity connected, or failed to connect, to the broker or carrier records behind it. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

When a posting requires a broker callback before any packet is shared

Load board questions should verify the party behind the account before documents or pickup details are shared. In this guide, that starts with broker identity, rate, lane, shipper details, contact domain, and packet requests.

A strong answer comes through a known company contact, not through the same profile that created the concern. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

Further context on posting verification

A marketplace profile can be compromised or reused. Treat reputation signals as context, not identity proof. In this guide, that starts with broker identity, rate, lane, shipper details, contact domain, and packet requests.

When a posting feels unusually urgent or generous, slow down enough to preserve the evidence and verify the entity. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

When the posting warrants a report

Escalate when the posting identity cannot be confirmed or when the account appears to be part of spoofing, phishing, or identity misuse. In this guide, that starts with broker identity, rate, lane, shipper details, contact domain, and packet requests.

Use platform reporting, known company contacts, IC3, FTC, or FMCSA resources according to the facts and the records you saved. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

Source Notes

FAQ