Free security.txt Checker and Generator
Read both security.txt addresses of a site, check the file against RFC 9116, see the days left before it expires, then correct it in your browser and copy the result.
Last updated 15 November 2026
A security.txt file tells security researchers how to report a vulnerability to you, and this security.txt checker reads the one your site serves. Enter your site's address and our server requests the two addresses RFC 9116 names, /.well-known/security.txt and /security.txt, then shows what each answered: the final address, the status, the Content-Type and the text. The findings check the file against the RFC: the Contact and Expires fields it requires, whether each address begins with a URI scheme and has no white space, whether web addresses start with https://, how many days are left before the Expires date, and whether an OpenPGP signature wrapper is present. A comparison says which address has a file, whether the two hold the same text and which one the RFC says to use. An editor then opens with the file, and works as a security.txt generator when there is none: add a Contact line, set a new Expires date and copy the corrected text. Check only a site you own or have permission to check.
How to use this tool
- 1
Enter your site's address
Type your site's name in the Site address box, or paste an address from your browser. Only the name is used, and both requests are made over HTTPS.
- 2
Run the check
Press Check security.txt. Our server requests /.well-known/security.txt and then /security.txt, follows up to 5 redirects for each and reads at most 32,768 bytes of each response.
- 3
Read the comparison and the two cards
The comparison says which address has a file and whether the two hold the same text. Each card shows the final address, the status, the Content-Type, the findings marked Fix, Review, Note or Matches, and the text with line numbers. Matches means the tool found that the rule quoted in that line is met, and a list under the cards says what the tool does not check.
- 4
Correct the file in the editor
The editor opens with the file that was read, or a short template. Add a Contact line, choose a date and press Set Expires, or type in the text box. The date box starts 364 days after the current date in UTC. The findings under it follow your edits.
- 5
Copy, publish and check again
Copy the edited text, publish it at /.well-known/security.txt, then run the check again to read what your site now serves.
What a security.txt file is, where RFC 9116 puts it and how the tool reads it
RFC 9116, published by the IETF in April 2022 as an Informational document, defines security.txt as a machine-parsable format to help organisations describe their vulnerability disclosure practices. For web-based services, organisations MUST place the file under the /.well-known/ path. For legacy compatibility, the RFC says a file might be placed at the top-level path, or redirect from there to the file under /.well-known/. If a file is present in both locations, the one in the /.well-known/ path MUST be used. Section 3 also says file access MUST use the https scheme, and that the file MUST have a Content-Type of text/plain with the default charset parameter set to utf-8. The tool shows HTTPS as a match only when every request in the chain went to an address that starts with https://. For text/plain with no charset parameter the tool gives no result, because the RFC does not say outright whether it has to be written. Section 3.1 limits what a file covers: it MUST only apply to the domain or IP address in the URI used to retrieve it, not to any of its subdomains or parent domains. So a file on your main site does not apply to a subdomain as a domain, though section 3.1 adds that a file MAY also apply to products and services provided by the organisation publishing the file. The tool reads a file's lines as the grammar in section 4 writes them, and marks Fix where it finds a line that departs from it. It still reads some of those lines, including a field whose colon is followed by no space, a tab or, on a field the RFC defines, more than one space, when it knows the field's name or a space or tab follows the colon. It also reads the text after a byte order mark, a comment with a character outside the ranges section 2.1 lists, a last line with no line ending, and the text inside an incomplete signature wrapper. Any other line that is not a field, a comment or a blank line is listed as unread.
The fields the checker reads and the rules it applies
RFC 9116 section 2.5 defines eight fields. Contact MUST always be present. Its value MUST follow URI syntax, which the RFC says means the mailto and tel URI schemes must be used when specifying email addresses and telephone numbers, and a Contact that indicates a web URI MUST begin with https://. Expires MUST always be present and MUST NOT appear more than once. Its value has the date and time form RFC 3339 defines, like the example in the RFC, 2021-12-31T18:37:07z. RFC 3339 says the T and the Z may be lower case, so the tool accepts both, though it says applications that generate the format SHOULD use upper case letters, as the editor does. RFC 3339 section 5.7 allows 60 in the seconds only at the end of a month in which a leap second occurs, and makes 58 the highest value where one is subtracted. The tool cannot know those months: it accepts 60 only in the last minute of a month in UTC, never shows it as a match, and accepts 59 in any minute. For a field that takes a URI, the tool checks only that the value begins with a scheme name and a colon, has no white space, and begins with https:// when its scheme is http or https. The rest is not checked against RFC 3986's URI syntax, so any other character it does not allow, such as < or >, is not marked. Preferred-Languages MUST NOT appear more than once and lists language tags separated by commas. The tool checks no tag against RFC 5646, and reads whatever sits between two commas as one tag. On 15 November 2026, the IANA registry the RFC created listed two more names, CSAF and Bug-Bounty. The tool describes both from the registry, checks no CSAF value, notes a Bug-Bounty value other than the True or False the registry gives, and marks a second Bug-Bounty line for review, because the registry's Multiple Appearances column says no. For any other name it quotes section 2.4: researchers MUST ignore any fields they do not explicitly support.
What the check requests, and what it cannot tell you
When you press Check security.txt, our server looks up your site's name in DNS and refuses it if it points to a private or reserved network address. It sends one GET request to the /.well-known/security.txt address on port 443, then one to the /security.txt address. If an answer is a redirect, the next address is checked the same way before it is requested, up to 5 redirects for each of the two, and a redirect can lead to an http:// address on port 80. The server reads at most 32,768 bytes of a response and gives each address 5 seconds, within 12 seconds for the whole check. Your browser receives the addresses requested, each status code, the Content-Type value, the findings, and the text of a response that had status 200 and was valid UTF-8, when every request for that address went to the host name you entered or to the same name with or without "www." in front. No other response header is passed on. When a redirect for an address goes to a host name that is neither the one you entered nor the same name with or without "www." in front, our server stops reading that response, and any after it, at its headers. If the chain then ends in a response, the tool shows the redirects, the final address and that response's status code and Content-Type value, and does not read or check its body. The findings come from the whole text. On screen a file's text is cut at 16,384 characters and 500 lines, and the page says so. A 200 response with no security.txt field is not counted as a file, and only its first 1,024 characters are shown. RFC 9116 section 4 says the file MUST be encoded using UTF-8 in Net-Unicode form. The tool checks that the body is valid UTF-8 and does not check Net-Unicode form. The tool reads each address once, from our server, without signing in, and never opens an address written inside the file, so it cannot tell you whether a contact address works or who reads it. A request limit is counted in a shared store by the address your request comes from (one IPv4 address, or one IPv6 /64 block) over a one-minute window, and again for all visitors together. The check spends one slot for each address it is about to request, taken before it looks the name up in DNS: one for each of the two addresses and one for each redirect followed, even when the lookup then refuses the address or finds none, so a check can be refused when too many have run. A check that returns a result also sends one analytics event, which names the tool and the page and carries nothing you typed. Check only a site you own or have permission to check: running the tool does not establish that permission.
Redirects, signatures and the Canonical field
Three parts of RFC 9116 bear on whether a reader can rely on a file. First, redirects. Section 5.2 says researchers should record any redirects, since they can lead to a different domain or IP address controlled by an attacker, and that further inspection of such redirects is recommended before using the information in the file. When a chain ends in a response, the tool lists each address with its status code, and marks the result for review when any is on another host name. A request that fails part way shows only the failure. Second, the signature. Section 2.3 says it is RECOMMENDED that a security.txt file be digitally signed using an OpenPGP cleartext signature. The tool checks the wrapper against the grammar in section 4: the BEGIN PGP SIGNED MESSAGE line, one or more Hash lines and nothing else, an empty line, the text, then a signature block of optional header lines, an empty line and one or more lines of base64 characters. A wrapper that differs is marked Fix. The tool is looser than the grammar in two ways: a wrapper line may end with a line feed alone, where the grammar writes a carriage return and line feed, as section 2.2 allows for every line, and algorithm names and base64 text are not checked. The tool does not verify the signature: a complete wrapper says nothing about whether it is valid or whose key made it. Third, the Canonical field. Section 2.5.2 says that if the field appears and the URI used to retrieve the file is not listed within any Canonical field, the contents of the file SHOULD NOT be trusted. The tool takes that URI to be the address the file was read from, the final address after any redirect. It shows a match only when that address is listed, and otherwise marks the file for review, saying after a redirect whether the address it asked for first is listed. Addresses are compared after each is parsed as a URL, and a value with white space or a control character is not compared.
Using the editor, the Expires countdown and publishing the file
The editor runs in your browser. It opens with the file under /.well-known/, which the RFC says to use, or with the top-level one when that is the only file found. When the file has a signature wrapper, the editor holds its text without the wrapper. The tool does not verify signatures, and a file you change needs signing again before you publish it. With no file, the editor opens with a short template: a comment line and an Expires line. Two controls write the two fields RFC 9116 requires. Add Contact line puts a Contact field after the last one already there, or at the end of the text; an email address you type gets mailto: in front, and anything else is kept as typed for the findings to check. Set Expires writes one Expires line for the end of the day you choose, in UTC, and replaces any Expires line already in the text. The date box starts 364 days after the current date in UTC. For someone ahead of UTC, as in Australia, that is 363 days after their own date during the first hours of each day. The line under the box counts the whole days until the end of the chosen day in UTC, rounded down. RFC 9116 section 2.5.5 says it is RECOMMENDED that the value be less than a year into the future, to avoid staleness, and the line says so when a date is a year or more away or has passed. The text box holds up to 20,000 characters. The findings under the editor are the same analysis that ran on the fetched file, applied to your text as you change it, with four differences. They read the text as the copy block holds it: line feeds as line endings, one after the last line and no byte order mark. They count days from your browser's clock at the moment the editor opened. A Canonical field is not compared with an address. And there is no response to check. Publish the copied text under /.well-known/, then run the check again.
Sources
- Internet Engineering Task Force (IETF), RFC Editor: RFC 9116: A File Format to Aid in Security Vulnerability Disclosure
- Internet Assigned Numbers Authority (IANA): security.txt Fields registry
- Internet Engineering Task Force (IETF), RFC Editor: RFC 3339: Date and Time on the Internet: Timestamps
- Internet Engineering Task Force (IETF), RFC Editor: RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
Worked example
An invented example, not taken from any site: an operations manager checks the company site before answering a supplier's security questionnaire.
- /.well-known/security.txt
- Status 404
- /security.txt
- Status 200, text/plain
- Contact
- An email address with no mailto:
- Expires
- A date six weeks in the past
- Signature wrapper
- None
The comparison is marked Fix: the only file is at the top-level path, and RFC 9116 section 3 says that for web-based services organisations MUST place the file under the /.well-known/ path. In the top-level card, the Contact line is marked Fix because its value has no scheme, Expires is marked Fix because the date has passed, and the missing signature is marked Review.
The editor opens with the top-level file. The manager deletes the old Contact line in the text box, types the address into the Contact box so the tool writes mailto: in front, and presses Set Expires with the starting date. The edited text then shows a new Review line, because RFC 9116 recommends encryption when a contact is an email address. They copy the text, ask the developer to publish it under /.well-known/, and run the check again.
Who uses this tool
Site owners publishing a first file
Start from the template, add a contact, set the Expires date and copy a file with the two fields RFC 9116 requires.
Developers after a deployment or a host move
Confirm the file is still served under /.well-known/ over HTTPS as text/plain, and see any redirect on the way to it.
Teams whose file is close to expiring
See how many days are left before the Expires date, review the contacts, then write a new Expires line.
Staff answering a security questionnaire
Read what the site publishes for vulnerability reports before answering a question about a disclosure contact.
Frequently asked questions
What is a security.txt file?
It is a plain text file a website publishes so that security researchers know how to report a vulnerability. RFC 9116 defines the format: one field on each line, such as Contact, Expires and Policy, with comments and blank lines allowed. The RFC says the file is intended to be complementary to an organisation's other public resources about its security disclosure practices, not a replacement for them.
Where does the security.txt file go?
RFC 9116 section 3 says that for web-based services organisations MUST place it under the /.well-known/ path, so its address ends in /.well-known/security.txt. For legacy compatibility a file might also be placed at the top-level path, /security.txt, or redirect from there to the other one. If a file is present in both locations, the RFC says the one in the /.well-known/ path MUST be used. This tool requests both and compares them.
Which fields does security.txt require?
Two. RFC 9116 says Contact MUST always be present, and that Expires MUST always be present and MUST NOT appear more than once. Section 2.5 says all fields are optional unless otherwise stated, which leaves Acknowledgments, Canonical, Encryption, Hiring, Policy and Preferred-Languages optional. The tool marks a missing Contact or Expires field as Fix, and the editor has a control for each.
What does this security.txt checker request from my site?
Our server looks up the site's name in DNS, then sends one GET request to /.well-known/security.txt and one to /security.txt over HTTPS, plus one more for each redirect, up to 5 for each address. A redirect can lead to an http:// address on port 80. It refuses private and reserved network addresses, reads at most 32,768 bytes of each response and gives each address 5 seconds. It takes a site name, not an IP address. Check only a site you own or have permission to check.
Does the checker verify the PGP signature?
No. It reports whether the file has the OpenPGP cleartext signature wrapper that RFC 9116 section 2.3 recommends, and it reads the fields inside the wrapper. A wrapper that does not match the grammar in section 4 is marked Fix. It does not check the signature against any key, so it cannot say whether the signature is valid or who made it. The RFC says it is always the security researcher's responsibility to make sure the key used is one they trust.
How far ahead should the Expires date be?
RFC 9116 section 2.5.5 says it is RECOMMENDED that the value be less than a year into the future, to avoid staleness. The field gives the date and time after which the data in the file is considered stale and should not be used. The editor's date box starts 364 days after the current date in UTC, which for someone ahead of UTC can be 363 days after their own date, and you can choose another date.