Skip to main content

By State / North Dakota

North Dakota Trucking Email Security

77.6% of active carrier domains in North Dakota have no enforced DMARC — leaving freight operators open to email impersonation, payment-redirect fraud, and cargo theft via phishing.

Edition: 2026-Q2State rank: #46Carriers: 2,035Domains: 1,361
By Stefan Efros, CEO & Founder, EFROS
Updated ·

No enforced DMARC

77.6%

national: 80.1%

p=reject

8.9%

national: 7.5%

Microsoft 365

40.5%

national: 38.1%

M365 + no DMARC (carriers)

416

national: 92,822

MTA-STS

3.1%

national: 3.3%

DNSSEC

5.6%

national: 6.1%

Dead domains

64

of 1,361 scanned

Total carriers

2,035

65 with dead domain

Risk bands — North Dakota carriers

Carrier counts by risk band (composite email-security pain score). Critical = score 70+; Minimal = score <15.

Risk bandScore rangeCarriersDomains
Criticalscore 70+9789
Highscore 50–69466397
Mediumscore 30–49857581
Lowscore 15–29531216
Minimalscore <151914

North Dakota vs. national average

No enforced DMARC77.6%vs 80.1% national
p=reject adoption8.9%vs 7.5% national
MTA-STS3.1%vs 3.3% national
DNSSEC5.6%vs 6.1% national

What the North Dakota numbers actually mean

DMARC posture. North Dakota's share of carrier domains with no enforced DMARC sits at 77.6% better than the national average by 2.5 points. North Dakota 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.9% of North Dakota domains are at p=reject — the only DMARC policy that actually instructs receivers to drop spoofed mail.

Microsoft 365 surface. Microsoft 365 mailflow adoption is heavier than the national distribution, which is consequential — every M365 tenant already includes the controls needed to enforce DMARC, so the 416 M365 carriers in North Dakota with DMARC disabled are leaving paid-for protection switched off. That share is 20.4% of all North Dakota 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 Dakota runs at 5.6% (vs 6.1% national) — meaningful for downstream DKIM and MTA-STS validation, but still a minority signal.

Risk-band shape. North Dakota's critical-band share is 4.8% versus 8.4% nationally, with the pressure shifting into the high band (22.9% of state carriers) where one or two control gaps still leave room for impersonation. 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 Dakota-based carriers, the operational exposure is the 77.6%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 Dakota with other states

States closest in carrier-count rank to North Dakota. 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.