Check security.txt
check_security_txtChecks a domain for a published RFC 9116 security.txt file at /.well-known/security.txt and /security.txt, then reports contact, expiry, policy fields, and whether it has expired.
Instructions
Looks for a security.txt file (RFC 9116) at https:///.well-known/security.txt and then /security.txt, and reports whether one is published, its Contact, Expires, Policy and other fields, and whether it has expired. Redirects are reported but not followed. Refuses IP addresses, ports other than 80 and 443, and any host that resolves to a private, loopback, link-local, carrier-grade NAT or cloud metadata address.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"domain": "<domain>"
},
"name": "check_security_txt"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain to check, such as example.com. A full URL is also accepted; only its host name is used. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Where the file was found; left out when none was found | |
| found | Yes | ||
| notes | Yes | Checks that did not finish, were skipped or saw partial data | |
| domain | Yes | ||
| fields | No | RFC 9116 fields, cleaned and shortened; left out when no file was found | |
| signed | Yes | True when the file carries an OpenPGP cleartext signature | |
| checked | Yes | ||
| expired | No | Left out when there is no readable Expires date | |
| findings | Yes | ||
| scannedAt | Yes | ||
| durationMs | Yes | ||
| contentType | No |