Warning

security.txt expires more than a year ahead

The short version

Set Expires less than a year ahead so the file gets reviewed.

What it means

The Expires: date in your security.txt is more than a year in the future. RFC 9116 recommends less than a year.

Why it matters

A far-off date means the file may never be reviewed: people leave, mailboxes close and policy pages move, while the file keeps promising that its contacts are current. A shorter expiry makes sure someone looks at it at least once a year.

How to fix it

  1. Change the date to less than a year ahead, for example Expires: 2027-06-30T23:00:00Z.
  2. Review the contacts while you are there.
  3. Sign the file again if you sign it.
  4. If the file is generated during deployment, set the expiry to a fixed number of months after the deployment date, so it moves forward with every release.

Check it worked

Run the standard files check again. security.txt should show an expiry less than a year away, and the finding should be gone.