What it means
Some lines in your security.txt don't follow RFC 9116: a line that isn't a Field: value pair, a
URI field without a valid https://, mailto: or tel: value, a second Expires or Preferred-Languages
line, or an Expires date in the wrong format. A Canonical line that doesn't include the address where the
file was found is reported here too. The detail lists the line numbers.
Why it matters
Readers skip lines they can't parse, so a contact written wrongly may simply be lost. A wrong Canonical makes the file look copied from another site.
How to fix it
- Open the file and go to each listed line.
- Write each field as
Name: value, with comments starting with#. - Use full URIs:
mailto:security@example.com,https://example.com/policy. - Keep exactly one Expires and at most one Preferred-Languages line.
- List the file's own HTTPS address in Canonical, for example
Canonical: https://example.com/.well-known/security.txt.
Check it worked
Run the standard files check again. No invalid lines should be listed, and the finding should be gone.