Temple Health · Domain Security

Temple Health Domain Security

Domain security

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

Academic Medical CenterCMS InteroperabilityCures ActDSTU2EpicFHIRFox Chase Cancer CenterHL7HealthcareHospital SystemMyChartAuthenticationPatient AccessPrice TransparencyR4SMART on FHIRTemple UniversityUS CoreUSCDI

Transport & Host Security

www.templehealth.org
HTTPS: yes · TLS: TLSv1.3 · HSTS: no · cert expires: Nov 12 00:46:51 2026 GMT
epicaccess.templehealth.org
HTTPS: yes · TLS: TLSv1.2 · HSTS: no · cert expires: Feb 2 23:59:59 2027 GMT

Domain (DNS/Email) Security

templehealth.org
DNSSEC: no · SPF: yes · DMARC: yes (p=reject) · CAA: yes

Source

Domain Security

Raw ↑ 
generated: '2026-08-15'
method: probed
source: live DNS/TLS/HTTP probes of apis.yml + OpenAPI hosts
hosts:
- host: www.templehealth.org
  https: true
  tls_version: TLSv1.3
  cert_expires: Nov 12 00:46:51 2026 GMT
  hsts: false
- host: epicaccess.templehealth.org
  https: true
  tls_version: TLSv1.2
  cert_expires: Feb  2 23:59:59 2027 GMT
  hsts: false
domains:
- domain: templehealth.org
  dnssec: false
  caa:
  - 0 issue "letsencrypt.org"
  - 0 issue "digicert.com"
  - 0 issue "entrust.net"
  spf: true
  dmarc: true
  dmarc_policy: reject
notes:
- 'HSTS discrepancy, observed 2026-08-15: the mechanical probe records hsts:false for epicaccess.templehealth.org
  because the origin-root 404 page carries no HSTS header. The FHIR API paths on that same host DO return
  "strict-transport-security: max-age=31536000; includeSubDomains" on both 200 and 401 responses. The
  API surface is HSTS-protected; the host root is not.'
- 'my.templehealth.org (the myTempleHealth/MyChart portal) is not in the probed host list because it is
  carried as a PatientPortal property rather than a baseURL. Probed separately 2026-08-15: HTTPS, TLSv1.2,
  HSTS present with max-age 31536000.'
- No security.txt on any Temple Health host, so no RFC 9116 contact exists for reporting a finding against
  these hosts. See well-known/temple-health-well-known.yml.

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/temple-health-domain-security"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.