Start with the surface.
For security research, application security conversations, or a considered question about a finding, email is the most direct route.
No contact form, no marketing list, no tracking. A direct message reaches the researcher.
For questions about a public note, include the note title and, where relevant, the program.
Good security conversations tend to start small: a system, a question, a constraint. You do not need a complete report to make the first message useful.
A useful first message.
Context matters more than length. The goal is to make the next step obvious for both sides.
- 01
Security findings
Include a short summary, the program or property involved, the impact you believe is relevant, and the safest way to continue. Do not include live exploit material in a first message.
- 02
Teams & reviews
Describe the surface, the scope, the constraints, and the decision you need to make. A short description of the system and what is authorized is enough to begin.
- 03
Recruiters & peers
Share the role, team, or research question, and what makes this work relevant. A link to the research is more useful than a long introduction.
Sensitive material
Do not send credentials, personal data, customer records, or live exploit material in a first email. If a secure channel is required, say so without including the sensitive details.