security.txt check: tell researchers how to reach you

Short answer

security.txt is a small text file at /.well-known/security.txt that tells security researchers how to report a vulnerability to you privately (RFC 9116). It needs at least a Contact: line and an Expires: date. SiteShield passes a reachable plain-text file with a Contact line and warns otherwise (1 of 100 points).

DomainWorth 1 of 100 pointsBy Mumshad JawadUpdated

What is security.txt?

The file is plain text with one field per line. Contact (an email or URL) and Expires (a date, ideally less than a year ahead) are required by RFC 9116; Preferred-Languages, Policy, Acknowledgments and Canonical are optional.

Weak
/.well-known/security.txt → 404, or your HTML "Page not found" template
Good
Contact: mailto:security@example.com
Expires: 2027-10-01T00:00:00.000Z
Preferred-Languages: en, ar
Canonical: https://example.com/.well-known/security.txt

Why it matters

A security.txt file tells researchers how to report a vulnerability to you privately, instead of posting it publicly.

When someone finds a hole in your site, they need a quick, private way to tell you. Without one, reports get lost in general inboxes, go to social media, or aren't sent at all. It's a tiny file that signals you take security reports seriously.

SiteShield maps this check to:

RFC 9116

See how these standards fit together in the UAE website security checklist.

How SiteShield grades it

This check, "security.txt", can cost up to 1 points: a fail loses all 1, a warning loses 1. Every scan starts at 100.

ResultWhenPoints lost
Passhttps://<domain>/.well-known/security.txt returns a success status, contains a Contact: line and isn't an HTML page.0
WarningNo such file, or the URL returns an HTML page (many sites answer every unknown URL with their 404 template).1

How to check it yourself

curl -s https://example.com/.well-known/security.txt

Or run a free SiteShield scan, which checks this and 16 other settings in one go.

How to fix it

The quick version: Publish /.well-known/security.txt with at least: Contact: mailto:security@yourdomain and Expires: (a date within a year).

Write the file

Use an address you actually monitor, and put a reminder in your calendar to update Expires before it passes.

Contact: mailto:security@example.com
Expires: 2027-10-01T00:00:00.000Z
Preferred-Languages: en, ar

Nginx

Save the file as /var/www/security.txt and serve it as plain text:

location = /.well-known/security.txt {
    default_type text/plain;
    alias /var/www/security.txt;
}

Apache

Create a .well-known folder in the document root and put security.txt in it. Apache serves .txt files as text/plain by default.

Cloudflare

Put the file on your origin server as above, or, if the site runs on Cloudflare Workers or Pages, add it to the static files at /.well-known/security.txt.

WordPress

Upload the file over SFTP or your host's file manager to .well-known/security.txt in the WordPress root (next to wp-config.php). Then open the URL to confirm you get plain text, not your theme's 404 page.

FAQ

Does security.txt invite hackers?

No. It gives people who have already found something a responsible way to tell you. Attackers don't need an invitation, and the file reveals nothing about your systems.

Do I need a bug bounty to publish security.txt?

No. A contact address is enough. Policy and Acknowledgments are optional, and you don't have to pay for reports.

Test your security.txt now

Run all 17 checks on your website and email domain in about 30 seconds. Free, no signup, passive checks only.

Rather not do it yourself? Fix it for me starts at AED 750 (about USD 205 by PayPal), quote agreed first. Monitoring re-scans weekly for AED 99/month or AED 990/year.

Related checks

See all 17 security checks →