By State / Washington
Washington Trucking Email Security
78.0% of active carrier domains in Washington have no enforced DMARC — leaving freight operators open to email impersonation, payment-redirect fraud, and cargo theft via phishing.
No enforced DMARC
78.0%
national: 80.1%
p=reject
8.5%
national: 7.5%
Microsoft 365
41.3%
national: 38.1%
M365 + no DMARC (carriers)
2,989
national: 92,822
MTA-STS
4.4%
national: 3.3%
DNSSEC
5.2%
national: 6.1%
Dead domains
692
of 9,905 scanned
Total carriers
11,961
695 with dead domain
Risk bands — Washington 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+ | 1,048 | 939 |
| High | score 50–69 | 3,198 | 2,614 |
| Medium | score 30–49 | 4,900 | 3,980 |
| Low | score 15–29 | 2,014 | 1,595 |
| Minimal | score <15 | 106 | 85 |
Washington vs. national average
What the Washington numbers actually mean
DMARC posture. Washington's share of carrier domains with no enforced DMARC sits at 78.0% — better than the national average by 2.1 points. enforced p=reject DMARC adoption is roughly in line with the national pool — meaning most Washington domains either have no DMARC at all or are stuck at the monitor-only p=none policy. At the protective end of the distribution, 8.5% of Washington 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 2,989 M365 carriers in Washington with DMARC disabled are leaving paid-for protection switched off. That share is 25.0% of all Washington 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 — the encrypted-transport policy that prevents DNS-downgrade interception — runs above the national rate, but the absolute floor is still under 9%, well short of where freight payment flows should sit. DNSSEC adoption in Washington runs at 5.2% (vs 6.1% national) — meaningful for downstream DKIM and MTA-STS validation, but still a minority signal.
Risk-band shape. Washington's critical and high bands combine to 35.5% 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 Washington-based carriers, the operational exposure is the 78.0%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 Washington with other states
States closest in carrier-count rank to Washington. 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.