Superscale Vulnerability Disclosure

generated: '2026-08-12'
method: searched
probe: true
source: https://superscale.ai/.well-known/security.txt
contact:
- mailto:security@superscale.ai
policy: []
policy_note: >-
  No Policy: field, no responsible-disclosure page and no bug bounty program.
  Probed /security, /responsible-disclosure, /vulnerability-disclosure and
  /security/responsible-disclosure on superscale.ai — all return the Next.js SPA
  shell rather than a disclosure document. No HackerOne, Bugcrowd or Intigriti
  program was found.
security_txt:
  url: https://superscale.ai/.well-known/security.txt
  http_status: 200
  content_type: text/plain
  also_served_from: https://app.superscale.ai/.well-known/security.txt
  fields:
    contact: mailto:security@superscale.ai
    expires: '2026-08-08T23:59:00.000Z'
    preferred_languages: en,de
  expired: true
  expired_note: >-
    The document expired on 2026-08-08, four days before this probe on
    2026-08-12. RFC 9116 section 2.5.5 says a security.txt whose Expires date
    has passed should not be relied upon — a finder acting correctly would treat
    the contact as stale. Refreshing the Expires field is a one-line fix.
  missing_recommended_fields: [Policy, Encryption, Acknowledgments, Canonical, Hiring]
evidence:
- source: https://superscale.ai/.well-known/security.txt
  kind: security.txt (live probe)
  http_status: 200
  fetched: '2026-08-12'
- source: https://app.superscale.ai/.well-known/security.txt
  kind: security.txt (live probe, identical body)
  http_status: 200
  fetched: '2026-08-12'