Serve security.txt from /.well-known/ on Shopify
Why it matters
RFC 9116 puts the file at /.well-known/security.txt and keeps /security.txt only for older setups. Researchers and tools look in the standard place first.
The fix
Not possible on Shopify. Shopify does not let a store publish a file at /.well-known/security.txt, so only a legacy path or a redirect is available and this finding cannot be fully cleared. Keep your security contact on a page of your store.
Related
- Reported by the security.txt check
- Publish a security.txt file
- Serve security.txt over https
- Serve security.txt as text/plain with utf-8
- Add a Contact line to security.txt
- Fix the Contact value in security.txt
- Add an Expires line to security.txt
- Use an RFC 3339 date in the Expires line
- Renew the expired security.txt
- Renew security.txt before it expires
- Shorten the security.txt Expires date
- Fix repeated or insecure fields in security.txt
- Make the Canonical line match where the file is served
Scan your domain to see whether this applies to you.