Shorten the security.txt Expires date
Why it matters
RFC 9116 recommends an Expires date less than a year ahead, so that the file is reviewed regularly and does not outlive its mailbox. A very distant date defeats that purpose.
The fix
- Set Expires to a date less than a year ahead and renew it on a schedule, for example every six months.
- Put the renewal in your calendar.
text
Expires: 2026-12-31T23:59:59Z Related
- Reported by the security.txt check
- Publish a security.txt file
- Serve security.txt from /.well-known/
- Serve security.txt over https
- Serve security.txt as text/plain with utf-8
- Add a Contact line to security.txt
- Fix the Contact value in security.txt
- Add an Expires line to security.txt
- Use an RFC 3339 date in the Expires line
- Renew the expired security.txt
- Renew security.txt before it expires
- Fix repeated or insecure fields in security.txt
- Make the Canonical line match where the file is served
Scan your domain to see whether this applies to you.