Skip to content

Free security.txt checker

Check that your security.txt file tells people how to report a vulnerability, and that it has not expired.

Reads /.well-known/security.txt only. No login access needed. What happens to the domain you enter

Example report

example.com
  • 1 Low
  • 1 Information
  • security.txt is incomplete or expiredexample.comLow

    The Expires date, 31 March 2026, has passed.

    Next step

    Make sure the file has at least one Contact line and an Expires date in the future (RFC 9116), and set a reminder to update it.

    View fix guide

  • No security.txtwww.example.comInformation

    https://www.example.com/.well-known/security.txt answered 404.

    Next step

    Publish /.well-known/security.txt with at least a Contact and an Expires line, for example Contact: mailto:security@example.com and Expires: 2027-12-31T23:59:59Z.

    View fix guide

What the security.txt check looks at

  • The file

    Fetched from /.well-known/security.txt on the domain and its www name.

  • Contact

    At least one Contact field, so a report has somewhere to go.

  • Expires

    Exactly one Expires date, in RFC 3339 form, that has not passed.

  • What is shown

    The file as your site serves it, up to its first 2,000 characters.

Optional fields such as Policy and Encryption are shown but not checked, and the contacts listed are never contacted.

Understand the issue and your next step

Each finding explains what we found, why it matters and what you can change. Start with the issues that need attention, then open the evidence when you want the detail.

  1. Enter your domain
  2. Review the findings
  3. Follow the fix guides
Example finding

security.txt is incomplete or expiredLow

A security.txt file exists but is missing a required field or has expired.

{
  "content": "Contact: mailto:security@example.com\nExpires: 2026-03-31T23:00:00Z\nPreferred-Languages: en\nCanonical: https://example.com/.well-known/security.txt",
  "status": 200
}

Common security.txt issues you can put right

  • No security.txtInformation

    Without the file, someone who finds a problem has no clear way to reach you. Publish a Contact and an Expires date at /.well-known/security.txt.

    Read the fix guide

  • security.txt is incomplete or expiredLow

    An expired or incomplete file tells researchers its contacts may be out of date. Add the missing field, or renew the Expires date before it passes.

    Read the fix guide

Keep watch after you've fixed it

Ironfang Security rechecks a verified domain every week or every day and tells you what changed: new findings, fixes and certificates nearing expiry.

Free during the preview. Domain verification required.

  1. NewIssue detected
  2. FixedConfirmed by recheck
  3. ReopenedDetected again

How the check works

  • https://<host>/.well-known/security.txt for the domain and its www. name, or the subdomain entered, following one redirect.
  • That the answer is a security.txt file: status 200, not an HTML page, and containing a Contact: line. A custom error page, or a site that answers every path with its home page, counts as no file.
  • At least one Contact field with a value, and exactly one Expires field.
  • That Expires is an RFC 3339 date, such as 2027-09-30T23:00:00Z, and has not passed.
  • The file as the site serves it, up to its first 2,000 characters.

Reading a result

security.txt (RFC 9116) is a plain text file at a fixed address that tells anyone who finds a security problem on your site how to report it. Without one, a report may go to a support queue that does not know what to do with it, or not be sent at all.

RFC 9116 requires at least one Contact and exactly one Expires. The expiry date exists so that a forgotten file stops being trusted: once it has passed, a researcher should assume the contacts may be out of date.

A missing file is a finding of informational severity; an incomplete or expired one is low. Neither is a weakness in the site itself. Both make it harder for someone to tell you about one.

What it does not do

  • Optional fields such as Policy, Encryption, Canonical, Acknowledgments and Preferred-Languages are shown in the file but not checked, and an OpenPGP signature is not verified.
  • It does not contact the addresses listed or test whether anyone answers.
  • Only /.well-known/security.txt is requested. A file at the older top-level location, /security.txt, is not read.
  • It does not judge how far ahead Expires is set. RFC 9116 recommends less than a year.

What happens to the domain you enter

The check runs from Ironfang Security's published scanner address with the same low-impact limits as a scan. Nothing you enter is stored or logged. A result is reused for five minutes, and a certificate log search for an hour, so a repeat check is quick and the domain is not checked again.

Guides

A few things worth knowing

What does a minimal security.txt look like?
Two lines: a Contact field, such as Contact: mailto:security@example.org, and an Expires date in RFC 3339 form, such as Expires: 2027-09-30T23:00:00Z. Serve it as plain text at /.well-known/security.txt over HTTPS.
How often should I update the Expires date?
RFC 9116 recommends an Expires date less than a year ahead. Review the file and renew the date before it passes.
Can Contact be a web form instead of an email address?
Yes. Contact takes a URI: mailto:, tel: or an https: address. A file can list several Contact lines, in order of preference.