How to fix missing security txt on Headless / Custom (I build in code)

Steps for Headless / Custom (I build in code)

1. Create the file at <webroot>/.well-known/security.txt on your server (or as a static asset in your framework's public directory).
2. Ensure your web server or framework serves it with Content-Type: text/plain and does not block dotfile directories.
3. For Next.js: place security.txt in /public/.well-known/security.txt — Next.js serves everything in /public as static files.
4. For Nuxt.js: place security.txt in /public/.well-known/security.txt.
5. Verify by visiting https://yourdomain.com/.well-known/security.txt.

What is missing security txt?

A security.txt file is a small, plain-text file you place at a standardised web address on your store (/.well-known/security.txt). It tells security researchers — people who discover bugs or vulnerabilities in websites — exactly how to contact you to report the problem privately, before a bad actor can exploit it. Think of it as a "if you find something broken, call this number" sign on your front door. The format is an internet standard (RFC 9116) championed by the security community and recognised by platforms like Google and HackerOne.

Without a security.txt, a well-meaning researcher who finds a vulnerability in your store has no obvious, trusted way to reach you — so they may give up, publish it publicly, or disclose it to the wrong party, leaving your customers' data exposed. OWASP lists Security Misconfiguration (A05:2021) as one of the most common causes of breaches, and missing disclosure channels fall squarely in that category. Regulators and payment-card standards (PCI-DSS) increasingly expect documented vulnerability-disclosure processes; having a security.txt demonstrates basic security hygiene and can reduce your legal exposure if an incident occurs. It costs almost nothing to add and can prevent a damaging public breach disclosure.

See the complete Missing security txt guide for every platform and the full background.