Paubox · Vulnerability Disclosure

Paubox Vulnerability Disclosure

Vulnerability disclosure

NO PUBLISHED VULNERABILITY DISCLOSURE PROGRAM FOUND. This is a recorded absence, not a gap in the probe. It is written down because it is a real finding for a company whose product is healthcare security infrastructure.

Paubox publishes a vulnerability disclosure policy for reporting security issues.

EmailHIPAAHealthcareComplianceTransactional EmailEmail MarketingFormsSecurityEncryptionMessaging
Program:

Disclosure Policy

Security Contact

Source

Vulnerability Disclosure

Raw ↑
generated: '2026-08-26'
method: probed
source: >-
  Live probes of /.well-known/security.txt on www.paubox.com, api.paubox.com and
  docs.paubox.com; DNS CAA lookup on paubox.com; and a review of
  https://www.paubox.com/security and the published https://docs.paubox.com/llms.txt
  documentation index.
description: >-
  NO PUBLISHED VULNERABILITY DISCLOSURE PROGRAM FOUND. This is a recorded absence, not a
  gap in the probe. It is written down because it is a real finding for a company whose
  product is healthcare security infrastructure.
program_published: false
policy_url: null
bug_bounty: false
bug_bounty_platform: null
safe_harbor_statement: null

security_contact:
  found: true
  address: security@paubox.com
  discovered_via: >-
    CAA record on paubox.com — `0 iodef "mailto:security@paubox.com"`. This is a
    certificate-authority incident-reporting address, and it is the ONLY machine-readable
    security contact Paubox publishes. It is not a vulnerability disclosure policy and
    makes no commitment about response, scope or safe harbor.
  source: security/paubox-domain-security.yml

evidence:
  - url: https://www.paubox.com/.well-known/security.txt
    status: 404
  - url: https://api.paubox.com/.well-known/security.txt
    status: 404
  - url: https://docs.paubox.com/.well-known/security.txt
    status: 404
  - url: https://www.paubox.com/security
    status: 200
    note: >-
      Compliance narrative page (HIPAA/HITECH, encryption, AWS platform certifications).
      Contains no reporting instructions, no scope statement and no safe-harbor language.
  - url: https://docs.paubox.com/llms.txt
    status: 200
    note: >-
      Provider's own documentation index; contains no security, disclosure, responsible
      disclosure or bug-bounty page.

recommendation: >-
  RFC 9116 security.txt at https://www.paubox.com/.well-known/security.txt, naming the
  existing security@paubox.com address and linking a disclosure policy, would turn a
  contact that is currently only discoverable through a DNS CAA record into a
  machine-readable one.

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

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