DoiT · Vulnerability Disclosure

Doit Vulnerability Disclosure

Vulnerability disclosure

DoiT runs a coordinated vulnerability disclosure program on Hackerone. A machine-readable /.well-known/security.txt is served. A dedicated security contact is published.

CompanyFinOpsCloud Cost ManagementCloud IntelligenceCost OptimizationMulti-CloudKubernetesAnalyticsMCPArtificial Intelligence
Program: Hackerone security.txt present

Disclosure Policy

Policy
https://help.doit.com/docs/vendor-information/bug-bounty-program

Security Contact

Contact
mailto:vulnerability-report@doit.com

Source

Vulnerability Disclosure

Raw ↑ 
generated: '2026-08-12'
method: searched
probe: true
source: https://help.doit.com/docs/vendor-information/bug-bounty-program
program_name: Vulnerability Reward Program
program_type: self-hosted bug bounty / responsible disclosure
platform: null
platform_note: DoiT runs the program itself. It is not listed on HackerOne, Bugcrowd or
  Intigriti, and reports go to a DoiT mailbox rather than a platform intake.
policy:
- https://help.doit.com/docs/vendor-information/bug-bounty-program
contact:
- mailto:vulnerability-report@doit.com
scope: DoiT-owned web properties
terms:
  disclosure: Participants agree not to discuss or disclose ongoing work or vulnerabilities
    with parties outside the program without explicit DoiT consent; violation is immediate
    disqualification.
  impact_bar: Reports must demonstrate a real security risk with tangible business impact;
    theoretical risks requiring highly specific low-likelihood conditions are deprioritised
    and reports without measurable business impact are ineligible.
  test_accounts: Not provided.
security_txt:
  served: false
  note: No /.well-known/security.txt on www.doit.com, api.doit.com, help.doit.com or mcp.doit.com
    (all 404 on 2026-08-12). The program is discoverable only through the help centre
    and the Conveyor trust centre, not through the RFC 9116 machine-readable path.
related:
  security_policy: https://help.doit.com/docs/vendor-information/security-and-data-access-policy
  trust_center: https://trust.doit.com/
  penetration_testing: true
evidence:
- source: https://help.doit.com/docs/vendor-information/bug-bounty-program
  kind: disclosure page
  http_status: 200
  fetched: '2026-08-12'
- source: https://trust.doit.com/
  kind: trust center trust_indicator bug_bounty_resp_disclosure
  http_status: 200
  fetched: '2026-08-12'
  detail: report_vulnerability_url = mailto:vulnerability-report@doit.com
- source: https://www.doit.com/.well-known/security.txt
  kind: security.txt
  http_status: 404
  fetched: '2026-08-12'

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/doit-vulnerability-disclosure"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.