What this page helps you understand
Responsible disclosure works when both sides keep users safe. This page explains what to include and what to avoid.
What Fixnx checks
Clear description
Proof steps
Affected URL
Impact
Safe testing
No data exposure
How to write a responsible vulnerability report
A useful report explains the affected area, the steps to reproduce, the impact, and the environment. Screenshots or short evidence summaries help, but raw secrets should not be included.
Do not access, modify, delete, or share data that does not belong to you. Avoid denial-of-service testing, social engineering, spam, and persistence.
Fixnx values clear, safe reports that help protect users and improve the product.
Run this check on your site
Enter a public URL and get a live Fixnx report with security, SEO, and performance checks.
Scan now. Google sign-in is only needed to unlock fix guidance.
FAQ
What should a disclosure include?
Include the affected URL or feature, reproduction steps, expected versus observed behavior, and potential impact.
Can I test on other users' data?
No. Only test with accounts and data you control.