Publish a security.txt file on Vercel

Why it matters

A security.txt file tells researchers who to contact when they find a security problem on your site, so a report reaches you instead of being posted publicly or lost. It is a small plain text file defined in RFC 9116.

The fix

1. Add the file to your project as public/.well-known/security.txt (for frameworks that use a different static folder, put it in that folder, so it ends up at /.well-known/security.txt in the build output).
2. Commit and deploy, then open https://example.com/.well-known/security.txt. Vercel serves static files with a content type based on the extension, so a file named security.txt is sent as text/plain.

Contact: mailto:security@example.com
Expires: 2026-12-31T23:59:59Z
Preferred-Languages: en
Canonical: https://example.com/.well-known/security.txt

The examples use example.com. Replace it with your own domain.

Read the documentation ↗(opens in a new tab)

Related

• Reported by the security.txt check
• Serve security.txt from /.well-known/
• 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