Contact
Questions, corrections, and security reports.
This page routes you to the operator of this deployment. There is no contact form backend in the default application, so messages are only accepted through the configured channel.
Contact channel
No public contact email is configured.
The deployment operator has not set NEXT_PUBLIC_CONTACT_EMAIL. Use the contact channel provided by whoever hosts or shared this site. This is not a failure of the scanner; the deployment simply has no public mailbox configured.
Operators can set a public address in the environment and restart the application. No contact form data is collected or stored by the default app.
What to include
- Report issues: the report link, scanned URL, timestamp, and a description of what looks incorrect.
- False positives: the report link and any public evidence that explains the site's legitimate purpose.
- Security reports: the affected endpoint, reproduction steps, and impact. Do not include live secrets.
- Privacy requests: the report link or approximate scan time so the record can be located.
Security disclosure
Report suspected SSRF bypasses, secret exposure, injection issues, or data leakage privately to the operator. Do not test against systems you do not own or have permission to assess.
False positives
Heuristics can be wrong. A lookalike domain, new registration, or suspicious phrase can have a legitimate explanation. Reports include the evidence so it can be reviewed.
Never send passwords, API keys, wallet recovery phrases, full card numbers, or other live secrets in a support message. The scanner does not need them to review a report.
Looking for a report?
Reports are accessed through the link returned after a scan and expire automatically.