Skip to main content

By State / California

California Trucking Email Security

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

Edition: 2026-Q2State rank: #1Carriers: 36,967Domains: 31,421
By Stefan Efros, CEO & Founder, EFROS
Updated ·

No enforced DMARC

80.1%

national: 80.1%

p=reject

7.8%

national: 7.5%

Microsoft 365

36.3%

national: 38.1%

M365 + no DMARC (carriers)

9,245

national: 92,822

MTA-STS

3.5%

national: 3.3%

DNSSEC

6.4%

national: 6.1%

Dead domains

1,676

of 31,421 scanned

Total carriers

36,967

1,682 with dead domain

Risk bands — California carriers

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

Risk bandScore rangeCarriersDomains
Criticalscore 70+3,3412,814
Highscore 50–6910,7129,482
Mediumscore 30–4915,24912,638
Lowscore 15–295,6744,593
Minimalscore <15309218

California vs. national average

No enforced DMARC80.1%vs 80.1% national
p=reject adoption7.8%vs 7.5% national
MTA-STS3.5%vs 3.3% national
DNSSEC6.4%vs 6.1% national

What the California numbers actually mean

DMARC posture. California's share of carrier domains with no enforced DMARC sits at 80.1% within 0.0 points of the national average. enforced p=reject DMARC adoption is roughly in line with the national pool — meaning most California domains either have no DMARC at all or are stuck at the monitor-only p=none policy. At the protective end of the distribution, 7.8% of California 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 25.0% of all California 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.5%, materially below the threshold a freight payment-redirect attacker would have to clear to be inconvenienced by transport-layer policy. DNSSEC adoption in California runs at 6.4% (vs 6.1% national) — meaningful for downstream DKIM and MTA-STS validation, but still a minority signal.

Risk-band shape. 9.0% of California carriers sit in the critical risk band (score 70+) — above the national share of 8.4% — meaning a disproportionate cluster carries simultaneously broken SPF, missing or monitor-only DMARC, and no MTA-STS. 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 California-based carriers, the operational exposure is the 80.1%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 California with other states

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