Answers that don't need an email
A lot of questions are already answered on the site — these are the fastest routes:
- API questions — the API documentation covers authentication, every endpoint, rate limits and error codes, with copy-paste examples;
- Quotas, plans and pricing — see Plans & Pricing for what each tier includes;
- How to read a scan report — the blog has analyst guides to verdicts, redirect chains and the rest of the report;
- What Voretix is and how verdicts are produced — see the About page.
Reporting a malicious site
You don't need to email us about a phishing link — scan it with public visibility. That is the report: the page is detonated and preserved with its verdict, joins the public corpus, and becomes visible to every analyst using Search and Hunt.
Security vulnerabilities
If you believe you have found a security vulnerability in Voretix itself, email
[email protected] with
"Security report" in the subject line and enough detail to reproduce the issue.
The full Vulnerability Disclosure Policy covers scope, rules of
engagement, coordinated disclosure and the safe harbor for good-faith research, and a
machine-readable pointer is published at
/.well-known/security.txt.
What to include
Whatever the route, the more specific the message, the faster the answer. Where it applies, include the scan ID or report URL you are writing about, the account email or username involved, and — for API issues — the endpoint, the request you sent and the response you got back (with your API key redacted). We read everything, and messages that arrive on the right route get answered soonest.