Security.txt - Revision history

Jsummers at 20:16, 4 March 2026

2026-03-04T20:16:10Z

Jsummers: /* Links */

2017-11-10T16:52:08Z

‎Links

Jsummers at 16:58, 22 September 2017

2017-09-22T16:58:18Z

Jsummers: Created page with "{{FormatInfo |formattype=electronic |subcat=Web |extensions={{ext|txt}} }} '''Security.txt''' is a proposed standard way for website owners to provide security-related informa..."

2017-09-22T16:56:58Z

Created page with "{{FormatInfo |formattype=electronic |subcat=Web |extensions={{ext|txt}} }} '''Security.txt''' is a proposed standard way for website owners to provide security-related informa..."

New page

{{FormatInfo
|formattype=electronic
|subcat=Web
|extensions={{ext|txt}}
}}
'''Security.txt''' is a proposed standard way for website owners to provide security-related information (e.g. how to report vulnerabilities) to security researchers and other third parties.

It is similar in concept, and in format, to [[Robots Exclusion Standard|robots.txt]].

To use it, the website administrator creates a document at <code>/.well-known/security.txt</code>. The full URL would be something like <code><nowiki>http://example.com/.well-known/security.txt</nowiki></code>. (The <code>"/.well-known/</code>" component of the URL is from RFC 5785.)

== Links ==
* [https://github.com/EdOverflow/security-txt GitHub project]
* [https://www.ietf.org/id/draft-foudil-securitytxt-00.txt RFC draft 2017-09-10]

[[Category:File formats with a distinctive filename]]

← Older revision		Revision as of 16:58, 22 September 2017
Line 14:		Line 14:
	* [https://www.ietf.org/id/draft-foudil-securitytxt-00.txt RFC draft 2017-09-10]		* [https://www.ietf.org/id/draft-foudil-securitytxt-00.txt RFC draft 2017-09-10]

		+	[[Category:Security]]
	[[Category:File formats with a distinctive filename]]		[[Category:File formats with a distinctive filename]]

@@ Line 8: / Line 8: @@
 It is similar in concept, and in format, to [[Robots Exclusion Standard|robots.txt]].
-To use it, the website administrator creates a document at <code>/.well-known/security.txt</code>. The full URL would be something like <code><nowiki>http://example.com/.well-known/security.txt</nowiki></code>. (The <code>"/.well-known/</code>" component of the URL is from RFC 5785.)
+To use it, the website administrator creates a document at <code>/.well-known/security.txt</code>. The full URL would be something like <code><nowiki>http://example.com/.well-known/security.txt</nowiki></code>. (See also [[Well-known URI]].)
 == Links ==

@@ Line 11: / Line 11: @@
 == Links ==
 * [https://github.com/EdOverflow/security-txt GitHub project]
 * [https://www.ietf.org/id/draft-foudil-securitytxt-00.txt RFC draft 2017-09-10]