Co-Legal · Vulnerability Disclosure

Co Legal Be Vulnerability Disclosure

Vulnerability disclosure

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

LegalLegal ResearchTaxCase LawLegislationCompany RegistryVAT ValidationBelgiumNetherlandsEuropean UnionA2AMCPAgent-NativeArtificial IntelligenceLegal Tech

Program: Hackerone security.txt present

Disclosure Policy

Policy

https://co-legal.be/security.html

Policy

https://co-legal.be/security

Security Contact

Contact

mailto:contact@co-legal.be

Source

Vulnerability Disclosure

generated: '2026-09-19'
method: searched
probe: true
source: well-known/co-legal-be-security.txt
docs:
- https://co-legal.be/security
policy:
- https://co-legal.be/security.html
- https://co-legal.be/security
contact:
- mailto:contact@co-legal.be
preferred_languages: [nl, en]
expires: '2027-05-19T00:00:00.000Z'
canonical: https://co-legal.be/.well-known/security.txt
bug_bounty: false
evidence:
- source: well-known/co-legal-be-security.txt
  kind: security.txt (RFC 9116, fetched 2026-09-19 from https://co-legal.be/.well-known/security.txt, 200 text/plain)
  quote: "# We don't run a paid bug-bounty programme today, but we credit valid reports and respond fast. Contact: mailto:contact@co-legal.be / Expires: 2027-05-19T00:00:00.000Z / Preferred-Languages: nl, en / Canonical: https://co-legal.be/.well-known/security.txt / Policy: https://co-legal.be/security.html"
- source: https://co-legal.be/security.html
  http_status: 301
  redirect: https://co-legal.be/security
  note: The Policy URL in security.txt 301s to the extensionless page, which is live (200, text/html, 28,634 bytes).
- source: https://co-legal.be/security
  http_status: 200
  kind: security & data page
  quote: 'Security-melding, vulnerability-disclosure, vraag over deze pagina: contact@co-legal.be met "[SECURITY]" in het onderwerp. Onze RFC 9116 security.txt bevat dezelfde gegevens machine-leesbaar.'
  keywords: [vulnerability-disclosure, security-melding, security.txt, incident response]
note: >-
  A real, complete RFC 9116 file with a Policy page that resolves, a named contact, a one-year Expires, a
  Canonical self-reference and language preferences. The disclosure channel is e-mail with a "[SECURITY]"
  subject tag; there is no HackerOne/Bugcrowd/Intigriti programme and the file says so. The policy page also
  publishes the incident-response timeline (triage 0–4 h, partner notification 4–24 h, regulator assessment
  within 72 h, post-mortem within 14 days). Security pointer emitted at https://co-legal.be/security.

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/co-legal-be-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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