By State / North Carolina
North Carolina Trucking Email Security
78.2% of active carrier domains in North Carolina have no enforced DMARC — leaving freight operators open to email impersonation, payment-redirect fraud, and cargo theft via phishing.
No enforced DMARC
78.2%
national: 80.1%
p=reject
8.7%
national: 7.5%
Microsoft 365
36.2%
national: 38.1%
M365 + no DMARC (carriers)
2,028
national: 92,822
MTA-STS
3.1%
national: 3.3%
DNSSEC
7.2%
national: 6.1%
Dead domains
470
of 7,893 scanned
Total carriers
9,256
473 with dead domain
Risk bands — North Carolina carriers
Carrier counts by risk band (composite email-security pain score). Critical = score 70+; Minimal = score <15.
| Risk band | Score range | Carriers | Domains |
|---|---|---|---|
| Critical | score 70+ | 788 | 677 |
| High | score 50–69 | 2,730 | 2,271 |
| Medium | score 30–49 | 3,543 | 3,152 |
| Low | score 15–29 | 1,662 | 1,265 |
| Minimal | score <15 | 60 | 58 |
North Carolina vs. national average
What the North Carolina numbers actually mean
DMARC posture. North Carolina's share of carrier domains with no enforced DMARC sits at 78.2% — better than the national average by 1.9 points. North Carolina carriers adopt the enforced p=reject DMARC policy at a meaningfully higher rate than the national pool. At the protective end of the distribution, 8.7% of North Carolina domains are at p=reject — the only DMARC policy that actually instructs receivers to drop spoofed mail.
Microsoft 365 surface. Microsoft 365 mailflow adoption sits below the national rate, which shifts the remediation surface toward self-hosted and Google Workspace estates where DMARC has to be configured at the DNS layer rather than flipped on in a tenant policy. That share is 21.9% of all North Carolina carriers — a one-flag-flip remediation set that any regional MSP or in-house IT lead can clear in a single quarter.
Transport encryption. MTA-STS adoption sits at 3.1%, materially below the threshold a freight payment-redirect attacker would have to clear to be inconvenienced by transport-layer policy. DNSSEC adoption in North Carolina runs at 7.2% (vs 6.1% national) — meaningful for downstream DKIM and MTA-STS validation, but still a minority signal.
Risk-band shape. North Carolina's critical and high bands combine to 38.0% of state carriers — close to the national distribution, meaning remediation prioritization here should follow the same shape as the national program. The composite pain score blends SPF posture, DMARC enforcement, MTA-STS presence, and DNSSEC — so a carrier clusters in the critical band only when several controls fail together. Remediation that flips DMARC to enforcement plus turns on MTA-STS typically moves a carrier two bands down in one quarter.
What this means for buyers and shippers. If you are dispatching freight, settling broker payments, or receiving rate confirmations from North Carolina-based carriers, the operational exposure is the 78.2%of domains that cannot stop a stranger from sending email in the carrier's name. Payment-redirect and load-redirect fraud rides on exactly that gap. Verifying a counterparty's DMARC posture before a first wire — a 30-second DNS lookup — is the cheapest control in the freight stack.
Compare North Carolina with other states
States closest in carrier-count rank to North Carolina. Each is scored on the same DNS-derived control set, so the comparison is apples-to-apples.
See where your own domain stands
The research is free and self-serve. Run the same public checks on your own domain in about a minute — SPF, DKIM, DMARC, MTA-STS, DNSSEC, and more — and get a scored report by email. No agents, no credentials.
Data as of 2026-05-20from public DNS measurements. Statistics are domain-weighted unless noted. State scope is the carrier's FMCSA-registered state. Methodology: read the full index.