Toolsky

Free Online Tools & Utilities for Every Task.

Security.txt Generator

Create a security.txt file to help researchers report vulnerabilities.

How researchers should reach you.
When this policy expires (Max 1 year recommended).
Link to your public PGP key.
Link to your vulnerability disclosure policy.
Link to your security researchers hall of fame.
Link to security-related job openings.
The permanent URL for this file.
Comma-separated list of language codes.
Generated security.txt Content

Place this file at /.well-known/security.txt or the root directory.

A security researcher finds a flaw in your website — a way into data that should be private. Now what? They look for a contact, find only a generic support form or a social media link, and after a week of silence many give up… or disclose the problem publicly. That dead end is exactly what security.txt exists to prevent: a small, standardised file that tells researchers who to contact, how, and under what policy. This generator builds the file for you, field by field, following the format defined in RFC 9116, so responsible disclosure has a working front door on your site.

What security.txt Is and Where It Lives

Security.txt is the security world's counterpart to robots.txt — fittingly, its closest relative on your server is the file our Robots.txt Generator produces, one guiding crawlers and the other guiding humans. The standard places it at a fixed, guessable address: yoursite.com/.well-known/security.txt (with the root path /security.txt kept working as a fallback). Anyone looking to report a vulnerability — a researcher, a customer, another company's security team — knows to check that address first, before digging through your site for an email that may not exist. The file is plain text, a handful of labelled lines, and it carries no sensitive information: it is an invitation, written in a format both humans and automated scanners can parse. Since 2022 it has been a formal IETF standard rather than a grassroots convention, and large organisations increasingly treat its absence as a small mark of immaturity.

Fields the Generator Helps You Fill

  • Contact — the one mandatory field: a monitored security email address, a disclosure web form, or a phone number. Multiple Contact lines are allowed, in your order of preference.
  • Expires — a required expiry date for the information, so stale contacts do not mislead researchers years later; the standard recommends a year or less.
  • Policy — a link to your vulnerability disclosure policy: what you accept, how you respond, and your stance on safe harbour for good-faith researchers.
  • Acknowledgments — a link to a page thanking past reporters, a small courtesy that measurably encourages careful reports.
  • Preferred-Languages — the languages your team can handle reports in, so a researcher in another country knows whether English will be understood.
  • Encryption, Canonical and Hiring — optional lines for your PGP key (for sensitive reports), the file's canonical URL, and even a link to security-team job openings.

How to Create Your security.txt

  1. Decide who genuinely receives vulnerability reports — a dedicated address such as security@yourdomain, monitored by someone empowered to act, not an unmonitored inbox.
  2. Enter that contact in the generator; add a disclosure form URL as a second Contact line if you have one.
  3. Set the expiry date — twelve months out is a sensible default — and note it in a calendar so the file is renewed before it lapses.
  4. Add your policy link; if you have no disclosure policy page yet, write a short one before publishing the file, because the file will send people there.
  5. Fill in the optional fields that apply — languages, acknowledgments, encryption key — and skip the rest rather than inventing filler.
  6. Generate the file, then upload it to /.well-known/security.txt on your server (and /security.txt for the fallback), and open the URL to confirm it loads as plain text.

A Finished security.txt, Line by Line

Here is what a complete, honest file looks like for a small company:

Contact: mailto:security@northwind-shop.example
Contact: https://northwind-shop.example/security-report
Expires: 2027-03-01T00:00:00.000Z
Preferred-Languages: en, de
Policy: https://northwind-shop.example/disclosure-policy
Acknowledgments: https://northwind-shop.example/thanks
Canonical: https://northwind-shop.example/.well-known/security.txt

Read it as a researcher would: two ways to reach a human, an expiry that proves the file is maintained, the rules of engagement one click away, and confirmation that this address is the file's official home. Producing this took minutes in the generator; the work that matters is organisational — making sure the mailbox is read and the policy page says something real. Websites that complete the picture usually also audit what researchers would find on arrival, so pair publication with our SSL Checker to be sure the connection they use to reach you is sound.

Mistakes That Make security.txt Useless

The cruellest failure is a perfect file pointing at a dead mailbox: the researcher writes, hears nothing, and concludes you do not care — the exact outcome the file exists to prevent. Test the contact address after publishing. Second is expiry neglect: an expired file signals abandonment, and some scanners downgrade or ignore expired files entirely. Third, serving the file as an HTML page or behind a redirect chain; the standard expects plain text at the well-known path, and tools that look for it may not follow page furniture. Fourth, legal overreach in the linked policy — policies that threaten good-faith researchers with prosecution reliably produce public disclosures instead of private reports. Keep the tone welcoming and the safe-harbour promise clear; you are asking skilled strangers for a favour.

Frequently Asked Questions About security.txt

Is security.txt legally required?

Not for most private websites, though some government and regulated-sector frameworks now require or strongly recommend it. For everyone else it is voluntary — and increasingly expected as basic security hygiene.

Where exactly must the file be hosted?

At /.well-known/security.txt on your domain, served as plain text over HTTPS. Keeping /security.txt working as well covers older tools that check the root path first.

What if we have no security team?

Then the contact is whoever would handle a serious bug report — a founder, your lead developer, your hosting provider's abuse desk. The requirement is a monitored route to a responsible human, not a department.

How often should the file be renewed?

Before its Expires date passes — annually at the latest — and immediately whenever contacts or policies change. An expired file is worse than a short one; set a calendar reminder when you publish.

Does publishing security.txt invite attacks?

No. Attackers do not need your permission or your file. What the file invites is reports from the people who find flaws and want to help — the audience you most want to hear from.

Should the Contact be a person's email?

Prefer a role address like security@yourdomain: people change jobs, role addresses persist, and a role inbox can be shared by whoever is on duty.

Can the file list more than one contact method?

Yes — repeat the Contact field, most preferred first. An email plus a web form is the common pairing, giving researchers a fallback if one route fails.

An Open Door for the Right People

Vulnerabilities get found either way; security.txt decides whether the finder knocks on your door or announces it in the street. Five minutes with the generator, one monitored mailbox, and your site joins the part of the web that treats disclosure as the collaboration it is.