Closinglock · Vulnerability Disclosure

Closinglock Vulnerability Disclosure

Vulnerability disclosure

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

Real-EstateTitle InsuranceFraud PreventionPaymentsIdentity VerificationDocument-ManagementFintechComplianceSecurityCompany

Program: Hackerone security.txt present

Disclosure Policy

Security Contact

Contact

mailto:security@closinglock.com

Source

Vulnerability Disclosure

generated: '2026-08-09'
method: searched
probe: true
source: https://www.closinglock.com/.well-known/security.txt
program:
  published: true
  mechanism: security.txt
  policy_url: null
  bug_bounty: false
  bug_bounty_platform: null
  safe_harbor_statement: false
contact:
- mailto:security@closinglock.com
security_txt:
  url: https://www.closinglock.com/.well-known/security.txt
  http_status: 200
  content_type: text/plain; charset=utf-8
  canonical: https://closinglock.com/.well-known/security.txt
  expires: '2025-12-31T23:59:00Z'
  expired: true
  preferred_languages: en
  hiring: https://ats.rippling.com/closinglock/jobs
  fields_present:
  - Canonical
  - Contact
  - Expires
  - Hiring
  - Preferred-Languages
  fields_absent:
  - Policy
  - Encryption
  - Acknowledgments
  - CSAF
served_on_hosts:
- host: www.closinglock.com
  status: 200
- host: portal.closinglock.com
  status: 200
- host: trust.closinglock.com
  status: 200
findings:
- id: security-txt-expired
  severity: low
  detail: >-
    The Expires field reads 2025-12-31T23:59:00Z, which is in the past as of this probe
    (2026-08-09). RFC 9116 says a security.txt whose Expires date has passed should be
    considered stale and MUST NOT be used. The file is otherwise well-formed and is served
    consistently from all three reachable Closinglock hosts.
  remedy: Refresh the Expires field (RFC 9116 recommends a value less than a year out).
- id: no-policy-field
  severity: low
  detail: >-
    No Policy field and no published disclosure-policy page were found, so a researcher has a
    reporting address but no stated scope, timelines, or safe-harbor language.
  remedy: Publish a vulnerability disclosure policy page and reference it from the Policy field.
- id: no-bug-bounty
  severity: info
  detail: >-
    No HackerOne, Bugcrowd, Intigriti, or self-hosted bug bounty program was found for
    closinglock.com.
evidence:
- source: https://www.closinglock.com/.well-known/security.txt
  kind: security.txt
  http_status: 200
- source: https://www.closinglock.com/.well-known/kinlane-control-xyz.txt
  kind: control probe — confirms this host does not soft-404 well-known paths
  http_status: 404

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/closinglock-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.