generated: '2026-08-26'
method: probed
source: >-
  Probes of /.well-known/security.txt on www.nextw.com, apps.nextworld.net, console.nextworld.net,
  support.nextworld.net and community.nextw.com; searches of the compliance, trust-center and
  security-responsibilities pages; and checks for HackerOne / Bugcrowd / Intigriti programs.
name: Nextworld vulnerability disclosure
program_found: false
security_txt: false
bug_bounty: false
disclosure_page: false
note: >-
  Nextworld publishes no security.txt, no coordinated vulnerability disclosure policy, and no bug
  bounty program that could be found from a public surface. The only published security-adjacent
  contact is compliance@nextworld.net, which the compliance page scopes to SOC report and compliance
  questions — not to vulnerability reports. This is a recorded ABSENCE and no Security pointer is
  emitted for it.
evidence:
- url: https://www.nextw.com/.well-known/security.txt
  status: 404
- url: https://apps.nextworld.net/.well-known/security.txt
  status: 404
- url: https://console.nextworld.net/.well-known/security.txt
  status: 404
- url: https://support.nextworld.net/.well-known/security.txt
  status: 404
- url: https://community.nextw.com/.well-known/security.txt
  status: 404
- url: https://trust.nextw.com/.well-known/security.txt
  status: 403
  note: Cloudflare bot challenge, not a confirmed absence on that host.
- url: https://www.nextw.com/utility/compliance
  status: 200
  note: Names compliance@nextworld.net for SOC/compliance questions only.