Fail

security.txt has no Expires

The short version

Add one Expires line, less than a year ahead.

What it means

Your security.txt has no Expires: line, or the date isn't in the required format. RFC 9116 requires exactly one Expires field, as an RFC 3339 date and time with a time zone, such as 2027-06-30T23:00:00Z.

Why it matters

Expires stops researchers from relying on stale files: contact details in an old file may lead to a mailbox nobody reads. Without it, readers can't tell whether the file is current, and tools that follow the standard treat the file as invalid.

How to fix it

  1. Add one line such as Expires: 2027-06-30T23:00:00Z.
  2. Use the full form with a T between date and time and a time zone (Z for UTC or an offset such as +02:00). A date alone isn't valid.
  3. Choose a date less than a year ahead, and renew the file before then.
  4. Remove any second Expires line; only one is allowed.

Check it worked

Run the standard files check again. security.txt should show when it expires, and the finding should be gone.