What to include
- The affected URL or component and when you observed the behavior.
- A clear description of the suspected impact.
- Minimal, non-destructive reproduction steps and redacted evidence.
- A way to contact you for clarification.
Protect people and systems
Do not access, modify or retain other people’s information. Avoid service disruption, social engineering, credential attacks and third-party systems. Stop if testing could cause harm and contact us to agree a safe next step.
Authorization and expectations
This contact page is not blanket permission to test and is not a bug-bounty or safe-harbor commitment. Agree any further validation with R53SEC. Do not send sensitive evidence until a secure exchange method has been arranged.
Email security@r53sec.in. Our machine-readable contact is available at /.well-known/security.txt.