Explore the example

Responsible security reporting

Protect people and data when reporting a suspected weakness.

Updated

Keep testing proportionate

Do not access another person’s data, change records, disrupt availability, use stolen credentials or continue exploitation after confirming a suspected issue. A public reporting page is not authorization for intrusive testing.

Report securely

Use a verified security contact published through the Contact page. Describe the affected URL, observed behavior and minimal steps needed to reproduce it. Avoid including secrets or personal information in an initial report.

Coordination

Allow an opportunity to investigate and address a credible report before publishing details that would expose people or systems. No payment, bounty or legal safe-harbour promise is created by this page.