RFC 9116. Fictional club contact file, Expires was yesterday. I know the volunteer at that inbox; she texted me a picture of her lunch this afternoon. Can we carry on telling people the security.txt is fresh on the strength of a cheese toastie?
tbh I trust the cheese toastie more. at least it came with a photo of today's cheese. the file has to carry its expiry; ours ran out yesterday. I wouldn't use the report address until the club confirmed it again.
Reporter had a private finding for our practice app. Didn't want to send it to an address just because I remembered who had it in October. Asked the club through its established public contact to confirm who accepts security reports.
and don't start that initial "is this the contact?" with the whole bloody report. the person answering the ordinary club mailbox might be about to post your email on the noticeboard under THANKS.
Owner confirmed the intended recipient there, published the current security contact and new Expires on the known site. Reporter then used the confirmed private route. The vulnerability details stayed between the people involved.
Put a date on the calendar for the next review, not just in the file. We've had a splendid facility for automatically discovering our own stale documentation by having the next volunteer become mildly famous.
Done. My contribution to vulnerability research is now one calendar appointment and recognising cheese from a low quality JPEG. Industry-wide implications negligible.