{"id":403010,"date":"2026-11-16T08:19:51","date_gmt":"2026-11-16T08:19:51","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/codo-security-txt\/"},"modified":"2026-11-16T08:19:18","modified_gmt":"2026-11-16T08:19:18","slug":"codo-security-txt","status":"publish","type":"plugin","link":"https:\/\/mr.wordpress.org\/plugins\/codo-security-txt\/","author":18270956,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.0.0","stable_tag":"1.0.0","tested":"7.1.4","requires":"6.2","requires_php":"7.4","requires_plugins":null,"header_name":"Codo Security.txt","header_author":"Codo Digital","header_description":"Publish a valid RFC 9116 security.txt file for your site, with strict validation, expiry reminders and a Site Health check. Free, no upsells.","last_updated":"2026-11-16 08:19:18","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/github.com\/Codo-Digital-Ltd\/codo-security-txt","header_author_uri":"https:\/\/codo.digital","rating":0,"author_block_rating":0,"active_installs":0,"downloads":56,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.0":{"tag":"1.0.0","author":"cododigital","date":"2026-11-16 08:19:18","revision":3804493}},"upgrade_notice":{"1.0.0":"<p>First release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3804493,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3804493,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3804493,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3804493,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3804493,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[291970,600,149750,270121,54762],"plugin_category":[54],"plugin_contributors":[284951],"plugin_business_model":[],"class_list":["post-403010","plugin","type-plugin","status-publish","hentry","plugin_tags-rfc-9116","plugin_tags-security","plugin_tags-security-txt","plugin_tags-vulnerability-disclosure","plugin_tags-well-known","plugin_category-security-and-spam-protection","plugin_contributors-cododigital","plugin_committers-cododigital"],"banners":{"banner":"https:\/\/ps.w.org\/codo-security-txt\/assets\/banner-772x250.png?rev=3804493","banner_2x":"https:\/\/ps.w.org\/codo-security-txt\/assets\/banner-1544x500.png?rev=3804493","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/codo-security-txt\/assets\/icon.svg?rev=3804493","icon":"https:\/\/ps.w.org\/codo-security-txt\/assets\/icon.svg?rev=3804493","icon_2x":false,"generated":false},"screenshots":[],"raw_content":"<!--section=description-->\n<p>A <code>security.txt<\/code> file is a small text file at <code>\/.well-known\/security.txt<\/code> that tells security researchers who to contact about a vulnerability on your site. It is standardised as <a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc9116\">RFC 9116<\/a>. Without one, a report may never reach you.<\/p>\n\n<p>Codo Security.txt serves the file from your WordPress settings. There is nothing to upload and no rewrite rules to flush.<\/p>\n\n<p><strong>What it does<\/strong><\/p>\n\n<ul>\n<li>Serves <code>\/.well-known\/security.txt<\/code> (and optionally the legacy <code>\/security.txt<\/code>) as <code>text\/plain; charset=utf-8<\/code>.<\/li>\n<li>Checks every field strictly: Contact, Expires, Encryption, Acknowledgments, Preferred-Languages, Canonical, Policy, Hiring and CSAF. URLs must be https, and bad input is refused with a clear message instead of being saved.<\/li>\n<li>Keeps the file from going stale. It shows a notice on the Dashboard and Plugins screens, adds a Site Health test, emails the site admin 30 days and 7 days before it expires and when it has expired, and has a one-click \"Extend by one year\" button.<\/li>\n<li>Adds the Canonical line for you.<\/li>\n<li>Can publish a PGP clear-signed message exactly as you signed it.<\/li>\n<li>Warns when a physical <code>security.txt<\/code> file would override the plugin, when WordPress is in a subdirectory, and on subdirectory multisite subsites.<\/li>\n<li>Checks that your web server really delivers the file, from the settings screen and Site Health.<\/li>\n<li>Works on Apache, NGINX and multisite, and does not interfere with other <code>\/.well-known\/<\/code> handlers.<\/li>\n<li>Loads no admin JavaScript, adds no tracking and has no Pro tier.<\/li>\n<\/ul>\n\n<p><strong>What it does not do<\/strong><\/p>\n\n<ul>\n<li>It does not verify PGP signatures. It checks the structure of a signed message, its Contact line and its Expires date, but verifying a signature needs GnuPG.<\/li>\n<li>It cannot publish the file on a subdirectory multisite subsite. Those share a host with the main site, and only the main site can answer <code>\/.well-known\/security.txt<\/code>.<\/li>\n<\/ul>\n\n<p>Built and maintained by <a href=\"https:\/\/codo.digital\">Codo Digital<\/a>.<\/p>\n\n<h3>External services<\/h3>\n\n<p>The \"Check delivery\" button and the Site Health test make one request to your own site's <code>\/.well-known\/security.txt<\/code> to confirm the web server delivers the file. The request goes to your own domain only. No data is sent to Codo Digital or any third party.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Install and activate the plugin.<\/li>\n<li>Go to Settings &gt; Security.txt.<\/li>\n<li>Enter at least one contact and an expiry date, tick \"Publish\" and save.<\/li>\n<li>Use \"Check delivery now\" to confirm your web server serves the file.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"where%20is%20the%20file%20served%3F\"><h3>Where is the file served?<\/h3><\/dt>\n<dd><p>At <code>https:\/\/your-site.example\/.well-known\/security.txt<\/code>, and at <code>\/security.txt<\/code> unless you turn the legacy location off.<\/p><\/dd>\n<dt id=\"the%20file%20returns%20a%20404\"><h3>The file returns a 404<\/h3><\/dt>\n<dd><p>Your web server is probably answering <code>\/.well-known\/<\/code> itself instead of passing the request to WordPress.<\/p>\n\n<p>NGINX: make sure no <code>location ~ \/\\.<\/code> rule denies dotfiles before WordPress sees the request. A rule like this keeps <code>.well-known<\/code> working:<\/p>\n\n<pre><code>location ^~ \/.well-known\/ { try_files $uri \/index.php?$args; }\n<\/code><\/pre>\n\n<p>Apache: the standard WordPress <code>.htaccess<\/code> already passes unknown paths to <code>index.php<\/code>. If you have a rule that blocks dotfiles, add an exception for <code>.well-known<\/code>:<\/p>\n\n<pre><code>RewriteRule ^\\.well-known\/ - [L]\n<\/code><\/pre>\n\n<p>Some hosts and CDNs also cache 404s. Purge the cache after you publish.<\/p><\/dd>\n<dt id=\"a%20real%20security.txt%20file%20exists%20on%20my%20server\"><h3>A real security.txt file exists on my server<\/h3><\/dt>\n<dd><p>Your web server serves a real file in preference to WordPress, so the settings here are ignored. The plugin warns you on its settings page and in Site Health. Delete the file.<\/p><\/dd>\n<dt id=\"does%20it%20work%20on%20multisite%3F\"><h3>Does it work on multisite?<\/h3><\/dt>\n<dd><p>Yes. Each site has its own settings. On a subdirectory network only the main site can publish the file, because every site shares one host.<\/p><\/dd>\n<dt id=\"why%20is%20an%20expired%20file%20still%20served%3F\"><h3>Why is an expired file still served?<\/h3><\/dt>\n<dd><p>So researchers can still find your contact details. The plugin warns you loudly until you renew it.<\/p><\/dd>\n<dt id=\"why%20does%20it%20say%20my%20expiry%20is%20too%20far%20away%3F\"><h3>Why does it say my expiry is too far away?<\/h3><\/dt>\n<dd><p>RFC 9116 recommends an expiry less than a year ahead, so that the file is reviewed regularly. A later date is accepted with a warning.<\/p><\/dd>\n<dt id=\"can%20i%20turn%20it%20off%20without%20deleting%20the%20settings%3F\"><h3>Can I turn it off without deleting the settings?<\/h3><\/dt>\n<dd><p>Untick \"Publish\", or define <code>CODO_SECURITY_TXT_DISABLE<\/code> as <code>true<\/code> in <code>wp-config.php<\/code>.<\/p><\/dd>\n<dt id=\"does%20it%20send%20data%20anywhere%3F\"><h3>Does it send data anywhere?<\/h3><\/dt>\n<dd><p>No. See \"External services\" below.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>First release.<\/li>\n<\/ul>","raw_excerpt":"Publish a valid RFC 9116 security.txt so researchers know how to report a vulnerability. Checks every field, warns before it expires.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/mr.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/403010","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mr.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/mr.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/mr.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=403010"}],"author":[{"embeddable":true,"href":"https:\/\/mr.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/cododigital"}],"wp:attachment":[{"href":"https:\/\/mr.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=403010"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/mr.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=403010"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/mr.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=403010"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/mr.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=403010"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/mr.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=403010"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/mr.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=403010"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}