| 开发者 | jbsabit |
|---|---|
| 更新时间 | 2026年11月11日 11:05 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
security.txt file (RFC 9116, the internet standard for publishing security contact information) at /.well-known/security.txt, exactly where security researchers and bug bounty hunters look first.
In short: install VulnLine, and your WordPress site publishes a standard security contact file at https://yoursite.com/.well-known/security.txt — with your contact details, an expiry date, and your vulnerability disclosure policy — valid the moment you activate it, with zero configuration.
What is a security.txt file?
A security.txt file is a small plain-text file that tells anyone who finds a security problem on your website how to report it to you responsibly. It is defined by the IETF in RFC 9116 (published 2022) and lives at one fixed address: /.well-known/security.txt, served over HTTPS as text/plain. Think of it as robots.txt for security researchers: a machine-readable signpost that says "found a vulnerability? Here is how to tell us."
What you get
security.txt served automatically at /.well-known/security.txt with the correct text/plain content type — no file editing, no FTP, no server configmailto:, https://, tel:Contact and Expires are required by RFC 9116. VulnLine generates this file for you, keeps the format correct, and updates it the moment you save your settings.
Why your WordPress site needs a security.txt
/.well-known/security.txt first; without one, many simply move on — or disclose publicly.well-known folder and upload a text file by FTP — if you have filesystem access and get every detail right. In practice, hand-made files break silently: the folder is lost in a site migration, the file is served as text/html instead of text/plain, the Expires date passes unnoticed, or the file is edited into an invalid format. VulnLine serves security.txt dynamically through WordPress, validates it against RFC 9116 every time you save, and warns you in the dashboard if anything is wrong — including an Expires date that is about to lapse.
Privacy
This plugin collects nothing, phones home nowhere, and adds zero front-end weight — it only serves one tiny text file when requested.
Built by WordPress security specialist Md Jahid Bin Sabit — jbsabit.com
/wp-content/plugins/vulnline/, or install through the WordPress plugins screen.yoursite.com/.well-known/security.txt to see it live.A security.txt file is a plain-text file, defined by RFC 9116, that tells security researchers how to report a vulnerability in your website. It is published at /.well-known/security.txt and must contain at least a Contact field (where to send reports) and an Expires field (when the information goes stale).
At https://yoursite.com/.well-known/security.txt — that is the only location RFC 9116 requires, served over HTTPS with the content type text/plain. VulnLine serves it at exactly that address automatically; you do not create folders or upload files.
No. WordPress core does not generate a security.txt file, and most hosts do not add one either. Without a plugin or a manually uploaded file, /.well-known/security.txt on a WordPress site returns a 404 — which is the gap VulnLine fills.
Install VulnLine and activate it. WordPress cannot write a real file to /.well-known/ by itself, so the plugin serves security.txt dynamically at that exact URL with the correct text/plain content type — no FTP, cPanel, file manager or .htaccess edits needed.
Two fields are required by RFC 9116: Contact (a mailto:, https:// or tel: URI that a human actually reads) and Expires (a future date, ideally less than a year ahead). Optional fields are Encryption (your PGP key), Policy (your disclosure policy page), Preferred-Languages, Acknowledgments, Hiring and Canonical. VulnLine's settings screen covers all of them.
No — RFC 9116 is a voluntary standard, not a law. That said, it is mandatory for Dutch government organisations, recommended by security agencies such as the UK NCSC, and the direction of regulation (for example the EU Cyber Resilience Act's coordinated-disclosure requirements) is toward every product and site having a published security contact. Having one costs nothing and takes a minute.
Different audiences. robots.txt tells search-engine crawlers which pages they may index. security.txt tells security researchers how to contact you about vulnerabilities. They live in different places, too: robots.txt sits in the root, security.txt belongs at /.well-known/security.txt.
No. On activation VulnLine fills in ready-to-use defaults — your site admin email as the Contact, an Expires date one year ahead, and your site language — so the file is valid and live immediately. Change anything you like under Settings → VulnLine.
Yes, if you have FTP or file-manager access: create a .well-known folder in your web root and upload a correctly formatted security.txt file. The plugin route is safer for most sites — it guarantees the text/plain content type, validates the format, survives migrations and theme changes, and reminds you before the Expires date lapses.
Yes. Researchers check /.well-known/security.txt first — it is machine-readable and unambiguous, unlike a contact form buried three clicks deep. VulnLine also links your existing policy page in the Policy field, so the two work together.
Open yoursite.com/.well-known/security.txt — you should see plain text, not a 404 or a web page. VulnLine goes further: it validates every save against RFC 9116, shows a live status (valid / action needed) on its settings screen, and warns you in the dashboard if the file ever becomes invalid.
Researchers treat the file as stale and may not trust or use the contact details. VulnLine shows a countdown on its settings screen and warns you in the dashboard if your file is missing or invalid — set a calendar reminder to renew the date yearly.
Because that is what it is: a direct line for vulnerability reports. When a researcher finds a bug, VulnLine makes sure they can reach you — through the standard security.txt file (RFC 9116) at /.well-known/security.txt.
The file is served dynamically through WordPress. If you use aggressive full-page caching, exclude the /.well-known/security.txt path so updates appear immediately.
No. Nothing loads on the front end; the plugin only responds when /.well-known/security.txt itself is requested.