Get in touch.
HexScan is maintained by a solo developer. Response times are usually within 24–48 hours. Bug reports and tool suggestions are especially welcome.
Found something broken? A tool that returns wrong results, a broken link, or a UI issue? Open a GitHub issue and I'll fix it fast.
→ Open GitHub issueMissing a security tool you use daily? Suggest it via GitHub Discussions or email. Good ideas get built — HexScan started as suggestions too.
→ GitHub DiscussionsFor anything that doesn't fit a GitHub issue — API questions, partnership inquiries, or general feedback. No spam, no newsletters.
→ draeneills@gmail.comAll tools are free and stay free. If HexScan saved you time, a small donation helps keep the APIs running and more tools coming.
→ Donate via PayPalYes. All 8 tools are free, require no login, and collect no personal data. The project is funded by optional donations and display ads. There is no premium tier.
No. Tools like the Password Generator and Base64 Decoder run entirely in your browser — nothing is sent to any server. The Breach Checker and IP Analyzer query third-party APIs (LeakCheck, ip-api) but HexScan does not log or store those queries. See the Privacy Policy for full details.
No. Tools like the Directory Exposure Checker and Subdomain Recon are for authorized testing only. Using them on systems you don't own or have written permission to test is illegal in most jurisdictions. Always get permission first. See Terms of Use.
Open a request on GitHub Discussions or send an email. Describe the tool, what it does, and why it would be useful for developers or security researchers. Good suggestions with clear use cases get prioritized.
Yes. HexScan is open source. You can view, fork, or contribute to the code on GitHub. Pull requests are welcome.