By State / Oregon
Oregon Trucking Email Security
77.5% of active carrier domains in Oregon have no enforced DMARC — leaving freight operators open to email impersonation, payment-redirect fraud, and cargo theft via phishing.
No enforced DMARC
77.5%
national: 80.1%
p=reject
8.4%
national: 7.5%
Microsoft 365
37.1%
national: 38.1%
M365 + no DMARC (carriers)
1,252
national: 92,822
MTA-STS
4.0%
national: 3.3%
DNSSEC
4.6%
national: 6.1%
Dead domains
255
of 4,564 scanned
Total carriers
5,752
255 with dead domain
Risk bands — Oregon 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+ | 498 | 429 |
| High | score 50–69 | 1,773 | 1,309 |
| Medium | score 30–49 | 2,257 | 1,811 |
| Low | score 15–29 | 935 | 729 |
| Minimal | score <15 | 34 | 31 |
Oregon vs. national average
What the Oregon numbers actually mean
DMARC posture. Oregon's share of carrier domains with no enforced DMARC sits at 77.5% — better than the national average by 2.6 points. enforced p=reject DMARC adoption is roughly in line with the national pool — meaning most Oregon 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.4% of Oregon domains are at p=reject — the only DMARC policy that actually instructs receivers to drop spoofed mail.
Microsoft 365 surface. Microsoft 365 mailflow adoption tracks the national distribution closely, so the 1,252 M365 carriers in Oregon with DMARC disabled represent the same "paid-for-but-switched-off" pattern that drives the national headline. That share is 21.8% of all Oregon 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 4.0%, materially below the threshold a freight payment-redirect attacker would have to clear to be inconvenienced by transport-layer policy. DNSSEC adoption in Oregon runs at 4.6% (vs 6.1% national) — meaningful for downstream DKIM and MTA-STS validation, but still a minority signal.
Risk-band shape. Oregon's critical and high bands combine to 39.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 Oregon-based carriers, the operational exposure is the 77.5%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 Oregon with other states
States closest in carrier-count rank to Oregon. 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.