Sectxt

<div align="center"> <h1>sectxt</h1> <h4 align="center"> The <a href="https://securitytxt.org/">security.txt standard</a> helps us make the Internet more secure. </h4> <p>sectxt lets you work with security.txt files on the command line.</p> </div> <p align="center"> <a href="https://github.com/eikendev/sectxt/actions"><img alt="Build status" src="https://img.shields.io/github/actions/workflow/status/eikendev/sectxt/main.yml?branch=main"/></a>&nbsp; <a href="https://github.com/eikendev/sectxt/blob/master/LICENSE"><img alt="License" src="https://img.shields.io/github/license/eikendev/sectxt"/></a>&nbsp; <a href="https://crates.io/crates/sectxt"><img alt="Version" src="https://img.shields.io/crates/v/sectxt"/></a>&nbsp; <a href="https://crates.io/crates/sectxt"><img alt="Downloads" src="https://img.shields.io/crates/d/sectxt"/></a>&nbsp; </p>

🚀 Installation

RUSTFLAGS="--cfg tracing_unstable" cargo install sectxt

Please refer to issue #15 for details.

📄 Usage

Feed sectxt a list of domains and it tells you which of them implement RFC 9116 correctly.

sectxt < domains.txt

👮 Acknowledgments

The idea was ~~shamelessly stolen from~~ inspired by haksecuritytxt. The main motivation was to play around with Rust's new async/await syntax and learn something new. Besides, sectxt enforces stricter checks against the RFC 9116.