Security.txt Workbench
Build or inspect supported security.txt contact and disclosure-policy fields.
Loading tool…
How to use Security.txt Workbench
Build or inspect supported security.txt contact and disclosure-policy fields. The workbench checks required Contact/Expires fields, single-line values, supported contact schemes and HTTPS policy links. It emits a separate file without hosting it or contacting any listed person.
- Provide field json or security.txt source.
- Choose the supported mode and run the tool. Review its assumptions and any reported errors.
- Copy the result or download a separate output; reset to clear the current form.
Good to know
- 10,000 characters and100 field lines. Supported fields only in Build; unknown inspection extensions are reported. Signed/PGP-armored files are unsupported.
- Expiry is parsed rather than judged against an implicit clock. Domain ownership, response readiness, contact delivery and actual hosting remain unverified.
- Inputs are processed on this device and are not automatically saved or uploaded.
Common questions
Does generating the file publish a vulnerability disclosure program?
No. It creates a text artifact with your supplied contact/policy values. You control hosting, ownership verification and the actual disclosure policy.
Does this change my original input?
No. The tool returns a separate result. Review that output before using it in another application.
Keep going with related tools
All seo →Robots.txt Generator
Build one crawler-rule group and optional sitemap lines with validated paths and URLs.
DeveloperHTTP Header Workbench
Parse ordered HTTP fields or export a validated JSON header list.
DeveloperURL Parser
Inspect HTTP(S) URL components, normalized hostnames, and repeated query parameters without visiting a link.