Agent view · Guides · 2026-10-02
security.txt (RFC 9116): fields, location and expiry rule
This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/guides/security-txt-rfc-9116-fields-expiry-and-where-to-serve-it: fetched when you opened this page, shown byte for byte. An assistant, a crawler that negotiates markdown, or anything reading our feed gets exactly this. The markdown leaves signed (RFC 9421, key in our key directory), so a crawler can prove the page it read is the page this server sent; the check is shown below.
| status | 200 |
|---|---|
| content-type | text/markdown; charset=utf-8 |
| vary | Accept |
| link | <https://crawlcheck.io/llms.txt>; rel="describedby"; type="text/plain", <https://crawlcheck.io/.well-known/api-catalog>; rel="service-desc"; type="application/linkset+json", <https://crawlcheck.io/guides/security-txt-rfc-9116-fields-expiry-and-where-to-serve-it>; rel="cite-as", <https://crawlcheck.io/.well-known/http-message-signatures-directory>; rel="http-message-signatures-directory" |
| cache-control | public, max-age=900, stale-while-revalidate=2400 |
| bytes | 14,298 |
| words | 2,008 |
| sha-256 | 53223c5ce9858e2ff210ce60adfb5e7d4681a36ede5d5cb5938c1e2802cd3ce7 |
| repr-digest | sha-256=:UyI8XOmFji/yEM5grftefUaBo27eXVy1k4weKALNPOc=: ← matches the body shown |
| signature-input | sig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795311496;expires=1795315096;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="Oj2aSduzwJ_RaY-JrhJkSA";tag="crawlcheck-page" |
| signature | sig1=:1aST5dWnV7FoCYodAlasZYtRf6Xnw5bE8hapQyITo763Qu8ZinNqmtKAY4XyMYFREKZkjZGia+pZaREmjCIUAw==: |
| verified | yes — signature by key 1hHmE3fo1rg5Ig70… from https://crawlcheck.io/.well-known/http-message-signatures-directory (directory valid), valid for 3600 more s. Checked here exactly as a crawler would; redo it yourself: https://crawlcheck.io/api/tool/wba |
Guides · 2026-10-02 · By [VSNARY | Emmanuel Orta](/author) · 2 views # security.txt (RFC 9116): fields, location and expiry rule security.txt tells someone who found a vulnerability where to report it. RFC 9116 requires two fields and one location. What goes in the file, the expiry rule most files break within a year, and how to check yours from outside. security.txt, standardised in RFC 9116 in April 2022, is a plain-text file at /.well-known/security.txt that tells security researchers how to report a vulnerability. It must be served over HTTPS as text/plain and must contain at least one Contact field and exactly one Expires field; the RFC recommends Expires be less than a year in the future. Optional fields are Encryption, Acknowledgments, Preferred-Languages, Canonical, Policy and Hiring. The file may be OpenPGP-signed. An expired file should be treated as stale, so the most common failure is a correct file that nobody renewed. Check your own site free Check my site About a minute. First scan free with your email, nothing installed. On this page - Where the file goes - The fields - The expiry rule - Making the contact work - Checking it from outside - Writing a disclosure policy to link from it - Common mistakes - What it does not do When someone finds a security problem on a website, the hardest part of reporting it is often finding who to tell. Generic contact forms go to sales, social accounts go unread, and the report stalls. `security.txt` fixes that with a small file in a fixed location that names the right contact. It costs minutes to publish and is one of the few security measures a site can show to anyone who checks. ## Where the file goes # The [canonical](/glossary/canonical) location is `/.well-known/security.txt`, served over HTTPS with `Content-Type: text/plain; charset=utf-8`. The RFC also allows a copy at the top-level path `/security.txt` for older tools, typically as a redirect to the well-known location. Each host needs its own file or a redirect to the one that applies, because a researcher who finds a problem on `shop.example.com` will look there first. Serving the file as HTML, or behind a bot challenge that answers with status 200, makes it unreadable to the tools that check for it. ## The fields # | Field | Required | What it says | | --- | --- | --- | | `Contact` | yes, one or more | a `mailto:`, `https:` or `tel:` [URI](/glossary/uri) to report to, in order of preference | | `Expires` | yes, exactly once | date and time after which the file should be considered stale, in ISO 8601 form | | `Encryption` | no | where to find a key for encrypting the report | | `Acknowledgments` | no | a page thanking past reporters | | `Preferred-Languages` | no | languages the team reads, as language tags | | `Canonical` | no | the URI or URIs where this file is meant to live; important when the file is signed | | `Policy` | no | the disclosure policy: scope, safe harbour, what to expect after reporting | | `Hiring` | no | security job openings | Lines starting with `#` are comments. Field names are case-insensitive. The whole file can be wrapped in an OpenPGP cleartext signature, in which case a `Canonical` field is what stops a valid signed file from being copied to another site and passed off as that site's. ## The expiry rule # `Expires` is required precisely so that abandoned files stop being trusted. The RFC recommends a value less than a year ahead. The consequence is that every [security.txt](/glossary/security-txt) needs renewing on a schedule, and a file published once and forgotten becomes formally stale within a year. That is the most common defect in practice: correct contact, correct location, expired date. Put the renewal in the same calendar as certificate and domain renewals, or generate the file from code with a rolling expiry. Ours reads: ``` Contact: mailto:hello@crawlcheck.io Expires: 2027-09-24T00:00:00.000Z Preferred-Languages: en Canonical: https://crawlcheck.io/.well-known/security.txt Policy: https://crawlcheck.io/security ``` ## Making the contact work # A security.txt is only as good as the inbox it points to. Use an address that a person reads, not a ticketing queue that auto-closes, and test it by sending a message from outside the organisation. We found the hard way that an alerting address on our own domain had no mailbox behind it for five days, which we wrote up in [five days of alerts to an address with no mailbox](/blog/five-days-of-our-alerts-went-to-an-address-with-no-mailbox). If the address is on your own domain, make sure the domain's mail authentication will not reject replies; the [DMARC](/glossary/dmarc) side of that is in [moving DMARC to quarantine](/guides/how-to-move-dmarc-from-none-to-quarantine-without-losing-mail). ## Checking it from outside # Request `https://yourdomain/.well-known/security.txt` from a network you do not control, with a plain client such as curl, and confirm four things: status 200, content type `text/plain`, a `Contact` line, and an `Expires` date in the future but less than a year away. Then check the top-level `/security.txt` path redirects to it or returns the same content, and repeat for each host you operate. Other signals anyone can read from outside include [HSTS](/glossary/hsts) and a [Content-Security-Policy](/glossary/content-security-policy); how to roll out the second without breaking pages is in [the CSP rollout guide](/guides/content-security-policy-rollout-report-only-to-enforced). ## Writing a disclosure policy to link from it # The `Policy` field points at a page explaining what happens after someone reports. It does not need to be long. State what is in scope, such as the main site and its subdomains, and what is out of scope, such as third-party services the site uses. Say how quickly you will acknowledge a report and roughly how quickly you aim to fix confirmed problems. Say that you will not pursue legal action against good-faith research that stays within the scope and avoids accessing other people's data, and ask reporters not to disclose publicly until a fix is in place or a stated period has passed. If you do not pay bounties, say so plainly; reporters prefer a clear no to silence. Keep the policy and the contact address consistent with what the business can actually do. A one-person business promising a 24-hour response it cannot meet loses trust faster than one promising a week and meeting it. ## Common mistakes # Beyond expiry, four mistakes recur: a `Contact` line with a bare email address instead of a `mailto:` URI; the file served as HTML by a CMS that routes unknown paths to a page template; a file present on the main domain but missing on the subdomain where the vulnerability was found; and an `Encryption` field pointing to a key that expired or was revoked. Each makes the file harder to use exactly when someone is trying to use it. ## What it does not do # security.txt does not protect anything by itself, and its presence is not evidence that a site is secure. It shortens the path from discovery to a report reaching someone who can act. For a small business that has never received a vulnerability report, that is still worth five minutes, because the alternative is a researcher giving up or posting publicly. CrawlCheck’s dataset when this page loaded: 582,334 sites measured. Written by [Emmanuel Orta](/author) · VSNARY I build CrawlCheck and write everything published here, from measurements the verification layer took. Where a post got something wrong, the correction stays in the post. [Every post, and where I got it wrong →](/author) · [Follow on LinkedIn →](https://www.linkedin.com/in/emmanuelorta) Share this finding: [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fsecurity-txt-rfc-9116-fields-expiry-and-where-to-serve-it%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fsecurity-txt-rfc-9116-fields-expiry-and-where-to-serve-it%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=security.txt%20(RFC%209116)%3A%20fields%2C%20location%20and%20expiry%20rule)[Email](mailto:?subject=security.txt%20(RFC%209116)%3A%20fields%2C%20location%20and%20expiry%20rule&body=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fsecurity-txt-rfc-9116-fields-expiry-and-where-to-serve-it)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta) ## Related findings [2026-09-08 OpenTimestamps proof says pending? Upgrade the receipt Our OpenTimestamps files said pending on all 26 sealed days though every day was anchored. Why a receipt is not a proof, and how t](/blog/our-proofs-said-pending-for-26-days)[2026-08-28 How to write an llms.txt and check it is actually served What goes in an llms.txt, which pages to list, whether generators help, and the fetch checks that prove crawlers get the file you](/guides/how-to-write-an-llms-txt-and-verify-it)[2026-09-08 Unquoted HTML attributes: why we said a viewport was missing Minified HTML with unquoted attributes read as having no viewport, canonical or description. All three were there. What was wrong](/blog/the-viewport-was-there-all-along) The main product Found this on your own site? **We fix it for $100.** Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after. [Fix it all — $100](https://buy.stripe.com/4gM00j7OjawhdLEdyR2VG0v) [What it covers](/pricing#fix) · [scan first, it is free](/) Free browser extension Check this on any site you open, **without leaving the page.** CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account. [Add to Chrome — free](https://chromewebstore.google.com/detail/plgjengobhbdmbgckiiaaflgiepdbcpi?utm_source=crawlcheck.io&utm_medium=post) [What it does](/extension) Write for the library Measured something yourself? **Submit an article.** Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published. [Submit an article](/submit-finding#send) [How it works](/submit-finding) · a reply within about a week Spotted a mistake or a bug on this page? [Report an error](/report-error?k=article). Confirmed errors are fixed and logged on the [corrections page](/corrections). ## Comments Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain ([how](/api/comment/signed)). Those appear at once, marked *verified*. Send for review Writing about this? [Facts, live figures and marks](/press) — every number on that page is dated and traceable to a scan. [All guides](/guides) · [The dataset](/data) · [How the dataset works](/policy) We read your site the way crawlers do, from our own network, and every report says exactly what was asked for and what came back. [Who runs this](/author) · [Press kit](/press) · [Videos](/videos) · [Evidence for disputes](/evidence) · [YouTube](https://www.youtube.com/@crawlcheck) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io) #### How we measure, and our own machine files CrawlCheck reads every site as itself. Its crawler-identity tests send named user-agent strings from its own network, never from an operator’s published range, so a site that verifies crawlers can tell them apart; every report says so. Results reflect what an anonymous non-browser client receives. [What we collect and how to opt out](/policy) · [how every report is timestamped](/proof) · [who runs this](/author) · [press kit](/press) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io). **Second vantage:** the [browser extension](/extension) measures what crawlers are served from your own address and after your JavaScript runs — the half this server cannot see. From 1.0.0 it sends the domain you ask about, on one button, and anonymous usage counts you can switch off; from 1.0.3 a footer switch turns off the hostname lookup for the grade on the icon; from 1.0.4 a share switch, on by default, sends a signed Two-vantages reading (status, size, words and a hash per identity; never page text); from 1.0.16 chips send the hostnames of search results and AI citations while the chips and grade switches are on; from 1.0.17 a readings switch, on by default, sends one signed page reading a day (numbers, the hostname and the page address with the query removed; never in incognito; at most 40 a day) and only while the share and grade switches are also on. Earlier versions send nothing. **Our own machine layer for the agentic web:** [llms.txt](/llms.txt) · [llms-full.txt](/llms-full.txt) · [agents.md](/agents.md) · [SKILL.md](/SKILL.md) · [entitymap.json](/entitymap.json) · [media kit](/.well-known/media-kit.json) · [MCP server card](/.well-known/mcp/server-card.json) · [API catalog](/.well-known/api-catalog) · [OpenAPI](/openapi.json) · [robots.txt](/robots.txt) · [sitemap.xml](/sitemap.xml) · [security.txt](/.well-known/security.txt) — every one named in robots.txt, which is exactly what we check for on yours. **Pages:** [Certificates](/certificates) · [Staple](/spec/staple) | **Registry:** [MCP: Operator](/registry/mcp/operator) · [MCP](/registry/mcp) · [AI policy](/registry/aipolicy) · [etisan.com](/registry/etisan.com) · [lab.crawlcheck.io](/registry/lab.crawlcheck.io) · [restyle.pl](/registry/restyle.pl) · [Places](/registry/places) · [peerpush.com](/registry/capabilities/peerpush.com) | **Datasets:** [Technologies: Hotjar](/datasets/technologies/hotjar) · [Technologies: Font awesome](/datasets/technologies/font-awesome) [Contact](/contact) · [Partnerships](/partnerships) · [Terms of service](/terms) · [Refund policy](/refunds) · [Trust center](/trust) · [Subprocessors](/subprocessors) · [Changelog](/changelog) · [Report an error](/report-error)
Same body as a file: /guides/security-txt-rfc-9116-fields-expiry-and-where-to-serve-it.md · as data: /feed.json · what we tell agents site-wide: /llms.txt, /agents.md. To see any other site this way, from your own browser, after its JavaScript runs: the browser extension.