Security.txt Generator

Create a security.txt file with your vulnerability-report contact and expiry, then review it before publishing.

Contact and expiry

Use your own monitored mailto: address or HTTPS reporting page. Publishing makes this contact public and may attract spam.

Enter future time including seconds and UTC Z or a numeric timezone offset. Renew before it expires.

security.txt preview

Enter your contact and future expiry to preview the file. Fix any marked fields before export.

Publish it yourself at https://your-site.example/.well-known/security.txt as text/plain; charset=utf-8. Check the live file and contact; this page does not host or audit your site.

Why Make a Security.txt Contact File?

A Clear Reporting Route

Researchers who find a vulnerability need a way to reach the people responsible for it. A published contact file tells them where to send a report instead of guessing from a general support page. Check that the address or form is monitored before you share it.

A Date That Demands Review

An Expires timestamp marks when the file becomes stale. Choose a future time, set a reminder before it arrives, and confirm the contact still works each time you renew. RFC 9116 recommends an expiry less than a year away to reduce stale information.

An Inspectable File

The preview shows exactly what Copy and Download use: your Contact URI and Expires timestamp, each on its own line. Generation runs in this browser tab, but the page also loads ordinary site scripts and analytics. Do not enter secrets.

What Goes in This Security.txt File?

A security.txt file is a plain-text signpost for vulnerability reports, defined by RFC 9116. This generator writes one Contact URI and exactly one Expires timestamp. An email address needs a mailto: prefix; a web reporting page needs HTTPS. It does not check that the mailbox or website belongs to you. Use a channel you operate and monitor, not a stranger's address.

The expiry must include a timezone, for example 2030-02-01T12:00:00Z for UTC. An offset such as +02:00 is also accepted and retained in the file rather than silently converted. The output ends with a line feed, ready to save as UTF-8 text. This page omits optional policy, signing and canonical-file fields; add those through your own reviewed process if your disclosure program needs them.

Fields and Delivery

  • ContactA monitored mailto: address or an HTTPS reporting page. The file makes it public once published.
  • ExpiresA future RFC3339 date and time with seconds and an explicit timezone. Refresh the hosted file before this moment.
  • File nameDownload security.txt as UTF-8 plain text. The browser download does not upload it to your site.
  • Site locationPublish at https://your-site.example/.well-known/security.txt and serve with text/plain; charset=utf-8.

Common Use Cases

Launch a Reporting Channel

Prepare a small contact file when your team has agreed on who handles incoming vulnerability reports. Review the preview before placing it on the site.

Renew an Expiring File

When the published Expires time approaches, verify the contact still reaches your team, choose a new future time and replace the hosted file.

Switch Contact Methods

Move from an email inbox to an HTTPS reporting page when your process changes. Replace the old hosted file and check the new page yourself.

How to Create and Publish Security.txt

1

Enter Your Contact

Type your own mailto: address or HTTPS reporting page. A sample placeholder is not a usable contact and is never put in the output.

2

Choose an Expiry

Enter a future date and time with a timezone, then set a reminder to renew your published file before that moment.

3

Inspect and Export

Read the plain-text preview. Copy it or download security.txt. If clipboard access fails, the preview is selected for manual copying.

4

Publish and Verify

Host the file yourself over HTTPS under /.well-known/security.txt with a UTF-8 plain-text response. Open that URL and verify its contents and contact route.

What the Generator Helps You Check

Required Fields Together

The generator does not enable export until both a contact URI and a future expiry are valid. Errors stay beside the field you need to correct.

Exact Preview

Output remains selectable, so you can compare what you intend to publish with the contact and expiry you typed. Copy uses the same text as download.

No Domain Probe

The tool never fetches your site or tests its security. Publishing and checking the live file are separate jobs for the site owner.

Before You Publish

  • •Choose a monitored channel: If you publish an email address, it becomes visible to anyone and may attract spam or unwanted reports. An HTTPS form can be an alternative.
  • •Check the response: A downloaded file alone is not a deployed file. Check the HTTPS URL and response content type after your own hosting step.
  • •Keep scope clear: The file applies to the domain or IP address where it is retrieved, not automatically to its parent or subdomains.
  • •Permission is separate: Publishing a contact file does not grant anyone permission to probe, exploit or test your systems.

Review Your Contact File Above

Enter a contact you control and an expiry you can maintain. Read the generated lines before copying or saving them. Fix any field error before export; the form keeps your draft so you can correct it.

After you publish, revisit the hosted file and the contact destination. This generator cannot host it, audit your domain, guarantee delivery of reports or certify your security posture. To manage crawler access instead, use the separate robots.txt generator; it does not create vulnerability contacts.

Related tools

Frequently Asked Questions

Where should I put the file?

Publish security.txt under /.well-known/ on your own HTTPS site. Serve it as UTF-8 plain text and open the URL to check the published content.

What happens when it expires?

The file is considered stale after its Expires timestamp. Check that the contact still works, generate a new file with a future date and replace the hosted copy before expiry.

Does a security.txt file give permission to test my site?

No. A reporting contact does not authorize security testing or define its permitted scope. Agree on any testing policy separately.

Does this generator publish the file or certify my site?

No. It prepares text and a download in your browser. You must publish it, verify the HTTPS response and maintain the contact yourself; generation is not a site audit or certification.