Contact
Feedback, bug reports, tool requests and security disclosures are all welcome.
Who runs LocalSecTools
LocalSecTools is built, written and maintained by Asad Ali, an IT Support Engineer and SOC analyst who holds the Microsoft SC-200 Security Operations Analyst and ISC2 Certified in Cybersecurity (CC) certifications. He answers messages sent to support@localsectools.com himself. His official website, asadali.tech, lists his background and other projects, and you can also reach him through the profiles below.
How your message reaches us
Every message sent with this form, or with the feedback panel under each tool, is delivered as an email to the LocalSecTools support inbox at support@localsectools.com. The category you choose (general inquiry, tool bug report, feature request, security disclosure or advertising) is added to the subject line so requests can be sorted and answered in order. If you leave an email address, we reply to it directly; if you leave it empty, your message is still read but we have no way to answer you. You can also write to the address above from your own mail client, which works the same way.
Reporting a bug or a wrong calculation
The most useful bug reports name the tool, describe what you expected and what you saw instead, and include a minimal example that reproduces the problem: a sample CIDR block, a cron expression, a chmod mode or a CVSS vector. Please do not paste real tokens, production logs, internal IP plans or customer data into a report. A made-up value with the same shape is almost always enough to reproduce a calculation error, and it keeps your sensitive data out of email. Mention your browser and version if the problem looks like a display or layout issue.
Security disclosures
If you find a security issue in the site itself, choose the Security Disclosure category and describe the affected page and the steps to reproduce. Please give us reasonable time to fix the issue before publishing details.
Your privacy when you contact us
All ten tools run 100% client-side: calculations happen in your browser with standard Web APIs, and what you type into a tool is never sent to a server. This form is the only part of the site that sends data, and it sends only the fields you fill in here, together with the page address, your IP address and your browser’s user agent, which help us reproduce problems and block abuse. Tool inputs and outputs are never attached automatically. Submissions are rate-limited to protect the inbox from spam, and messages are kept only as long as needed to answer them. The privacy policy explains in detail what is collected and why.