Security and reporting vulnerabilities
If you find a vulnerability in Arablyzer, send it to us before you publish it. We thank everyone who reports in good faith.
Last updated
On this page
How to report
Write to [email protected] with what you found and the page or request, the steps to repeat it, and its impact in your view. Do not attach real people’s data. If you want an encrypted channel, ask for it in your first message. We aim to reply within five working days and to tell you what we decide.
The file /.well-known/security.txt has the same address in the form tools read.
What is in scope
- The arablyzer.com site and its paths, the
/apiinterface, the public API (v1) and the MCP server. - The GitHub Action and the Chrome extension that Arablyzer makes.
Out of scope: vulnerabilities in the sites that visitors scan (tell their owners), social engineering, flooding the service with requests, output of automated scanners with no proven impact, and “best practice” remarks with no security effect.
Rules for safe research
- Do not access, change or delete other people’s data beyond what is needed to prove the vulnerability.
- Do not disrupt the service or try to flood it.
- Give us reasonable time to fix before you publish details.
As long as you act in good faith and by these rules, we will not take legal action over your research.
What we do to protect the service
- Strict egress rules: a scan cannot reach internal networks or metadata addresses, and all outside connections go through an egress proxy.
- The site’s interface accepts state-changing requests only from its own origin and as JSON, and a content security policy (CSP) is on every page.
- We do not store Google tokens: the Search Console token is temporary and revoked as soon as it is used.
- Nor do we store Bing tokens: the Bing Webmaster Tools tokens are used for one reading, then dropped.
- We keep API keys and deletion tokens as fingerprints only, limit requests, and check visitors with Turnstile.