The Site HOUND project takes security seriously. We encourage responsible disclosure of vulnerabilities to ensure the safety of users and the integrity of the project.

The following versions of Site HOUND are currently supported with security updates:

⚠️ Always use the latest version to stay protected.

If you discover a security vulnerability, please do not disclose it publicly.

Instead, report it responsibly:

• 📧 Email: bcs.team.oficial@gmail.com
• 💬 GitHub Issues: Use private reporting (if available)
• 🔐 Facebook (Private Message): Bangladesh Cyber Squad

To help us investigate quickly, include:

• 📌 Description of the vulnerability
• 🎯 Affected component (module, function, feature)
• 🔁 Steps to reproduce
• 💥 Potential impact
• 📎 Proof-of-concept (if possible)

We aim to respond as quickly as possible.

We follow a responsible disclosure approach:

• ❌ No public disclosure before fix
• ✅ Coordinated disclosure after patch
• 🤝 Credit will be given (if requested)

This policy applies to:

• Core fuzzing engine (site-hound.py)
• Wordlist processing system
• Header spoofing engine
• Async request handling
• Output & logging system

The following are not considered vulnerabilities:

• Misuse of the tool
• Scanning without permission
• Target-side vulnerabilities
• Rate limiting or blocking by target servers

• ✔ Use only on authorized targets
• ✔ Avoid aggressive scanning on production systems
• ✔ Use rate limiting to prevent disruption
• ✔ Respect legal and ethical boundaries

This tool is intended for educational and authorized security testing only.

The maintainers are not responsible for:

• misuse of the tool
• illegal activities
• damage caused by improper usage

We appreciate responsible security researchers who help improve this project.

“Security is not a feature — it is a responsibility.”