What it means
We found security.txt at /security.txt in the site root but not at /.well-known/security.txt.
The root location is the older one; RFC 9116 makes /.well-known/ the standard place and the root
location only a fallback.
Why it matters
This is information. Most tools look in /.well-known/ first and some never look in the root.
Moving the file costs nothing and makes sure every reader finds it.
How to fix it
- Create the folder
.well-knownin your web root if it doesn't exist. - Move or copy the file to
/.well-known/security.txt. - Keep the root copy, or redirect
/security.txtto the new location with a 301. - Update any Canonical line so it lists the new address.
- Check that your server doesn't hide folders starting with a dot; some configurations block them.
Check it worked
Run the standard files check again. security.txt should be found at /.well-known/security.txt, and the finding should be gone.