Title: Codo Security.txt
Author: Codo Digital Ltd
Published: <strong>November 16, 2026</strong>
Last modified: November 16, 2026

---

Search plugins

![](https://ps.w.org/codo-security-txt/assets/banner-772x250.png?rev=3804493)

![](https://ps.w.org/codo-security-txt/assets/icon.svg?rev=3804493)

# Codo Security.txt

 By [Codo Digital Ltd](https://profiles.wordpress.org/cododigital/)

[Download](https://downloads.wordpress.org/plugin/codo-security-txt.1.0.0.zip)

 * [Details](https://wordpress.org/plugins/codo-security-txt/#description)
 * [Reviews](https://wordpress.org/plugins/codo-security-txt/#reviews)
 *  [Installation](https://wordpress.org/plugins/codo-security-txt/#installation)
 * [Development](https://wordpress.org/plugins/codo-security-txt/#developers)

 [Support](https://wordpress.org/support/plugin/codo-security-txt/)

## Description

A `security.txt` file is a small text file at `/.well-known/security.txt` that tells
security researchers who to contact about a vulnerability on your site. It is standardised
as [RFC 9116](https://www.rfc-editor.org/rfc/rfc9116). Without one, a report may
never reach you.

Codo Security.txt serves the file from your WordPress settings. There is nothing
to upload and no rewrite rules to flush.

**What it does**

 * Serves `/.well-known/security.txt` (and optionally the legacy `/security.txt`)
   as `text/plain; charset=utf-8`.
 * 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.
 * 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.
 * Adds the Canonical line for you.
 * Can publish a PGP clear-signed message exactly as you signed it.
 * Warns when a physical `security.txt` file would override the plugin, when WordPress
   is in a subdirectory, and on subdirectory multisite subsites.
 * Checks that your web server really delivers the file, from the settings screen
   and Site Health.
 * Works on Apache, NGINX and multisite, and does not interfere with other `/.well-
   known/` handlers.
 * Loads no admin JavaScript, adds no tracking and has no Pro tier.

**What it does not do**

 * 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.
 * 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 `/.well-known/security.
   txt`.

Built and maintained by [Codo Digital](https://codo.digital).

### External services

The “Check delivery” button and the Site Health test make one request to your own
site’s `/.well-known/security.txt` 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.

## Installation

 1. Install and activate the plugin.
 2. Go to Settings > Security.txt.
 3. Enter at least one contact and an expiry date, tick “Publish” and save.
 4. Use “Check delivery now” to confirm your web server serves the file.

## FAQ

### Where is the file served?

At `https://your-site.example/.well-known/security.txt`, and at `/security.txt` 
unless you turn the legacy location off.

### The file returns a 404

Your web server is probably answering `/.well-known/` itself instead of passing 
the request to WordPress.

NGINX: make sure no `location ~ /\.` rule denies dotfiles before WordPress sees 
the request. A rule like this keeps `.well-known` working:

    ```
    location ^~ /.well-known/ { try_files $uri /index.php?$args; }
    ```

Apache: the standard WordPress `.htaccess` already passes unknown paths to `index.
php`. If you have a rule that blocks dotfiles, add an exception for `.well-known`:

    ```
    RewriteRule ^\.well-known/ - [L]
    ```

Some hosts and CDNs also cache 404s. Purge the cache after you publish.

### A real security.txt file exists on my server

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.

### Does it work on multisite?

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.

### Why is an expired file still served?

So researchers can still find your contact details. The plugin warns you loudly 
until you renew it.

### Why does it say my expiry is too far away?

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.

### Can I turn it off without deleting the settings?

Untick “Publish”, or define `CODO_SECURITY_TXT_DISABLE` as `true` in `wp-config.
php`.

### Does it send data anywhere?

No. See “External services” below.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“Codo Security.txt” is open source software. The following people have contributed
to this plugin.

Contributors

 *   [ Codo Digital Ltd ](https://profiles.wordpress.org/cododigital/)

[Translate “Codo Security.txt” into your language.](https://translate.wordpress.org/projects/wp-plugins/codo-security-txt)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/codo-security-txt/),
check out the [SVN repository](https://plugins.svn.wordpress.org/codo-security-txt/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/codo-security-txt/)
by [RSS](https://plugins.trac.wordpress.org/log/codo-security-txt/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.0.0

 * First release.

## Meta

 *  Version **1.0.0**
 *  Last updated **1 day ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.2 or higher **
 *  Tested up to **7.1.4**
 *  PHP version ** 7.4 or higher **
 * Tags
 * [rfc 9116](https://wordpress.org/plugins/tags/rfc-9116/)[security](https://wordpress.org/plugins/tags/security/)
   [security.txt](https://wordpress.org/plugins/tags/security-txt/)[vulnerability-disclosure](https://wordpress.org/plugins/tags/vulnerability-disclosure/)
   [well-known](https://wordpress.org/plugins/tags/well-known/)
 *  [Advanced View](https://wordpress.org/plugins/codo-security-txt/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/codo-security-txt/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/codo-security-txt/reviews/)

## Contributors

 *   [ Codo Digital Ltd ](https://profiles.wordpress.org/cododigital/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/codo-security-txt/)