How to verify a broker’s MC number before you call

All of this is free, all of it is public record, and none of it needs our tool. The reason nobody runs it on every load isn’t that it’s hard — it’s that it’s four different pages, and you’re looking at hundreds of postings.

Step one: get the MC

On the DAT One board a collapsed row gives you the company name and one contact — a phone number or an email address, not both. The MC number appears when you open the load. That is worth knowing because it shapes everything below: until you expand, you are checking a name and a contact, which is a weaker question than checking an authority.

If a posting never produces an MC at all, that is itself the first thing to notice. You cannot verify what you were not given, and “call me and I’ll send the packet” is not a substitute.

The one check that ends it

It works because the whole shape of an impersonation is a real name attached to a contact the poster controls. The name survives the check. The contact does not.

Five things the record tells you

1. The name on the authority

Compare the company name in the posting with the legal name and DBA that FMCSA holds for that MC. They should be recognisably the same business.

Read a mismatch as a question, not an answer. Names differ from the record for entirely ordinary reasons: a rename that hasn’t propagated, a DBA that isn’t the legal name, an acquisition, an authority that changed hands, or one FMCSA dataset simply lagging another. We treat a name mismatch as serious only when something else fires alongside it — on its own it is a reason to ask, and that is deliberate.

2. How old the authority is

The record shows when broker authority was granted, and whether it was reinstated after a lapse. New authority is not evidence of anything — honest carriers and brokers get theirs every day. What it changes is how much verifying is worth doing before you hand over a packet.

For reference, these are the lines we draw: granted within the last 12 months is worth a look, within 6 months more so, and a reinstatement inside the last 180 days is worth noting. A reinstatement on its own is weak — established brokers lapse and come back over paperwork all the time.

3. Whether the bond is on file

An MC existing and a surety bond being on file are two separate questions, and the second one is the one that matters if you don’t get paid. Brokers file a BMC-84 bond or a BMC-85 trust fund, and FMCSA publishes a roster of who currently has one.

This is the check with the most misinformation around it, so it has its own page: what a broker bond is, and what “not on file” actually means.

4. The contact on file

The record carries a phone number and, for some brokers, an email address. These are two very different signals and treating them the same is how a checking habit turns into noise:

• A phone that differs is weak. Large brokers post regional dispatch lines that are nothing like the number on their FMCSA filing, and FMCSA contact data goes stale. We count a phone mismatch only as support for something else; on its own it never raises a badge.
• An email that differs is interesting in exactly one shape: the posting wants your packet at a free consumer mailbox — the kind of address anyone can create in a minute — while the broker has a company domain on file. A different company domain is usually just drift, a parent company’s domain, or a branch address, and reading that as a red flag will have you rejecting good loads by Thursday.

5. The address — and who else is at it

You can read the physical address off the record in a second. What you cannot easily do by hand is the useful part: count how many other active authorities file from that same address, or share that same registered phone or email. That is a genuine limit of manual checking, and it is worth saying plainly rather than pretending otherwise.

It also has an ordinary explanation more often than not. Freight offices, business parks, registered agents and process-agent services all put many unrelated authorities at one address, and a corporate family will file every entity at one headquarters. A shared address is a fact about the neighbours, not an accusation about the subject — which is why, when we surface it, the ordinary explanation is printed next to it rather than hidden in a tooltip.

The check that isn’t on the FMCSA record at all

Look hard at the domain they want the packet sent to. This is the highest-yield check on the page and the record can’t help you with it.

• Look-alike domains. One extra letter, a swapped word, a hyphen that isn’t there, .co instead of .com. Read fast, on a phone, between calls — that’s the entire trick, and it is very hard to catch by reading.
• Domain age. Any free WHOIS or RDAP lookup returns a registration date in about ten seconds. A domain registered days ago, sending you paperwork, answers the question by itself. Our own thresholds: under 90 days is worth noting, 21 days or under is a serious fact.
• Where the booking contact is buried. On a load board the tell is frequently not in the contact field but in the posting’s own comments — a booking email on a domain that isn’t the broker’s, an address written as x (at) gmail dot com to get past a filter, “email only, no calls,” or a redirect to a messaging app.

What the record can never tell you

• Whether they pay, or pay on time. That is credit data and it lives in a different kind of product entirely. The FMCSA record answers an identity question, not a payment one.
• Whether the person on the phone is the company on the record. This is the important one. A clean record means the authority is real and in good order. It says nothing about who is currently using its name — which is precisely why check number one is a phone call to the number on the record rather than a reading exercise.
• Whether a bond was canceled. Genuinely nobody can tell you that from published FMCSA data. Why that is, in detail.

Where to look

Those addresses are written out rather than linked on purpose. On a page about impersonation, the habit worth building is typing the address into the bar yourself instead of following a link somebody handed you. FMCSA does not email you a sign-in link.

This is the part we automated

Nothing above is a secret and nothing above is new. The problem is arithmetic: run that sequence properly on a broker and it is not a fast piece of work, and a dispatcher scans hundreds of postings a day. Nobody does it two hundred times. That gap is the whole reason identity-based freight fraud works at all.

So LaneScout runs it on the row. It is a Chrome extension for the DAT One load board: as rows render, each broker is checked against our copy of the public FMCSA record and the row gets a badge. No lookup, no second tab, no copy-paste.

Click the badge and you get the specific line that fired, where it came from, and the date the record was pulled — not a score out of a hundred. Our copy of the FMCSA broker file is rebuilt every morning. On the collapsed row the match is provisional, made from the company name and the one contact the row shows; open the load and it re-resolves against the exact MC, and an authoritative badge is never downgraded by a later guess.

Badges are free on every row. It is DAT One only, it will not tell you anything about payment history, and it never labels anybody: every line is a checkable fact about a public record, and any company can contest one at lanescout.io/dispute without an account.