LetsGetChecked · Vulnerability Disclosure

Letsgetchecked Vulnerability Disclosure

Vulnerability disclosure

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

CompanyHealthHealthcareDiagnosticsLaboratoryTelehealthMedical TestingPharmacyOrdersResultsWebhooksHL7LOINC
Program: Hackerone security.txt present

Disclosure Policy

Policy

Security Contact

Contact
mailto:security@letsgetchecked.com

Source

Vulnerability Disclosure

letsgetchecked-vulnerability-disclosure.yml Raw ↑
generated: '2026-08-04'
method: searched
probe: true
source: https://www.letsgetchecked.com/security.txt

policy:
- https://www.letsgetchecked.com/terms-of-use/
contact:
- mailto:security@letsgetchecked.com
preferred_languages:
- en

security_txt:
  present: true
  url: https://www.letsgetchecked.com/security.txt
  http_status: 200
  content_type: text/plain
  file: well-known/letsgetchecked-security.txt
  canonical_location: false
  canonical_location_note: 'RFC 9116 requires /.well-known/security.txt. That path returns
    404 on every LetsGetChecked host; the document is served only from the pre-RFC
    root path /security.txt, so a conformant automated scanner will not find it.'
  expires: '2024-03-01T00:00:00.000Z'
  expired: true
  expired_note: 'The Expires field is more than two years in the past. RFC 9116 section
    2.5.5 says a security.txt with a past Expires value should be considered stale
    and must not be relied on; the contact address may no longer be monitored.'
  fields_present:
  - Contact
  - Expires
  - Preferred-Languages
  - Policy
  fields_absent:
  - Encryption
  - Acknowledgments
  - Canonical
  - Hiring
  - CSAF

bug_bounty:
  program: none-found
  platforms_checked:
  - HackerOne
  - Bugcrowd
  - Intigriti
  note: No public bug bounty or coordinated vulnerability disclosure programme was found.

policy_quality:
  dedicated_disclosure_page: false
  note: 'The Policy field points at the general Terms of Use, not at a vulnerability
    disclosure policy. No safe-harbour statement, scope definition, or response-time
    commitment is published.'

cross_reference:
  trust_center: security/letsgetchecked-trust-center.yml
  trust_center_report_vulnerability_url: https://www.letsgetchecked.com/security.txt

evidence:
- source: https://www.letsgetchecked.com/security.txt
  kind: security.txt
  http_status: 200
  fetched: '2026-08-04'
- source: https://trust.letsgetchecked.com/
  kind: trust-center quick link "Report a Vulnerability"
  http_status: 200
  fetched: '2026-08-04'
- source: https://www.letsgetchecked.com/.well-known/security.txt
  kind: canonical RFC 9116 path
  http_status: 404
  fetched: '2026-08-04'