Tridge Domain Security

generated: '2026-08-30'
method: probed
source: live DNS/TLS/HTTP probes of every Tridge host discovered during enrichment (apis.yml declares
  no baseURL, so the extra hosts were probed by hand and are recorded with the same method)
hosts:
- host: www.tridge.com
  https: true
  tls_version: TLSv1.2
  cert_expires: Dec 27 23:59:59 2026 GMT
  hsts: false
- host: api.tridge.com
  https: true
  tls_version: TLSv1.2
  cert_expires: Dec 27 23:59:59 2026 GMT
  hsts: false
  note: GraphQL surface host; root returns 404 and /graphql returns 403 "crc rejected" to anonymous callers.
- host: accounts.tridge.com
  https: true
  tls_version: TLSv1.2
  cert_expires: Dec 27 23:59:59 2026 GMT
  hsts: false
  note: OAuth 2.0 authorization server host (/oauth/authorize, /oauth/token). No HSTS on an authentication
    host.
- host: app.tridge.com
  https: true
  tls_version: TLSv1.2
  cert_expires: Dec 23 23:59:59 2026 GMT
  hsts: false
  note: Single-page web application; catch-all answers 200 text/html for every path.
- host: blog.tridge.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Nov  8 11:22:03 2026 GMT
  hsts: true
  hsts_max_age: 31536000
  note: The only Tridge host observed serving HSTS, and the only one negotiating TLS 1.3 — it is externally
    hosted, not part of the core platform.
domains:
- domain: tridge.com
  dnssec: false
  caa: []
  spf: true
  spf_record: v=spf1 include:_spf.mlsend.com a mx include:spf.mtasv.net  include:servers.mcsv.net include:_spf.google.com
    include:amazonses.com include:41698150.spf02.hubspotemail.net  ~all
  dmarc: true
  dmarc_policy: quarantine
  dmarc_record: v=DMARC1; p=quarantine; pct=100; rua=mailto:re+houm4bhpeoi@dmarc.postmarkapp.com; sp=none;
    aspf=r;
findings:
- No CAA record on tridge.com — any public CA may issue for the domain.
- DNSSEC is not enabled on tridge.com.
- No HSTS on www.tridge.com, api.tridge.com, accounts.tridge.com or app.tridge.com; the OAuth authorization
  host in particular carries no Strict-Transport-Security header.
- Core platform hosts negotiate TLS 1.2 (not 1.3); only the externally hosted blog negotiates TLS 1.3.
- SPF and DMARC are published; DMARC policy is p=quarantine with sp=none, so subdomains are not covered
  by the parent policy.