Respond.io · Domain Security

Respond Domain Security

Domain security

Domain security posture for Respond.io, probed live across 3 host(s) and 1 registrable domain(s). 3 host(s) serve HTTPS (up to TLSv1.3); 1 advertise HSTS. Email/DNS controls: DNSSEC absent, SPF present, DMARC present (p=quarantine).

MessagingOmnichannelCustomer ConversationsWhatsAppAI

Transport & Host Security

respond.io
HTTPS: yes · TLS: TLSv1.3 · HSTS: no · cert expires: Sep 30 19:09:53 2026 GMT
developers.respond.io
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Sep 15 18:31:07 2026 GMT
api.respond.io
HTTPS: yes · TLS: TLSv1.3 · HSTS: no · cert expires: Nov 2 23:59:59 2026 GMT

Domain (DNS/Email) Security

respond.io
DNSSEC: no · SPF: yes · DMARC: yes (p=quarantine) · CAA: yes

Source

Domain Security

Raw ↑ 
generated: '2026-07-11'
method: probed
source: live DNS/TLS/HTTP probes of apis.yml + OpenAPI hosts
hosts:
- host: respond.io
  https: true
  tls_version: TLSv1.3
  cert_expires: Sep 30 19:09:53 2026 GMT
  hsts: false
- host: developers.respond.io
  https: true
  tls_version: TLSv1.3
  cert_expires: Sep 15 18:31:07 2026 GMT
  hsts: true
  hsts_max_age: 31536000
- host: api.respond.io
  https: true
  tls_version: TLSv1.3
  cert_expires: Nov  2 23:59:59 2026 GMT
  hsts: null
domains:
- domain: respond.io
  dnssec: false
  caa:
  - 0 issuewild "pki.goog; cansignhttpexchanges=yes"
  - 0 issuewild "ssl.com"
  - 0 issue "comodoca.com"
  - 0 issue "digicert.com; cansignhttpexchanges=yes"
  - 0 issue "letsencrypt.org"
  - 0 issue "pki.goog; cansignhttpexchanges=yes"
  spf: true
  dmarc: true
  dmarc_policy: quarantine