
security.txt checker
Check a security.txt file against RFC 9116: required fields, an expired Expires date, and recommended Canonical and Encryption lines.
security.txt checker reads an RFC 9116 file and lists every Contact and Expires field found, flagging an Expires date that has passed or cannot be parsed. It notes whether Canonical, Encryption and Policy, recommended but optional, showed up. A missing Contact or Expires field is marked as that problem; more than one Expires field is also flagged.
Questions
Which fields are required?
Contact and Expires; either missing is flagged as a specific problem.
What happens with an expired date?
It is flagged as EXPIRED with the number of days since it passed.
What happens with more than one Expires field?
It is flagged, since RFC 9116 requires exactly one.
What fields are recommended but optional?
Canonical, Encryption and Policy; their absence is noted but does not count as a problem.
What comment style does the parser recognise?
Lines starting with #, which are skipped, per RFC 9116's field syntax.