# security.txt Checker

Check a website's security.txt file against RFC 9116. The tool fetches /.well-known/security.txt (and the older /security.txt location), reads every field, checks the required Contact and Expires fields, the expiry date, URI schemes, the content type and the Canonical field, and reports whether the file is signed.

## Frequently asked questions

### What is security.txt?

A plain text file defined in RFC 9116 that tells security researchers how to report vulnerabilities, served at /.well-known/security.txt. It lists contact addresses, an expiry date and optionally an encryption key, a disclosure policy and preferred languages.

### Which fields are required?

At least one Contact field with a mailto:, tel: or https: URI, and exactly one Expires field with a date and time in RFC 3339 format, such as 2027-01-31T23:00:00.000Z. The tool reports a missing or repeated Expires field and an expiry date in the past as errors.

### How far in the future should Expires be?

RFC 9116 recommends a date less than a year ahead, so the file is reviewed regularly. The tool warns when the date is more than a year away.

### Does the file have to be signed?

No, but the RFC recommends signing it with an OpenPGP cleartext signature so readers can verify it. The tool detects a signed file and reads the fields inside it, but it does not verify the signature.

### Why is the content type checked?

RFC 9116 requires the file to be served as text/plain with the UTF-8 charset. A file served as HTML usually means the site returned an error page or a soft 404 instead of the file.

### What does the Canonical field do?

It lists the URLs where the file is meant to live. If it is present but does not contain the URL the file was fetched from, the file may have been copied from elsewhere, so the tool warns.

Your ad here?

[Email us](mailto:hi@dennn.is?subject=Advertising%20on%20OneClick%20Pro)

[Ad 433 tools for your AI agents through one MCP server.](https://multitaskai.com/?ref=oneclickpro)
