Publish a security.txt file on Caddy

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. Create /var/www/security/.well-known/security.txt with the content shown in the generic tab.
2. Add a handle block for the path to the site block of example.com. file_server sets Content-Type from the .txt extension, which Caddy serves as text/plain with the utf-8 charset.
3. Run caddy reload and open https://example.com/.well-known/security.txt to confirm.

example.com {
	handle /.well-known/security.txt {
		root * /var/www/security
		file_server
	}
	# keep the rest of your site configuration here
}

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