Uptime Report Research · Bank email security census

Bank DMARC Adoption: 55% of the Smallest US Banks Enforce It, vs 100% of the Largest

Bank DMARC adoption is lower than the big-bank studies suggest. As of November 11, 2026, we checked the public DNS of 4,118 FDIC-insured institutions: 72% enforce DMARC with quarantine or reject, 44% use p=reject, and 9% have no valid record. Banks under $100 million enforce at 55%; banks over $100 billion at 100%.

Key findings

  1. 72% of 4,118 FDIC-insured banks enforce DMARC (quarantine or reject) on the domain they list as their website, and 44% use the strictest setting, p=reject.
  2. Enforcement rises with size: 55% of banks under $100 million enforce, against 100% of the 31 banks with $100 billion or more in assets.
  3. 9% of banks (386) publish no valid DMARC record at all, which Gmail requires of anyone sending 5,000 or more messages a day to personal Gmail accounts.
  4. FDIC-designated community banks enforce at 71%, against 82% for all other insured institutions.
  5. Of banks that receive mail, 40% point their MX record straight at Microsoft 365 and 46% route it through a filtering gateway such as Proofpoint or Barracuda; Google Workspace handles 1.0%.
  6. Only 75 banks (1.8%) publish a BIMI record backed by a mark certificate, the setup that shows a verified logo in Gmail.
  7. Among the 28 states with at least 50 banks, enforcement runs from 48% in Georgia to 85% in Nebraska.

Share enforcing DMARC, by total assets

Under $100M (486 banks)55%
$100M to $1B (2,604 banks)72%
$1B to $10B (875 banks)81%
$10B to $100B (122 banks)80%
$100B and up (31 banks)100%

FDIC BankFind Suite, assets as of June 30, 2026. DNS checked November 11, 2026. Free to cite and republish with a link.

The asset-size gradient

The bank DMARC studies in the current top search results sample the biggest names: dmarcian’s top 100 global banks by revenue, and a 25-bank category in DMARCdrift’s monthly scan, which reports 92% of those at p=reject. That sample is the top of a staircase. Across the full list of 4,118 insured institutions, enforcement climbs from 55% to 81% across the three bands below $10 billion, holds at 80% from $10 billion to $100 billion, and reaches 100% above that: a gap of 45 percentage points from bottom to top.

p=rejectp=quarantinep=none (monitor only)No valid DMARC recordUnder $100M486 banksUnder $100M: p=reject 144 of 486 (29.6%)30%Under $100M: p=quarantine 123 of 486 (25.3%)25%Under $100M: p=none (monitor only) 115 of 486 (23.7%)24%Under $100M: No valid DMARC record 104 of 486 (21.4%)21%55%enforce$100M to $1B2,604 banks$100M to $1B: p=reject 1,098 of 2,604 (42.2%)42%$100M to $1B: p=quarantine 776 of 2,604 (29.8%)30%$100M to $1B: p=none (monitor only) 482 of 2,604 (18.5%)19%$100M to $1B: No valid DMARC record 248 of 2,604 (9.5%)10%72%enforce$1B to $10B875 banks$1B to $10B: p=reject 475 of 875 (54.3%)54%$1B to $10B: p=quarantine 237 of 875 (27.1%)27%$1B to $10B: p=none (monitor only) 132 of 875 (15.1%)15%$1B to $10B: No valid DMARC record 31 of 875 (3.5%)81%enforce$10B to $100B122 banks$10B to $100B: p=reject 74 of 122 (60.7%)61%$10B to $100B: p=quarantine 24 of 122 (19.7%)20%$10B to $100B: p=none (monitor only) 21 of 122 (17.2%)17%$10B to $100B: No valid DMARC record 3 of 122 (2.5%)80%enforce$100B and up31 banks$100B and up: p=reject 30 of 31 (96.8%)97%$100B and up: p=quarantine 1 of 31 (3.2%)100%enforceShare of institutions in each band by DMARC policy on their website domain. Enforce = quarantine or reject.

The smallest band is where missing records cluster: 21% of banks under $100 million publish no valid DMARC record, against 0% of banks at $100 billion and up. Monitoring-only p=none, which collects reports but asks receivers to take no action on mail that fails, covers 24% of the smallest band and 0% of the largest.

Segment Banks Any DMARC p=none p=quarantine p=reject Enforcing rua reports SPF -all Logo (VMC/CMC) DNSSEC
Under $100M 486 79% 24% 25% 30% 55% 59% 63% 0.2% 12%
$100M to $1B 2,604 90% 19% 30% 42% 72% 76% 62% 0.3% 27%
$1B to $10B 875 96% 15% 27% 54% 81% 89% 52% 3.8% 35%
$10B to $100B 122 98% 17% 20% 61% 80% 97% 43% 15.6% 34%
$100B and up 31 100% 0% 3% 97% 100% 100% 61% 41.9% 19%
Community banks (FDIC flag) 3,715 90% 19% 29% 42% 71% 76% 61% 0.7% 27%
Not community banks 403 96% 14% 19% 64% 82% 91% 45% 11.9% 29%
All banks 4,118 91% 18% 28% 44% 72% 78% 59% 1.8% 27%

Share of institutions in each row. Any DMARC = a single valid v=DMARC1 record with p=none, quarantine or reject. Logo = BIMI record with an a= certificate URL. DNSSEC = DS record present for the domain at the parent zone.

Small banks versus large banks, control by control

Splitting at $10 billion in assets (3,965 banks below, 153 at or above), the gap is widest for the controls that take sustained work: p=reject (43% vs 68%), requesting aggregate reports (77% vs 97%) and a verified inbox logo (1.1% vs 21%). It disappears or reverses for the rest. Nearly every bank publishes SPF, smaller banks end it in the strict -all more often (60% vs 46%), and DNSSEC signing is close to even (27% vs 31%).

Under $10B (3,965 banks)$10B and up (153 banks)0%20%40%60%80%100%SPF record publishedSPF record published: 97.7% of banks under $10BSPF record published: 99.3% of banks with $10B or more98 vs 99SPF ends in -all (hard fail)SPF ends in -all (hard fail): 59.7% of banks under $10BSPF ends in -all (hard fail): 46.4% of banks with $10B or more60 vs 46Any DMARC recordAny DMARC record: 90.3% of banks under $10BAny DMARC record: 98.0% of banks with $10B or more90 vs 98DMARC reports requested (rua)DMARC reports requested (rua): 76.9% of banks under $10BDMARC reports requested (rua): 97.4% of banks with $10B or more77 vs 97DMARC enforced (quarantine or reject)DMARC enforced (quarantine or reject): 72.0% of banks under $10BDMARC enforced (quarantine or reject): 84.3% of banks with $10B or more72 vs 84DMARC p=rejectDMARC p=reject: 43.3% of banks under $10BDMARC p=reject: 68.0% of banks with $10B or more43 vs 68DNSSEC-signed domain (DS record)DNSSEC-signed domain (DS record): 26.8% of banks under $10BDNSSEC-signed domain (DS record): 30.7% of banks with $10B or more27 vs 31BIMI recordBIMI record: 2.2% of banks under $10BBIMI record: 24.8% of banks with $10B or more2 vs 25BIMI with a mark certificateBIMI with a mark certificate: 1.1% of banks under $10BBIMI with a mark certificate: 20.9% of banks with $10B or more1 vs 21MTA-STS recordMTA-STS record: 2.1% of banks under $10BMTA-STS record: 2.6% of banks with $10B or more2 vs 3

MTA-STS, which tells sending servers to require TLS when delivering to the bank, is rare at every size: 2.6% of banks at $10 billion and up and 2.1% below. Google requires a Verified Mark Certificate or Common Mark Certificate, plus a DMARC policy of quarantine or reject, before Gmail shows a BIMI logo. Among the 15 largest institutions, those publishing p=reject plus a certificate-backed BIMI logo include JPMorgan Chase Bank, National Association; Bank of America, National Association; Wells Fargo Bank, National Association; Goldman Sachs Bank USA; Capital One, National Association; TD Bank, National Association.

Who runs bank email: Microsoft, gateways and the rest

Of the 4,118 banks, 3,968 have mail exchanger (MX) records on their website domain; the other 150 receive mail elsewhere or not at all, and are still counted in the DMARC figures because an unprotected domain can be spoofed whether or not it receives mail.

Bar: share of banks with mail (MX). Dot: share of that group enforcing DMARC0%25%50%75%100%Microsoft 365 (direct MX)1,568 banksMicrosoft 365 (direct MX): 1,568 of 3,968 banks with MX (39.5%)Microsoft 365 (direct MX): 75.8% enforce DMARC (quarantine or reject)76%Filtering gateway1,820 banksFiltering gateway: 1,820 of 3,968 banks with MX (45.9%)Filtering gateway: 73.1% enforce DMARC (quarantine or reject)73%Google Workspace (direct MX)39 banksGoogle Workspace (direct MX): 39 of 3,968 banks with MX (1.0%)Google Workspace (direct MX): 71.8% enforce DMARC (quarantine or reject)72%Own mail server91 banksOwn mail server: 91 of 3,968 banks with MX (2.3%)Own mail server: 51.6% enforce DMARC (quarantine or reject)52%Other host or provider450 banksOther host or provider: 450 of 3,968 banks with MX (11.3%)Other host or provider: 68.4% enforce DMARC (quarantine or reject)68%

40% of banks with MX records hand inbound mail straight to Microsoft 365. Another 46% put a filtering gateway in front, and in 81% of those the SPF record or autodiscover entry points to Microsoft 365 behind it, against 1.2% for Google. Adding Microsoft 365 behind gateways to direct Microsoft 365, 77% of banks with mail run on Microsoft. The inbound setup says little about DMARC: banks behind a gateway enforce at 73% and banks on direct Microsoft 365 at 76%, and within the $100 million to $1 billion band alone the figures are 72% and 76%. DMARC is a DNS record the bank publishes for mail sent under its own name, so putting a gateway in front of inbound mail does not set it.

Gateway in MX Banks Share of gateway banks Enforcing DMARC p=reject
Proofpoint 713 39% 72% 50%
Barracuda 352 19% 68% 42%
Mimecast 284 16% 79% 54%
OpenText (Zix / AppRiver) 281 15% 77% 45%
Cisco Secure Email 77 4% 82% 34%
SpamTitan 30 2% 50% 17%

The “other host or provider” group (450 banks) is fragmented: its most common MX domains are secureyourmail.com (109), USA.NET (96), emailservice.io (31), Intermedia (30).

Who reads the reports

78% of banks ask receivers to send aggregate DMARC reports (rua). 40% of those banks send the reports to an address on their own domain; the rest mostly use specialist report-processing services. The most common destinations, named as neutral market facts:

rua destination domain Banks Share of banks with rua
bank’s own domain 1,268 40%
dmarcian.com 258 8%
encirca.com 183 6%
bankonitusa.com 173 5%
proofpoint.com 155 5%
easydmarc.us 122 4%
vali.email 105 3%
dmarcanalyzer.com 100 3%

Bank DMARC adoption by state

Banks are assigned to the state of their headquarters in BankFind. Click a column to sort. States with fewer than 10 banks are marked with an asterisk on the map; read their percentages as a handful of institutions.

Alaska: 5 of 5 banks enforce DMARC (100%)AK100%*Maine: 19 of 22 banks enforce DMARC (86%)ME86%Vermont: 9 of 12 banks enforce DMARC (75%)VT75%New Hampshire: 14 of 16 banks enforce DMARC (88%)NH88%Washington: 14 of 27 banks enforce DMARC (52%)WA52%Idaho: 9 of 10 banks enforce DMARC (90%)ID90%Montana: 25 of 34 banks enforce DMARC (74%)MT74%North Dakota: 36 of 59 banks enforce DMARC (61%)ND61%Minnesota: 146 of 220 banks enforce DMARC (66%)MN66%Illinois: 215 of 307 banks enforce DMARC (70%)IL70%Wisconsin: 106 of 153 banks enforce DMARC (69%)WI69%Michigan: 57 of 70 banks enforce DMARC (81%)MI81%New York: 76 of 99 banks enforce DMARC (77%)NY77%Rhode Island: 5 of 5 banks enforce DMARC (100%)RI100%*Massachusetts: 71 of 89 banks enforce DMARC (80%)MA80%Oregon: 8 of 12 banks enforce DMARC (67%)OR67%Nevada: 12 of 13 banks enforce DMARC (92%)NV92%Wyoming: 15 of 24 banks enforce DMARC (62%)WY62%South Dakota: 39 of 54 banks enforce DMARC (72%)SD72%Iowa: 178 of 223 banks enforce DMARC (80%)IA80%Indiana: 67 of 87 banks enforce DMARC (77%)IN77%Ohio: 113 of 153 banks enforce DMARC (74%)OH74%Pennsylvania: 75 of 107 banks enforce DMARC (70%)PA70%New Jersey: 32 of 48 banks enforce DMARC (67%)NJ67%Connecticut: 21 of 25 banks enforce DMARC (84%)CT84%California: 87 of 113 banks enforce DMARC (77%)CA77%Utah: 32 of 42 banks enforce DMARC (76%)UT76%Colorado: 41 of 63 banks enforce DMARC (65%)CO65%Nebraska: 111 of 131 banks enforce DMARC (85%)NE85%Missouri: 132 of 189 banks enforce DMARC (70%)MO70%Kentucky: 77 of 118 banks enforce DMARC (65%)KY65%West Virginia: 28 of 38 banks enforce DMARC (74%)WV74%Virginia: 42 of 56 banks enforce DMARC (75%)VA75%Maryland: 21 of 26 banks enforce DMARC (81%)MD81%Delaware: 11 of 14 banks enforce DMARC (79%)DE79%Arizona: 8 of 12 banks enforce DMARC (67%)AZ67%New Mexico: 20 of 28 banks enforce DMARC (71%)NM71%Kansas: 125 of 181 banks enforce DMARC (69%)KS69%Arkansas: 63 of 77 banks enforce DMARC (82%)AR82%Tennessee: 71 of 108 banks enforce DMARC (66%)TN66%North Carolina: 21 of 36 banks enforce DMARC (58%)NC58%South Carolina: 28 of 42 banks enforce DMARC (67%)SC67%District Of Columbia: 4 of 4 banks enforce DMARC (100%)DC100%*Oklahoma: 131 of 165 banks enforce DMARC (79%)OK79%Louisiana: 57 of 103 banks enforce DMARC (55%)LA55%Mississippi: 34 of 56 banks enforce DMARC (61%)MS61%Alabama: 55 of 89 banks enforce DMARC (62%)AL62%Georgia: 57 of 120 banks enforce DMARC (48%)GA48%Hawaii: 3 of 6 banks enforce DMARC (50%)HI50%*Texas: 285 of 339 banks enforce DMARC (84%)TX84%Florida: 65 of 80 banks enforce DMARC (81%)FL81%Puerto Rico: 3 of 4 banks enforce DMARC (75%)PR75%*under 40%40 to 49%50 to 59%60 to 69%70 to 79%80% and up
State Banks Any DMARC Enforcing p=reject No valid record Microsoft 365 MX Gateway MX Median assets
Alabama 89 85% 62% 27% 15% 24% 62% $354M
Alaska 5 100% 100% 40% 0% 40% 40% $890M
Arizona 12 83% 67% 42% 17% 55% 27% $214M
Arkansas 77 94% 82% 40% 6% 47% 40% $517M
California 113 94% 77% 50% 6% 47% 41% $1,175M
Colorado 63 94% 65% 40% 6% 30% 45% $330M
Connecticut 25 92% 84% 44% 8% 67% 25% $1,255M
Delaware 14 100% 79% 64% 0% 29% 64% $745M
District Of Columbia 4 100% 100% 75% 0% 50% 25% $758M
Federated States Of Micronesia 1 100% 100% 100% 0% n/a n/a $278M
Florida 80 98% 81% 55% 2% 36% 55% $626M
Georgia 120 82% 48% 30% 18% 23% 68% $331M
Guam 2 50% 50% 0% 50% 50% 0% $1,714M
Hawaii 6 100% 50% 50% 0% 17% 67% $8,272M
Idaho 10 100% 90% 70% 0% 40% 60% $1,019M
Illinois 307 90% 70% 41% 10% 43% 40% $300M
Indiana 87 90% 77% 38% 10% 42% 45% $456M
Iowa 223 94% 80% 50% 6% 40% 44% $277M
Kansas 181 84% 69% 46% 16% 55% 21% $208M
Kentucky 118 86% 65% 20% 14% 51% 39% $304M
Louisiana 103 88% 55% 24% 12% 48% 45% $378M
Maine 22 100% 86% 59% 0% 50% 40% $1,634M
Maryland 26 92% 81% 46% 8% 32% 52% $808M
Massachusetts 89 92% 80% 47% 8% 26% 58% $1,082M
Michigan 70 93% 81% 56% 7% 41% 48% $470M
Minnesota 220 89% 66% 42% 11% 31% 58% $219M
Mississippi 56 79% 61% 38% 21% 34% 39% $456M
Missouri 189 92% 70% 42% 8% 30% 53% $333M
Montana 34 79% 74% 47% 21% 56% 25% $241M
Nebraska 131 93% 85% 42% 7% 42% 50% $257M
Nevada 13 92% 92% 77% 8% 58% 33% $446M
New Hampshire 16 100% 88% 69% 0% 47% 40% $695M
New Jersey 48 92% 67% 46% 8% 38% 40% $894M
New Mexico 28 93% 71% 50% 7% 32% 44% $441M
New York 99 90% 77% 34% 10% 47% 33% $1,025M
North Carolina 36 92% 58% 22% 8% 33% 61% $606M
North Dakota 59 88% 61% 39% 12% 35% 58% $293M
Ohio 153 90% 74% 50% 10% 42% 43% $286M
Oklahoma 165 95% 79% 62% 5% 22% 41% $303M
Oregon 12 92% 67% 50% 8% 45% 55% $745M
Pennsylvania 107 91% 70% 48% 9% 43% 46% $675M
Puerto Rico 4 100% 75% 75% 0% 75% 0% $15,633M
Rhode Island 5 100% 100% 60% 0% 60% 20% $3,153M
South Carolina 42 88% 67% 43% 12% 27% 68% $584M
South Dakota 54 83% 72% 35% 17% 58% 29% $327M
Tennessee 108 85% 66% 36% 15% 33% 57% $474M
Texas 339 95% 84% 53% 5% 49% 38% $437M
U.S. Virgin Islands 1 100% 100% 100% 0% 100% 0% $506M
Utah 42 93% 76% 57% 7% 30% 60% $2,787M
Vermont 12 92% 75% 33% 8% 33% 33% $608M
Virginia 56 98% 75% 48% 2% 43% 53% $1,036M
Washington 27 89% 52% 37% 11% 52% 33% $1,019M
West Virginia 38 89% 74% 42% 11% 50% 39% $348M
Wisconsin 153 92% 69% 50% 8% 26% 65% $404M
Wyoming 24 83% 62% 50% 17% 46% 46% $339M

Microsoft 365 MX and gateway MX are shares of the state’s banks that have MX records. Median assets in millions of dollars, June 30, 2026 reports.

By charter and regulator

Charter and primary regulator matter less than size. National banks (OCC) enforce at 74%, state member banks (Federal Reserve) at 76% and state nonmember banks (FDIC) at 72%. The lowest group is the 42 state savings and loan associations, at 57%.

Segment Banks Any DMARC p=none p=quarantine p=reject Enforcing rua reports SPF -all Logo (VMC/CMC) DNSSEC
National bank (OCC) [N] 650 91% 17% 28% 46% 74% 80% 55% 4.5% 24%
State member bank (Fed) [SM] 687 94% 18% 27% 48% 76% 83% 63% 1.7% 31%
State nonmember bank (FDIC) [NM] 2,325 90% 19% 29% 43% 72% 76% 60% 0.9% 27%
Savings bank (state) [SB] 194 89% 18% 28% 43% 71% 75% 59% 4.6% 25%
Savings institution (OCC) [SI] 220 88% 19% 28% 41% 69% 78% 48% 1.8% 30%
Savings and loan (state) [SL] 42 74% 17% 21% 36% 57% 57% 64% 0.0% 26%

What Gmail and Yahoo require, and how banks measure up

“Starting February 1, 2024, email senders who send more than 5,000 messages per day to Gmail accounts must meet the requirements in this section.” Among them: “Set up DMARC email authentication for your sending domain. Your DMARC enforcement policy can be set to none.” Google, Email sender guidelines.

Google’s sender FAQ adds that “Starting November 2025, Gmail is ramping up its enforcement on non-compliant traffic,” with “temporary and permanent rejections,” and that a domain counts as a bulk sender permanently once it crosses the threshold. The DNS-visible part of that floor is an SPF record plus any DMARC record: 90% of banks meet it on their website domain, and 77% of banks under $100 million. DKIM, the third requirement, cannot be checked from DNS without knowing each bank’s selector names, so it is not measured here. Yahoo publishes its own sender requirements on its Sender Hub; that page returned only a consent screen to our fetcher, so we quote Google alone.

Gmail’s floor is p=none. The stronger benchmark in US public policy is CISA’s Binding Operational Directive 18-01, issued October 16, 2017, which gave federal civilian agencies one year to set “a DMARC policy of ‘reject’ for all second-level domains and mail-sending hosts.” 44% of insured banks meet that standard today. We did not cite the FFIEC IT Examination Handbook: its site’s robots.txt disallows all automated access, and we did not find another primary bank-regulator document that names DMARC. The current DMARC specification is RFC 9989 (2026), which replaced RFC 7489 and dropped the pct tag that let senders apply a policy to only part of their mail.

What this means for MSPs and bank IT teams

If you support community banks, the opening is specific. Roughly 352 banks under $1 billion have no valid DMARC record and another 597 sit at p=none. Moving a bank from p=none to p=reject is mostly inventory work: list every service that sends as the bank’s domain (core banking notices, online banking alerts, loan origination, marketing platforms), get each one passing SPF or DKIM alignment, and read the rua reports for several weeks before each policy step. Point rua at a mailbox or service someone reads; 30% of p=none banks request no reports at all, which makes p=none pointless. For banks already at reject, the next DNS-level controls are DNSSEC (27% of smaller banks), MTA-STS with TLS reporting, and BIMI if the bank has a registered trademark. Our DMARC adoption statistics show how banks compare with the wider web, and the Microsoft 365 market share census covers the same mail-provider method across public companies and .gov domains. For the threat side, see phishing statistics from four primary sources.

Frequently asked questions

What percentage of banks use DMARC?

In our November 11, 2026 scan of 4,118 FDIC-insured institutions, 91% published a DMARC record on their website domain, 72% enforced it with quarantine or reject, and 44% used p=reject.

Do small banks have DMARC?

Most do, but fewer enforce it. Among 486 banks under $100 million in assets, 79% have a DMARC record and 55% enforce it. 21% have no valid record.

Do the largest US banks use DMARC p=reject?

14 of the 15 largest insured institutions by assets publish p=reject on their listed website domain, including JPMorgan Chase Bank, National Association; Bank of America, National Association; Citibank, National Association; Wells Fargo Bank, National Association; Goldman Sachs Bank USA.

Is DMARC required for banks?

We did not find a primary federal banking regulation that names DMARC. Gmail requires DMARC (at least p=none) from senders of 5,000 or more messages a day to personal Gmail accounts, a threshold a bank emailing its customers can reach. Federal civilian agencies have had to use p=reject since CISA’s Binding Operational Directive 18-01 in 2017.

What email provider do most banks use?

Microsoft. 40% of banks with mail records point their MX directly at Microsoft 365, and in the 46% that use a filtering gateway, SPF records name Microsoft 365 behind the gateway 81% of the time. Google Workspace receives mail directly for 1.0%.

How can a bank check its DMARC record?

Query the TXT record at _dmarc followed by the bank’s domain (for example with nslookup or dig). A record starting v=DMARC1 with p=reject or p=quarantine is enforced; p=none only monitors. 18% of banks in our scan were at p=none.

Download the data. us-bank-dmarc-adoption-by-asset-size-state-2026.csv (CSV). Licensed under CC BY 4.0: free to reuse with attribution to The Uptime Report.

Free to cite and republish with a link. The CSV holds aggregates by asset band, community bank flag, charter, state and mail setup; it contains no per-bank results.

Methodology

Population. Every active FDIC-insured institution in the FDIC BankFind Suite institutions API (4,212 records, financial data as of June 30, 2026, retrieved November 11, 2026). 70 records list no web address, 6 had a domain whose lookups did not complete, and 18 list a domain that no longer exists in DNS. That leaves 4,118 institutions on 4,086 distinct registered domains.

Domain. The registered domain of the WEBADDR field (for example www.examplebank.com becomes examplebank.com), using the Public Suffix List. A bank may send customer mail from a different domain; we measure the domain it lists as its website, which is the one customers see and attackers imitate.

Checks. Passive DNS lookups only, through Google Public DNS over HTTPS, at most 5 concurrent queries and 40 a second: MX; apex TXT (SPF); _dmarc TXT; default._bimi TXT; _mta-sts TXT; _smtp._tls TXT; DS; and, where MX is not Microsoft or Google, the SPF include chain (up to 8 lookups) and the autodiscover CNAME to infer the mailbox platform behind a gateway. No mail was sent, no web pages were requested, and nothing was probed. 1 domains were re-queried through Quad9 after resolver errors.

Definitions. Enforcing = exactly one DMARC record whose p tag is quarantine or reject. No valid record = no record, more than one record, or a missing or unknown p tag. Asset bands use BankFind total assets. Community bank = the FDIC’s CB flag. Mail provider = the provider of the lowest-preference MX hosts, classified by host name.

Limitations. DKIM is not measured. A p=reject record does not prove every sending service aligns. The pct tag is ignored when classifying; 79 enforcing banks set pct below 100. Holding companies with several charters can share one domain, so they appear once per charter.

Privacy. Results for individual banks are not published. Banks are named on this page only for positive facts (p=reject, verified logo) or as service providers.

Not advice. This is a measurement of public DNS records, not a security assessment of any institution.

Cite as:The Uptime Report. "Bank DMARC Adoption: 55% of the Smallest US Banks Enforce It, vs 100% of the Largest." November 2026. https://theuptimereport.com/bank-dmarc-adoption/

References

  1. FDIC BankFind Suite API, institutions endpoint. Accessed November 2026.
  2. Google, Email sender guidelines. Accessed November 2026.
  3. Google, Email sender guidelines FAQ. Accessed November 2026.
  4. Google, Set up BIMI. Accessed November 2026.
  5. CISA, Binding Operational Directive 18-01. Accessed November 2026.
  6. RFC 9989, Domain-Based Message Authentication, Reporting, and Conformance (DMARC). Accessed November 2026.
  7. dmarcian, DMARC Status of Top 100 Global Banks. Accessed November 2026.
  8. DMARCdrift, DMARC Adoption Across the Web. Accessed November 2026.
  9. Google Public DNS (DNS over HTTPS JSON API). Accessed November 2026.

Research library

More original data reports from The Uptime Report. Every report includes its methodology and a free CSV download. Browse all research

Threats and breaches

Infrastructure and uptime

Regulation and disclosure

Workforce and pay

MSP market and spending

Comments

One response to “Bank DMARC Adoption: 55% of the Smallest US Banks Enforce It, vs 100% of the Largest”

  1. […] Bank DMARC Adoption 2026DMARC at 4,118 US banks, by size […]

Leave a Reply

Your email address will not be published. Required fields are marked *