Skip to main content

Security report for medicare.gov

Centers for Medicare & Medicaid Services · Healthcare · United States

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

Security score

79/100

Risk levelLow

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

Medicare.gov is the official U.S. government website managed by the Centers for Medicare & Medicaid Services (CMS). It provides comprehensive information and services related to Medicare health insurance for people aged 65 or older and younger individuals with disabilities. The site offers key functionalities such as plan comparison, account management, provider lookup, fraud reporting, and customer support including live chat. It serves as a trusted authoritative source for Medicare-related information in the United States. Technically, the website is built on Drupal 10 CMS and leverages modern web technologies including Font Awesome icons, YouTube API for video content, and Tealium for tag management and analytics. The site is well-optimized for mobile devices and accessibility, featuring structured data (JSON-LD) for enhanced SEO and rich search results. Performance is moderate with asynchronous script loading to improve user experience. From a security perspective, the site enforces HTTPS and employs secure form practices including consent checkboxes. However, explicit security headers such as Content-Security-Policy and cookie consent mechanisms are not detected, representing areas for improvement. The WHOIS data is unavailable due to the .gov domain nature, but the domain's legitimacy is strongly supported by official branding, content, and government affiliation. Overall, Medicare.gov demonstrates a high level of professionalism, trustworthiness, and compliance with privacy standards. It effectively serves its target audience with clear navigation, relevant content, and multiple contact channels. Strategic recommendations include enhancing security headers, implementing cookie consent, and publishing security and incident response policies to further strengthen trust and compliance.

Scanned

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 medicare.gov

This scan found 17 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
100
Security headers
55
Email security
85
DNS health
80
Network security
100
GDPR outside view
53
Average
79

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

Medicare.gov holds a strong market position as the official government portal for Medicare services, targeting elderly and disabled populations in the U.S. Its business model is service-oriented, focusing on providing authoritative information and facilitating access to Medicare plans and providers. The site benefits from the backing of the U.S. Department of Health and Human Services, ensuring credibility and regulatory compliance. The presence of social media channels and integration with other government health sites indicates a broad partnership ecosystem. Growth indicators include continuous updates for open enrollment periods and educational initiatives such as fraud prevention. The website's enterprise scale and government affiliation position it as a critical resource in the healthcare sector.

Security posture

The security posture of Medicare.gov is solid with mandatory HTTPS encryption and secure handling of user inputs, including consent for data privacy. The absence of explicit security headers and cookie consent banners suggests room for enhancement in defense-in-depth strategies and regulatory compliance, particularly GDPR cookie consent. No vulnerabilities or exposed sensitive data were detected in the analyzed content. The lack of a published security policy or incident response contact limits transparency in security governance. Overall, the site maintains a mature security baseline appropriate for a government healthcare portal but should adopt additional best practices to mitigate emerging threats and compliance risks.

Recommendations

  1. Implement comprehensive security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  2. Deploy a cookie consent mechanism to comply fully with GDPR and other privacy regulations, improving user transparency and legal compliance.
  3. Publish a detailed security policy and incident response plan on the website to increase transparency and user trust.
  4. Introduce a vulnerability disclosure program or security.txt file to facilitate responsible reporting of security issues.
  5. Regularly audit third-party scripts and tracking technologies to minimize privacy risks and ensure compliance with data protection standards.

Contact details published on the site

Addresses
Legal name
Centers for Medicare & Medicaid Services
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Centers for Medicare & Medicaid Services
Description
The official U.S. government website for Medicare, a health insurance program for people age 65 or older and younger people with disabilities.
Key services
Medicare plan comparison, Account login and management, Care provider comparison, Fraud reporting, Customer support and live chat
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 10, Font Awesome 6 Pro, YouTube iframe API, Tealium tag management, jQuery, Ajax, JSON-LD structured data
Frameworks
Drupal CMS
Performance
moderate
Mobile
excellent
Accessibility
excellent
SEO
excellent

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Secure forms with required consent checkbox
  • Use of async and defer for scripts to improve performance

Analytics and tracking

Services
Tealium
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Tealium
Marketing tools
Tealium
Transparency
basic

Site quality

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

Key observations

  1. Official US government Medicare website
  2. Comprehensive Medicare information and services
  3. Uses Drupal CMS with modern frontend technologies
  4. No signs of malicious or suspicious content
  5. Good accessibility and mobile optimization
  6. Lacks explicit cookie consent mechanism
  7. WHOIS data unavailable but domain is .gov indicating high trust
  8. Includes social media presence on Twitter, Facebook, YouTube
  9. Includes structured data for SEO and rich results
  10. Includes multiple contact methods including phone and live chat
Technical notes

Notes

The website uses Drupal 10 CMS, a robust and widely supported content management system suitable for enterprise and government use. It integrates modern frontend technologies including Font Awesome for icons and asynchronous JavaScript loading for performance optimization. The site is mobile-optimized and accessible, adhering to best practices in web design and user experience. Performance is moderate, with potential for improvement through further optimization of resource loading and caching. The technical infrastructure reflects a mature digital presence with opportunities to enhance security and privacy controls. No hosting provider details were explicitly found in the content, but the domain's .gov status implies government-managed hosting.
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

Reviews of this site

Share your experience with medicare.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 medicare.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.