Skip to main content

Security report for healthcare.gov

HealthCare.gov · Government · United States

Medium risk. 3 critical or high findings in Security headers and GDPR outside view.

Security score

74/100

Risk levelMedium

0–100, higher is better. How it is calculated

HealthCare.gov is the official US government website providing access to the Health Insurance Marketplace®, enabling US residents to enroll in health insurance plans and access subsidies. It serves as a critical platform for healthcare coverage under federal regulations, positioning itself as the primary marketplace for millions of Americans. The website demonstrates a mature digital infrastructure built on modern technologies such as Gatsby and React, ensuring fast performance, mobile responsiveness, and accessibility compliance. Security is robust with HTTPS enforcement, comprehensive security headers, and no detected vulnerabilities in the provided content. Privacy policies and cookie consent mechanisms are well implemented, reflecting compliance with GDPR and US privacy standards. Overall, the site exhibits high professionalism, trustworthiness, and strong business credibility as a government entity.

Scanned

This is an earlier scan of healthcare.gov. View the latest report

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

3 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

Need hands-on remediation? Email guard@offseq.com

Keep watching healthcare.gov

This scan found 20 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
85
Security headers
55
Email security
70
DNS health
80
Network security
100
GDPR outside view
53
Average
74

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The website operates under the US Government, specifically related to healthcare services. Its business model is service-oriented, focusing on providing health insurance enrollment and information to the public. The platform leverages partnerships with the Department of Health and Human Services (HHS) and maintains a strong presence across social media channels for outreach. The marketplace targets US residents seeking affordable health insurance, offering plan comparisons and subsidy eligibility tools. The site’s enterprise scale and government backing provide significant market authority and trust. The absence of commercial advertising and affiliate programs aligns with its public service mission.

Security posture

HealthCare.gov exhibits a strong security posture with enforced HTTPS, modern security headers, and no exposed sensitive data in the HTML content. The site uses secure forms and input fields, minimizing risks of injection or data leakage. However, no explicit vulnerability disclosure or incident response contacts were found, which could be improved to enhance transparency and security readiness. The presence of FedRAMP certification indicates compliance with federal cloud security standards. Overall, the site is secure, but could benefit from publishing a vulnerability disclosure policy and incident response information to align with best practices.

Recommendations

  1. Publish a clear vulnerability disclosure policy and security.txt file to encourage responsible reporting.
  2. Enhance visibility of incident response contacts for security issues to improve trust and readiness.
  3. Maintain regular third-party script audits to prevent supply chain vulnerabilities.
  4. Continue updating and patching all dependencies and frameworks to mitigate emerging threats.
  5. Implement advanced user privacy controls and transparent data retention policies.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
HealthCare.gov
Description
Official government website providing access to the Health Insurance Marketplace® for health insurance coverage.
Key services
Health insurance enrollment, Marketplace information, Subsidy eligibility, Plan comparison
Content quality
excellent
Branding
consistent

Technology

Stack
Gatsby, React, JavaScript, CSS
Frameworks
Gatsby
Performance
fast
Mobile
excellent
Accessibility
excellent
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Security headers implemented
  • No exposed sensitive data in HTML
  • Secure forms with proper input types

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Transparency
good

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Official US government health insurance marketplace website
  2. High quality, accessible, and mobile-optimized content
  3. Strong security posture with modern best practices
  4. Comprehensive privacy and cookie policies present
  5. No suspicious or malicious content detected
  6. No WHOIS data available publicly, typical for government domains
Technical notes

Notes

The website is built using Gatsby, a React-based static site generator, which contributes to fast load times and excellent performance. The use of modern CSS and JavaScript frameworks ensures responsive design and accessibility compliance. The site is hosted on government infrastructure, likely with robust backend security and availability. SEO is well addressed with proper meta tags and Open Graph data. No CMS was detected, indicating a custom or static site approach. The technical implementation is modern and well maintained, with opportunities to further enhance security transparency and incident response capabilities.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Earlier scans of this domain

  1. 75/100 −1Medium27 findingsView report
  2. 76/100Low22 findingsView report
Reviews of this site

Share your experience with healthcare.gov. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review healthcare.gov.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.