Rhapsody · Domain Security

Rhapsody Domain Security

Domain security

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

HealthcareUnited StatesInteroperabilityIntegration EngineFHIRHL7EMPITerminologyHealth DataMCPAPI Gateway

Transport & Host Security

rhapsody.health
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Nov 8 10:54:11 2026 GMT

Domain (DNS/Email) Security

rhapsody.health
DNSSEC: no · SPF: yes · DMARC: yes (p=quarantine) · CAA: none

Source

Domain Security

rhapsody-domain-security.yml Raw ↑ 
generated: '2026-08-14'
method: probed
source: live DNS/TLS/HTTP probes of apis.yml + OpenAPI hosts
hosts:
- host: rhapsody.health
  https: true
  tls_version: TLSv1.3
  cert_expires: Nov  8 10:54:11 2026 GMT
  hsts: true
  hsts_max_age: 31622400
domains:
- domain: rhapsody.health
  dnssec: false
  caa: []
  spf: true
  dmarc: true
  dmarc_policy: quarantine
  spf_note: >-
    The automated probe returned spf:false on 2026-08-14; verified by hand the
    same day with `dig +short TXT rhapsody.health`, which does return
    "v=spf1 mx ip4:54.240.69.246/32 ip4:54.240.69.247/32 ...". The domain
    publishes 32 TXT records and the probe's lookup truncated, so the false was a
    probe artifact, not a missing record. Corrected to true.