By State / Kansas
Kansas Trucking Email Security
75.6% of active carrier domains in Kansas have no enforced DMARC. That leaves freight operators open to email impersonation, payment-redirect fraud, and cargo theft via phishing.
No enforced DMARC
75.6%
national: 80.1%
p=reject
10.9%
national: 7.5%
Microsoft 365
40.8%
national: 38.1%
M365 + no DMARC (carriers)
1,093
national: 92,822
MTA-STS
3.9%
national: 3.3%
DNSSEC
5.6%
national: 6.1%
Dead domains
227
of 3,748 scanned
Total carriers
4,768
227 with dead domain
Risk bands — Kansas 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+ | 350 | 302 |
| High | score 50–69 | 1,388 | 1,017 |
| Medium | score 30–49 | 1,878 | 1,493 |
| Low | score 15–29 | 885 | 679 |
| Minimal | score <15 | 40 | 30 |
Kansas vs. national average
What the Kansas numbers actually mean
DMARC posture. Kansas's share of carrier domains with no enforced DMARC sits at 75.6%, better than the national average by 4.5 points. Kansas carriers adopt the enforced p=reject DMARC policy at a meaningfully higher rate than the national pool. At the protective end of the distribution, 10.9% of Kansas 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. Every M365 tenant already includes the controls needed to enforce DMARC, so the 1,093 M365 carriers in Kansas with DMARC disabled are leaving paid-for protection switched off. That share is 22.9% of all Kansas 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.9%, materially below the threshold a freight payment-redirect attacker would have to clear to be inconvenienced by transport-layer policy. DNSSEC adoption in Kansas runs at 5.6% (vs 6.1% national), which matters for downstream DKIM and MTA-STS validation but is still a minority signal.
Risk-band shape. Kansas's critical-band share is 7.3% versus 8.4% nationally, with the pressure shifting into the high band (29.1% 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 Kansas-based carriers, the operational exposure is the 75.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 Kansas with other states
States closest in carrier-count rank to Kansas. 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.