eucsoft

security.txt: every RFC 9116 field, shown in the files of 160 software vendors

A security.txt is a small text file at /.well-known/security.txt that tells a security researcher where to report a vulnerability. RFC 9116 defines it: two fields are required, a Contact and an Expires date, and seven more are optional. Below, each field is explained with lines from the 100 real files we read at the vendors in this registry, followed by whole files that pass every check, the files that have expired or lack a required field, and how these vendors compare with the wider web.

100of 160 publish a security.txt
32of those 100 lack a required field or have expired
6files past their own expiry date
47have no file at either path
52 no file · 34%32 file with a fault · 21%68 file with both required fields, in date · 45%

Where the file goes, and what it looks like

The file sits at /.well-known/security.txt on every host it covers, is served over HTTPS, and has the content type text/plain in UTF-8 (RFC 9116, section 3). It applies only to the host it was fetched from, not to subdomains or the parent domain. The older top-level /security.txt is kept for legacy compatibility; when both exist, the /.well-known/ file is the one that counts. Each line is a field, a comment starting with #, or blank, and a field is a name, a colon and a value. The smallest file the standard allows has two lines:

The two required fields, with example.com values in the form RFC 9116 uses
Contact: mailto:security@example.com
Expires: 2027-10-31T23:59:59Z

Of the 100 files we read, 94 were at /.well-known/. Bitwarden, Datadog, Drata, Notion, Piwik PRO and Wix serve the file only at the top-level path on the host we read. Wire serves it with a character set other than UTF-8. 7 files contain lines that are neither a field, a comment nor blank, which a tool following the standard cannot read:

Field by field

Field names are case-insensitive, a field may appear more than once unless its definition says otherwise, and a reader must ignore any field it does not know (section 2.4). Across the 100 files:

Contact (required)

How to report a vulnerability: an email address, a phone number or a web page. The value must be a URI, so an email address is written mailto: and a phone number tel:, and a web address must start with https://. A file may list several, in order of preference, the first being the preferred one. 97 of the 100 files have one; 30 list more than one.

Adobe, Airtable, Databricks, Grammarly, IONOS Cloud, Infomaniak, JetBrains, OVHcloud, STRATO, Sentry and Smartsheet write at least one address without the mailto: scheme, or with a space after it, so a tool that follows the standard may not recognise it. 78 of the 100 files with a security.txt link a disclosure policy; of the 96 with a contact, 40 give only email, 32 only a web page or form, and 24 both. When the contact is email, the standard recommends an encryption key as well.

Expires (required)

The date and time after which the file should be treated as stale, in the RFC 3339 format (2027-10-31T23:59:59Z). It must appear exactly once, and the standard recommends a date less than a year ahead. It exists so that a forgotten file with a dead mailbox stops being trusted. 76 of the 100 files have one.

24 files have no Expires at all, 6 had passed it on the day we read them, and 26 of the 68 in date set it more than a year ahead. All three are listed further down.

Encryption

Where to get the key a researcher should use to encrypt a report. The key itself must not be in the field: the value is a URI pointing to it. 42 of the 100 files have one.

27 files give an email contact and no Encryption field.

Policy

A link to the vulnerability disclosure policy: what a researcher may test, how to report, and what the organisation commits to in return. The standard also points here for the scope of the file. 78 of the 100 files have one.

Canva, Microsoft, Okta, Retool, WhatsApp Business and Wire list more than one policy.

Canonical

The address or addresses where this file is meant to be found. If a file fetched from one address lists only others, the standard says its contents should not be trusted. 53 of the 100 files have one, and 6 list several, such as Clay's 2.

Anthropic's file at www.anthropic.com lists only anthropic.com; Canva's file at www.canva.com lists only canva.com; CleverReach's file at www.cleverreach.com lists only cleverreach.com.

Preferred-Languages

The languages a report may be written in, as language tags separated by commas, with no order of priority. It may appear only once; without it, a researcher may assume English. 68 of the 100 files have one, and 58 of those give en alone. The others:

Adobe en, ro, hi; Bitwarden en, de; CleverReach en,de; DATEV de, en; Infomaniak fr, en; Lusha en, he; Scaleway en, fr; Spendesk en, fr; TeamViewer en, de; Wire en, de.

Acknowledgments

A link to a page thanking researchers who reported vulnerabilities. 30 of the 100 files have one.

Grammarly, OVHcloud, Slack, WordPress.com and Zoho spell the field Acknowledgements. The standard's name is Acknowledgments, and a reader must ignore a field it does not know, so the link is invisible to tools.

Hiring

A link to security job openings. 61 of the 100 files have one, e.g. Adobe Hiring: https://www.adobe.com/careers.html; Adyen Hiring: https://careers.adyen.com/vacancies?team=Security.

CSAF

Not part of RFC 9116: the OASIS CSAF 2.0 standard uses this field to point to a machine-readable feed of security advisories. One file has it: Microsoft CSAF: https://msrc.microsoft.com/csaf/provider-metadata.json.

Fields the standard does not define

A file may carry other fields, and a reader must ignore any it does not know. These appear in the files we read:

1Password Site: https://hackerone.com/1password; 1Password Signature: https://1Password.com/.well-known/security.txt.sig; Airtable Permission: none; Cursor Secondary-Contact: mailto:security-reports@cursor.com; Infomaniak BugBounty: https://yeswehack.com/programs/infomaniak-bug-bounty-progra…; OVHcloud Signature: https://www.ovh.com/.well-known/security.txt.sig; Scaleway Abuse: https://abuse.scaleway.com/; Spendesk Bug-Bounty: True; Spendesk Last-Update: 2026-10-28T21:26:02Z; Wix Article: https://support.wix.com/en/article/reporting-a-security-issue.

Signing the file

The standard recommends an OpenPGP cleartext signature around the whole file, with a Canonical field inside it so the signature also vouches for where the file lives (section 2.3). Verifying the key is left to the researcher. 15 of the 100 files are signed; we did not verify the signatures. Piwik PRO and Sentry sign without a Canonical field. 1Password and OVHcloud instead point to a separate signature file in a Signature field, which RFC 9116 does not define. Adobe opens as a signed message but has no signature block, and is not counted as signed.

Whole files that pass every check

Three real files, quoted exactly as we stored them. They were picked by rule, not by hand: every check on this page passes, the expiry date is under a year ahead, and the file names its canonical location, a disclosure policy and the languages reports can be written in. The rule takes the two shortest such files and the shortest signed one. 21 of the 100 files meet it.

Mistral AI, mistral.ai/.well-known/security.txt, read 2026-10-17
Contact: mailto:security@mistral.ai
Expires: 2027-05-05T23:59:59.000Z
Policy: https://hackerone.com/58acc269-165e-4d18-a2d8-61f296cdea60/embedded_submissions/new
Preferred-Languages: EN
Canonical: https://mistral.ai/.well-known/security.txt
Kahoot!, kahoot.com/.well-known/security.txt, read 2026-11-09
Contact: mailto:security@kahoot.com
Expires: 2027-10-02T16:01:01.000Z
Encryption: https://kahoot.com/security_public_key.txt
Preferred-Languages: en
Canonical: https://kahoot.com/.well-known/security.txt
Policy: https://kahoot.com/disclosure-policy.txt
Zendesk, www.zendesk.com/.well-known/security.txt, read 2026-10-17, OpenPGP-signed (signature not verified by us)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

# Zendesk - Vulnerability Disclosure
Contact: https://www.zendesk.com/company/policies-and-guidelines/responsible-disclosure-policy/
# Bug Bounty Program
Contact: https://bugcrowd.com/engagements/zendesk
Contact: mailto:security@zendesk.com
Encryption: https://www.zendesk.com/.well-known/zendesk-psirt-public.asc
Policy: https://www.zendesk.com/company/policies-and-guidelines/responsible-disclosure-policy/
Preferred-Languages: en
Canonical: https://www.zendesk.com/.well-known/security.txt
Hiring: https://www.zendesk.com/company/careers/
Expires: 2027-04-16T00:00:00.000Z
-----BEGIN PGP SIGNATURE-----

iKcEARYKAE8WIQQWbtRbS6npPD9gMI0FwFA9Ed6GuQUCafKWYRsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMiwwLDMVHHNlY3VyaXR5QHplbmRlc2suY29tAAoJEAXAUD0R
3oa5YQkBAKmuLoE5SFOI1QQCXSb15DEu1zppejeoxDlo44exlO0xAPsFdUMpR4cN
HHh5xv/cbw/C5sgGakzMTv3GoHomDtOlAA==
=HUvi
-----END PGP SIGNATURE-----

Expired files

These files were past their own Expires date on the day we read them:

VendorExpires, as writtenRead onFile
Adyen2025-12-31T22:59:00.000Z2026-10-17www.adyen.com
CleverReach2024-12-31T22:59:00.000Z2026-10-25www.cleverreach.com
Element2025-01-30T23:00:00.000Z2026-10-17element.io
Mentimeter2026-10-02T12:00:00.000Z2026-11-09www.mentimeter.com
Microsoft2026-09-23T16:00:00.000Z2026-10-17www.microsoft.com
Smartsheet2026-07-01T04:00:00.000Z2026-11-09www.smartsheet.com

An expired file is usually forgotten rather than abandoned: the contact in it may well still work. Amazon Web Services' file had expired on 24 September 2026 when we first read it on 11 October, and had been renewed by our next reading on 17 October.

Missing a required field

24 files have no Expires field at all and 4 have no Contact field, the line the file exists to carry. 1 has an Expires that is not a date in the format the standard requires (RFC 3339).

VendorWhat RFC 9116 requires and the file lacksFile
1Passwordno Expires field1password.com
Aircallno Contact field; no Expires fieldaircall.io
Airtableno Expires fieldairtable.com
Canvano Expires fieldwww.canva.com
Cloudflareno Expires fieldwww.cloudflare.com
Cursorno Expires fieldcursor.com
Databricksno Expires fieldwww.databricks.com
Dropboxno Contact field; no Expires fieldwww.dropbox.com
Freshworksno Expires fieldwww.freshworks.com
Grammarlyno Expires fieldwww.grammarly.com
HubSpotExpires not a date: 2034-06-01:00:00.000Zwww.hubspot.com
Infomaniakno Expires fieldwww.infomaniak.com
JetBrainsno Expires fieldwww.jetbrains.com
Mailchimpno Expires fieldmailchimp.com
New Relicno Expires fieldnewrelic.com
OVHcloudno Expires fieldwww.ovhcloud.com
OpenAIno Expires fieldopenai.com
PayPalno Expires fieldwww.paypal.com
Sentryno Expires fieldsentry.io
Shopifyno Expires fieldwww.shopify.com
Slackno Expires fieldslack.com
Supabaseno Expires fieldsupabase.com
Vimeono Expires fieldvimeo.com
Webflowno Contact fieldwebflow.com
Wixno Expires fieldwww.wix.com
WordPress.comno Expires fieldwordpress.com

Expiry dates years ahead

The standard recommends an Expires less than a year away, so that someone looks at the file again. 26 of the 68 files in date set it further out, measured from the day we read them. This is a recommendation, not a requirement, and none of these is counted as a fault above.

VendorExpires, as writtenYears ahead
Drata2034-02-28T07:00:00.000Z7.3
Google Analytics2030-04-01T00:00:00z3.5
Google Cloud2030-04-01T00:00:00z3.5
Google Workspace2030-04-01T00:00:00z3.5
Notion2030-01-01T07:00:00.000Z3.2
Docker2030-01-01T05:00:00.000Z3.2
Datadog2029-12-31T23:00:00.000Z3.2
Zoom2029-12-31T00:00:00.000Z3.2
STACKIT2029-12-07T22:59:00.000Z3.1
Discord2029-08-12T13:37:00.000Z2.8
Intercom2029-03-15T00:00:00z2.4
Amplitude2028-12-31T23:59:00Z2.2
Scaleway2028-12-31T09:45:00.000Z2.2
Zoho2028-06-30T23:59:59.000Z1.7
DigitalOcean2028-04-05T04:00:00.000Z1.5
CrowdStrike2028-04-01T04:00:00.000Z1.5
IONOS Cloud2028-02-11T23:30:00.000Z1.3
STRATO2028-02-10T11:00:00.000Z1.3
Contentsquare2028-01-31T21:59:00.000Z1.3
Squarespace2028-01-01T05:00:00.000Z1.2
Linear2027-12-31T23:59:00.000Z1.2
n8n2027-12-31T22:59:00.000Z1.2
Perplexity2027-12-31T00:00:00Z1.2
Piwik PRO2027-12-16T23:00:00.000Z1.2
Hetzner2027-11-11T13:14:00.000Z1.1
Figma2027-10-21T15:25:00.000Z1.0

Against the wider web

Surveys of the top million websites find security.txt on about one site in a hundred. Among the software companies businesses buy from, it is the norm. Our sample is 160 vendors, not a million domains, and the studies define "compliant" differently, so the comparison is made check by check:

Check160 vendors here (2026-11-09)Top 1M domains (Uriports, Jan 2025)
Publish a security.txt63%1.25%
Of those, no Expires field24%45%
Of those, already expired6%13%
Of those, signed15%11%

Wider-web figures: Uriports, "Follow-Up on Security.txt Adoption", January 2025. Earlier studies found 0.49% of the top million (Findlay and Abdou, 2022) and higher adoption among the most visited sites (Li et al., IMC 2021).

No file

47 vendors answer neither /.well-known/security.txt nor the older /security.txt on their main website. That does not mean they have no way to report a vulnerability: a vendor can publish one on an ordinary page, which this count does not look for. It means the standard place to look is empty:

ActiveCampaign, Apollo.io, Attio, Backblaze, Box, Brevo, Cisco Webex, Docusign, Doodle, Elastic Cloud, Gong, Grafana Labs, Klaviyo, KnowBe4, Langdock, Langfuse, Mailgun, Make, Mapbox, Miro, Mural, Netlify, Nextcloud, OneTrust, Optimizely, Oracle Cloud, Pennylane, Personio, Pipedrive, Pleo, Postmark (ActiveCampaign), Rippling, S3NS, Salesforce, Sinch, SiteGround, SurveyMonkey, T Cloud Public, Typeform, Usercentrics, WeTransfer, Workday, Xero, Zapier, ZoomInfo, Zscaler, monday.com.

3DS Outscale, Matomo Cloud, Telegram, Twilio, Vonage answer the path with a web page instead of a text file, which a tool reading security.txt cannot use. MongoDB and SAP disallow the path in their robots.txt, so we did not read it and say nothing about whether a file is there.

Download the data (CSV): every row with its source and the date it was read.Cite as: eucsoft, “security.txt at SaaS vendors”, https://eucsoft.com/en/findings/security-txt/, data read up to 2026-11-09.

Questions

Where does a security.txt file go?

At /.well-known/security.txt on each host it covers, served over HTTPS as text/plain in UTF-8 (RFC 9116, section 3). The older top-level /security.txt is allowed for legacy compatibility only, and when both exist the /.well-known/ file wins. A file applies only to the host it was fetched from, not to subdomains or the parent domain. Of the 100 vendor files read here, 94 were found at /.well-known/.

Which fields are required in security.txt?

Two: Contact, which can appear several times, and Expires, exactly once. Everything else is optional. Of the 100 vendors here that publish a file, 24 have no Expires field and 4 no Contact field.

How far ahead should Expires be?

RFC 9116 recommends less than a year, so that someone looks at the file again; it does not set a limit. Of the 68 vendor files here that are in date, 26 set Expires more than a year from the day we read them, and 6 had already passed it.

Does security.txt have to be signed?

No. An OpenPGP cleartext signature is recommended, not required, and the standard recommends a Canonical field alongside it so the signature also covers the file's address. 15 of the 100 vendor files here are signed.

How this was read

Each file was fetched from the vendor's main website, on the homepage's host and then on the bare domain, and parsed field by field without a model; values are kept as written. The latest readings are from 2026-11-09, and the files are read again every week, so a vendor that renews its file drops off the expired list at the next reading. Products of one company that share a website share its file, so Google's three products count three times. 6 vendors have not been read yet. The full method is on the methodology page.

No verdicts. A missing or stale security.txt is a fact about one file, not a measure of how a vendor handles security. It does make a report slower to route, which is the problem the standard was written to fix.