Update on Bug Bounty Response Times
11/12/2026, 10:34:22 AM (about 13 hours ago)

Hi researchers,

Thank you for your continued submissions and contributions to our bug bounty program. We are currently experiencing a higher-than-usual volume of reports, which may lead to delays in our response and triage times. Please bear with us—our team is actively working through the queue and will review your reports as quickly as possible. We appreciate your patience and support!

Important Reminder: Testing Scope & Traffic Guidelines
11/9/2026, 1:28:01 PM (3 days ago)

Hi researchers,

To ensure platform availability and fair testing across both our Production and Testing Sandbox environments, please adhere strictly to our updated traffic, scanning, and authentication rules:

  • Mandatory Intigriti VPN: All testing activities must be conducted through the Intigriti WireGuard VPN. Requests originating from outside the VPN IP range will be blocked and will not be eligible for bounty rewards.
  • Identify Your Traffic (Mandatory Header): You must include the custom header x-intigriti-username: {username} in every request sent by your automated tools, scripts, and browsers.
  • Registered Researcher Email: Always register test accounts and perform test actions using your @intigriti.me email address.
  • No Excessive Scanning or Brute-Forcing: High-concurrency automated scanning and aggressive directory or content brute-forcing (such as unrestricted runs with ffuf, dirsearch, or gobuster) are strictly prohibited. Throttle all traffic to prevent service degradation.
  • Stick to the Scope: Always review and respect the target domains, endpoints, and exclusions explicitly defined in the program scope.

Failure to route traffic through the VPN, omitting the required header, or generating unthrottled excessive traffic may lead to immediate IP blocking, rejected submissions, or removal from the program.

Thank you for your cooperation in keeping our environments safe and stable. Happy hunting!