generated: '2026-08-13' method: searched probe: true note: >- NextRoll runs a Responsible Disclosure programme published on its SafeBase trust portal, with a dedicated reporting mailbox. It does NOT serve an RFC 9116 security.txt on any host probed (see well-known/adroll-well-known.yml), so the programme is discoverable only by a human reading the trust portal — an automated scanner following the standard path finds nothing. policy: - https://security.nextroll.com/ contact: - security@nextroll.com report_mechanism: kind: email address: security@nextroll.com subject_template: 'SafeBase Responsible Disclosure Report for NextRoll' source: https://security.nextroll.com/ bug_bounty: public_program: false platform: null note: >- No public HackerOne/Bugcrowd/Intigriti bounty programme was found. HackerOne appears on the trust portal as the auditor of NextRoll's penetration test report, which is a pentest engagement, not an open bounty. penetration_testing: published: true vendor: HackerOne artifact: Pentest Report (available on request through SafeBase) security_txt: served: false hosts_probed: [www.adroll.com, www.nextroll.com, services.adroll.com, srv.adroll.com, apidocs.nextroll.com, app.adroll.com, developers.nextroll.com] results: '404 on adroll.com/nextroll.com/apidocs/srv, 504 on services.adroll.com, 200-HTML-SPA-shell (not a document) on app.adroll.com and developers.nextroll.com' recommendation: >- Publishing /.well-known/security.txt on www.nextroll.com and www.adroll.com with Contact: mailto:security@nextroll.com and Policy: https://security.nextroll.com/ would make the existing programme machine-discoverable at zero policy cost. evidence: - source: https://security.nextroll.com/ kind: trust-portal http_status: 200 finding: 'Responsible Disclosure section with mailto:security@nextroll.com' - source: https://www.nextroll.com/trust-center kind: trust-page http_status: 200 - source: /.well-known/security.txt across 7 hosts kind: probe finding: no document served x-evidence: checked: '2026-08-13'