Skip to main content

By State / Indiana

Indiana Trucking Email Security

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

Edition: 2026-Q2State rank: #17Carriers: 9,012Domains: 7,439
By Stefan Efros, CEO & Founder, EFROS
Updated ·

No enforced DMARC

76.3%

national: 80.1%

p=reject

9.3%

national: 7.5%

Microsoft 365

40.0%

national: 38.1%

M365 + no DMARC (carriers)

2,195

national: 92,822

MTA-STS

3.8%

national: 3.3%

DNSSEC

5.7%

national: 6.1%

Dead domains

375

of 7,439 scanned

Total carriers

9,012

376 with dead domain

Risk bands — Indiana carriers

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

Risk bandScore rangeCarriersDomains
Criticalscore 70+698612
Highscore 50–692,5161,979
Mediumscore 30–493,6283,109
Lowscore 15–291,6931,297
Minimalscore <1510167

Indiana vs. national average

No enforced DMARC76.3%vs 80.1% national
p=reject adoption9.3%vs 7.5% national
MTA-STS3.8%vs 3.3% national
DNSSEC5.7%vs 6.1% national

What the Indiana numbers actually mean

DMARC posture. Indiana's share of carrier domains with no enforced DMARC sits at 76.3% better than the national average by 3.8 points. Indiana carriers adopt the enforced p=reject DMARC policy at a meaningfully higher rate than the national pool. At the protective end of the distribution, 9.3% of Indiana 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,195 M365 carriers in Indiana with DMARC disabled are leaving paid-for protection switched off. That share is 24.4% of all Indiana 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.8%, materially below the threshold a freight payment-redirect attacker would have to clear to be inconvenienced by transport-layer policy. DNSSEC adoption in Indiana runs at 5.7% (vs 6.1% national) — meaningful for downstream DKIM and MTA-STS validation, but still a minority signal.

Risk-band shape. Indiana's critical-band share is 7.7% versus 8.4% nationally, with the pressure shifting into the high band (27.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 Indiana-based carriers, the operational exposure is the 76.3%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 Indiana with other states

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