Mutiny · Domain Security

Mutiny Domain Security

Domain security

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

CompanyEnterpriseSalesMarketingGo-To-MarketArtificial IntelligenceAI AgentsSales EnablementAccount Based MarketingWorkflow AutomationModel Context Protocol

Transport & Host Security

www.mutinyhq.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Oct 24 09:30:55 2026 GMT
mcp.mutinyhq.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: no
status.mutinyhq.com
HTTPS: no · HSTS: no

Domain (DNS/Email) Security

mutinyhq.com
DNSSEC: no · SPF: yes · DMARC: yes (p=quarantine) · CAA: none

Source

Domain Security

mutiny-domain-security.yml Raw ↑ 
generated: '2026-08-13'
method: probed
source: live DNS/TLS/HTTP probes of apis.yml + OpenAPI hosts
hosts:
- host: www.mutinyhq.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Oct 24 09:30:55 2026 GMT
  hsts: true
  hsts_max_age: 31536000
- host: mcp.mutinyhq.com
  https: true
  tls_version: TLSv1.3
  hsts: false
  note: >-
    The MCP server host returns no Strict-Transport-Security header on any response (checked 2026-08-13
    on GET and POST /mcp). It does set a Content-Security-Policy of "default-src 'self'; connect-src
    'self' https://*.mutinyhq.com". This is the host that carries every authenticated agent call.
- host: status.mutinyhq.com
  https: false
  tls_error: certificate name mismatch
  note: >-
    CNAMEs to Atlassian Statuspage (2c8f8lzxjbxr.stspg-customer.com) but presents CN=*.statuspage.io,
    which does not cover status.mutinyhq.com — TLS validation fails for every conforming client. See
    lifecycle/mutiny-lifecycle.yml.
domains:
- domain: mutinyhq.com
  dnssec: false
  caa: []
  spf: true
  dmarc: true
  dmarc_policy: quarantine