stackscan commited on
Commit
1972430
·
verified ·
1 Parent(s): 65f78f1

Add DMARC and SPF adoption data for 36,120 large organizations

Browse files

Collected August 2026. Population is organizations with 5,001 or more employees and resolvable company information, matching stackscan/lets-encrypt.

Files changed (2) hide show
  1. Email-Authentication.csv +0 -0
  2. README.md +217 -0
Email-Authentication.csv ADDED
The diff for this file is too large to render. See raw diff
 
README.md ADDED
@@ -0,0 +1,217 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ pretty_name: "DMARC and SPF Adoption Among Large Organizations"
3
+ license: cc-by-4.0
4
+ tags:
5
+ - cybersecurity
6
+ - email-security
7
+ - dmarc
8
+ - spf
9
+ - email-authentication
10
+ - technographics
11
+ - technology-adoption
12
+ - company-data
13
+ - phishing
14
+ - business
15
+ task_categories:
16
+ - tabular-classification
17
+ language:
18
+ - en
19
+ size_categories:
20
+ - 10K<n<100K
21
+ dataset_info:
22
+ features:
23
+ - name: Popularity Rank
24
+ dtype: int64
25
+ - name: Domain
26
+ dtype: string
27
+ - name: Company Name
28
+ dtype: string
29
+ - name: Company Size
30
+ dtype: string
31
+ - name: Year Founded
32
+ dtype: float64
33
+ - name: Industry
34
+ dtype: string
35
+ - name: LinkedIn URL
36
+ dtype: string
37
+ - name: Locality
38
+ dtype: string
39
+ - name: Country
40
+ dtype: string
41
+ - name: TLD
42
+ dtype: string
43
+ - name: Language
44
+ dtype: string
45
+ - name: Instagram
46
+ dtype: string
47
+ - name: Twitter
48
+ dtype: string
49
+ - name: YouTube
50
+ dtype: string
51
+ - name: TikTok
52
+ dtype: string
53
+ - name: SPF
54
+ dtype: string
55
+ - name: DMARC
56
+ dtype: string
57
+ - name: BIMI
58
+ dtype: string
59
+ - name: MTA-STS
60
+ dtype: string
61
+ - name: Posture
62
+ dtype: string
63
+ splits:
64
+ - name: train
65
+ num_examples: 36120
66
+ ---
67
+
68
+ # DMARC and SPF Adoption Among Large Organizations
69
+
70
+ ## Overview
71
+
72
+ This dataset records which of 36,120 large organizations publish SPF and DMARC records on their primary domain, with firmographic context for each: industry, employee band, country, locality, founding year and LinkedIn profile.
73
+
74
+ SPF lists the servers allowed to send mail for a domain. DMARC tells receiving servers what to do with mail that fails that check, and where to send reports. A domain with SPF but no DMARC has published the list without publishing an instruction, so receivers are left to decide for themselves.
75
+
76
+ Collected in August 2026. DNS records change, so treat the data as a snapshot of that month rather than a current state.
77
+
78
+ Full statistics are published at StackScan for [DMARC](https://www.stackscan.com/technology/dmarc) and [SPF](https://www.stackscan.com/technology/spf-sender-policy-framework).
79
+
80
+ ## SPF and DMARC Coverage
81
+
82
+ Of the 35,563 large organizations that publish SPF, **45.7% also publish DMARC**. The other 19,315 publish SPF alone.
83
+
84
+ | Posture | Organizations |
85
+ | ------- | ------------- |
86
+ | SPF only | 19,315 |
87
+ | SPF + DMARC | 16,248 |
88
+ | DMARC without SPF | 557 |
89
+
90
+ SPF is close to universal among organizations that send mail, so the SPF group serves as a denominator and the percentage above is a rate rather than a raw count.
91
+
92
+ ## Adoption by Country and Industry
93
+
94
+ DMARC adoption among SPF publishers, by country. Groups with fewer than 150 organizations are omitted.
95
+
96
+ | Country | Organizations | DMARC |
97
+ | ------- | ------------- | ----- |
98
+ | Sweden | 305 | 59.7% |
99
+ | Argentina | 219 | 56.6% |
100
+ | Denmark | 188 | 56.4% |
101
+ | Belgium | 305 | 53.4% |
102
+ | United Kingdom | 1,733 | 51.9% |
103
+ | Australia | 596 | 51.8% |
104
+ | South Korea | 199 | 34.2% |
105
+ | Vietnam | 268 | 34.3% |
106
+ | China | 1,456 | 30.2% |
107
+
108
+ By industry, same threshold:
109
+
110
+ | Industry | Organizations | DMARC |
111
+ | -------- | ------------- | ----- |
112
+ | defense & space | 168 | 56.5% |
113
+ | medical devices | 197 | 55.8% |
114
+ | banking | 650 | 55.5% |
115
+ | airlines/aviation | 252 | 54.0% |
116
+ | insurance | 638 | 53.4% |
117
+ | security and investigations | 318 | 35.5% |
118
+ | professional training & coaching | 150 | 28.7% |
119
+
120
+ Employee band makes little difference. Organizations with 5,001 to 10,000 employees reach 46.7%, and those with more than 10,000 reach 44.9%.
121
+
122
+ BIMI and MTA-STS are rare in this population. Across all 36,120 organizations, 17 publish BIMI and 5 publish MTA-STS.
123
+
124
+ ## Dataset Fields
125
+
126
+ `Email-Authentication.csv`, 36,120 rows, 20 columns. Coverage is the share of rows where the field is populated.
127
+
128
+ | Column | Type | Coverage | Description |
129
+ | ------ | ---- | -------- | ----------- |
130
+ | `Popularity Rank` | int64 | 95.1% | Website popularity rank, lower being more popular. Rows are stored in ascending rank order |
131
+ | `Domain` | string | 100% | Primary website domain. Unique across the file |
132
+ | `Company Name` | string | 100% | Organization name, lowercased |
133
+ | `Company Size` | string | 100% | Employee band. Two values: `5001-10000` and `10001+` |
134
+ | `Year Founded` | float64 | 71.2% | Founding year |
135
+ | `Industry` | string | 99.1% | Industry label, lowercased |
136
+ | `LinkedIn URL` | string | 100% | Organization LinkedIn profile path |
137
+ | `Locality` | string | 79.7% | City or region, where available |
138
+ | `Country` | string | 100% | Organization or website country |
139
+ | `TLD` | string | 100% | Top-level domain |
140
+ | `Language` | string | sparse | Detected site language |
141
+ | `Instagram` | string | sparse | Instagram handle |
142
+ | `Twitter` | string | sparse | Twitter handle |
143
+ | `YouTube` | string | sparse | YouTube channel |
144
+ | `TikTok` | string | sparse | TikTok handle |
145
+ | `SPF` | string | 100% | `yes` or `no` |
146
+ | `DMARC` | string | 100% | `yes` or `no` |
147
+ | `BIMI` | string | 100% | `yes` or `no` |
148
+ | `MTA-STS` | string | 100% | `yes` or `no` |
149
+ | `Posture` | string | 100% | `SPF only`, `SPF + DMARC` or `DMARC without SPF` |
150
+
151
+ The language and social columns are populated for fewer than 1% of rows.
152
+
153
+ ## Methodology
154
+
155
+ Domains were checked for published SPF, DMARC, BIMI and MTA-STS records in August 2026. An organization is included when at least one of SPF or DMARC was found on its primary domain.
156
+
157
+ The population is large organizations, meaning 5,001 or more employees, for which company information could be resolved.
158
+
159
+ ## Important Notes
160
+
161
+ * `DMARC` means a DMARC record was found. It does not mean the policy is enforced. A policy of `p=none` requests monitoring only and is common, and the policy value is not recorded here, so `DMARC = yes` should not be read as protection.
162
+ * DKIM is not included. Detecting a DKIM record requires knowing the DNS selector in advance, so any count would understate adoption by orders of magnitude.
163
+ * The 557 organizations with DMARC but no SPF are unusual and often misconfigured. DMARC relies on SPF or DKIM alignment, so a DMARC record with neither does little.
164
+ * Records are read from the primary domain only. Large organizations send from many domains and subdomains, and those are not covered.
165
+ * Rates are calculated against organizations publishing SPF, not against all large organizations.
166
+ * Results represent observations made in August 2026.
167
+
168
+ ## Use Cases
169
+
170
+ * Email security and anti-phishing research
171
+ * Benchmarking an organization or sector against its peers
172
+ * Public sector and regulatory policy analysis
173
+ * Journalism on email security preparedness
174
+ * Technographic and market research
175
+ * Data science and machine learning
176
+
177
+ ## Citation
178
+
179
+ If you use this dataset, please credit StackScan and link to the source page.
180
+
181
+ Plain text:
182
+
183
+ StackScan. (2026). *DMARC and SPF Adoption Among Large Organizations* (data collected August 2026) [Data set]. StackScan. https://www.stackscan.com/technology/dmarc
184
+
185
+ BibTeX:
186
+
187
+ ```bibtex
188
+ @misc{stackscan_email_authentication_2026,
189
+ author = {{StackScan}},
190
+ title = {DMARC and SPF Adoption Among Large Organizations},
191
+ year = {2026},
192
+ month = {aug},
193
+ publisher = {StackScan},
194
+ howpublished = {\url{https://www.stackscan.com/technology/dmarc}},
195
+ note = {Data collected August 2026. Dataset: \url{https://huggingface.co/datasets/stackscan/email-authentication}}
196
+ }
197
+ ```
198
+
199
+ ## Related
200
+
201
+ [stackscan/lets-encrypt](https://huggingface.co/datasets/stackscan/lets-encrypt) uses the same population definition and collection period, so the two can be joined on `Domain`.
202
+
203
+ ## Access to More Data
204
+
205
+ The files in this repository are CC BY 4.0 and free for anyone to use, including commercially. No request or permission is needed.
206
+
207
+ StackScan also provides free access to larger and custom datasets for data journalists, academic researchers, non-profits and other organizations working on non-commercial projects. Ask through [stackscan.com](https://www.stackscan.com/technology/dmarc).
208
+
209
+ ## License
210
+
211
+ Released under [Creative Commons Attribution 4.0 International (CC BY 4.0)](https://creativecommons.org/licenses/by/4.0/). You are free to share and adapt the data, including commercially, provided you give appropriate credit.
212
+
213
+ Attribution must name StackScan and link to the source page:
214
+
215
+ > Data from [StackScan](https://www.stackscan.com/technology/dmarc), licensed under CC BY 4.0.
216
+
217
+ For academic or published work, use the citation above.