Keyzra vulnerability disclosure policy Last updated: 2026-11-20 Canonical: https://keyzra.com/security-policy.txt We welcome reports of security vulnerabilities in Keyzra. This policy explains what is in scope, how to report, what you can expect from us, and how to research in good faith. 1. Scope In scope: - keyzra.com and its subdomains, including the website, the console and the API (/api/...) - the tools we publish: probe.py, the keyzra Python package and the Keyzra GitHub Action - the integrity of our published evidence: signed measurement runs, signatures and timestamps Out of scope: - services we use but do not operate: CDN, cloud and hosting providers, email providers - the post-quantum results of other organizations' servers in our public index; those are measurement findings, not vulnerabilities in Keyzra, and we notify the organizations concerned ourselves - denial of service, load or volume testing, spam, social engineering and physical attacks - findings that need an unlikely user interaction, a compromised device, or an outdated browser - missing security headers or best practices without a demonstrated impact 2. How to report Email security@keyzra.com with: - the affected URL, endpoint or component - the steps to reproduce, or a proof of concept - the impact you believe it has - how you would like to be credited, if at all If you need an encrypted channel, say so in your first email and we will arrange one. Please write in English. 3. What we commit to - Acknowledge your report within 3 business days. - Give you an initial assessment within 10 business days. - Keep you informed while we fix the issue, and tell you when it is fixed. - Credit you publicly once the fix is out, if you wish. - Not pursue or support legal action against research that follows this policy (see section 5). We do not run a paid bug bounty at this time. 4. Rules for good-faith research - Only test against your own account, data and resources. Access only the minimum data needed to show the problem; if you encounter data that belongs to someone else, stop, do not keep or share it, and tell us. - Do not degrade the service. Respect the rate limits; no denial of service and no high-volume automated scanning. - Do not modify or delete data, and do not use a vulnerability beyond what is needed to confirm it. - Give us reasonable time to fix the issue before any public disclosure. We aim for 90 days or less and will agree on a date with you. 5. Safe harbor If you make a good-faith effort to follow this policy, we consider your research authorized. We will work with you to understand and resolve the issue quickly, and we will not recommend or pursue legal action related to your research. If a third party takes legal action against you for activity that followed this policy, we will make it known that your actions were authorized by us. 6. Related - Contact file: https://keyzra.com/.well-known/security.txt - How we measure other organizations' servers, and how to opt out of our measurements: https://keyzra.com/#/scanning