generated: '2026-08-06'
method: probed
source: live DNS/TLS/HTTP probes of apis.yml + OpenAPI hosts
hosts:
- host: www.barogo.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Dec  2 23:59:59 2026 GMT
  hsts: false
- host: developer.gorelas.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Oct  7 23:59:59 2026 GMT
  hsts: false
- host: api-interlocker.gorelas.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Oct  7 23:59:59 2026 GMT
  hsts: null
- host: staging-api-interlocker.gorelas.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Oct  7 23:59:59 2026 GMT
  hsts: null
domains:
- domain: barogo.com
  dnssec: false
  caa: []
  spf: true
  spf_record: v=spf1 ip4:18.168.51.200 ip4:18.168.140.58 include:mail.stibee.com include:spf.protection.outlook.com
    include:amazonses.com ~all
  dmarc: false
  dmarc_policy: null
- domain: gorelas.com
  dnssec: false
  caa: []
  spf: false
  dmarc: false
  dmarc_policy: null
findings:
- No HSTS on any host, including the production API host and the developer portal.
- No CAA record on either domain, so certificate issuance is unconstrained.
- No DNSSEC on either domain.
- barogo.com publishes SPF but no DMARC record, so there is no policy on spoofed mail from the
  brand domain. gorelas.com — the domain that carries the API, the developer portal and the
  admin consoles — publishes neither SPF nor DMARC.
- TLS 1.3 with valid certificates everywhere probed. That part is clean.
corrections:
- field: barogo.com dnssec / caa
  detail: >-
    An automated pass initially recorded dnssec:true and a CAA value of
    "production-homepage-lb-2000987377.ap-northeast-2.elb.amazonaws.com." for barogo.com. That
    is wrong. barogo.com is a CNAME at the apex pointing at an AWS ELB, so `dig DNSKEY` and
    `dig CAA` both follow the CNAME and echo the target hostname. Re-verified directly: no
    DNSKEY, no CAA record. Corrected to false / [].
  corrected: '2026-08-06'
x-evidence:
  fetched: '2026-08-06'
  method: dig + TLS handshake + HTTP HEAD