Skip to main content

Security report for ssa.gov

Social Security Administration · Government · United States

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

Security score

72/100

Risk levelMedium

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

The Social Security Administration (SSA) website serves as the official digital presence of the U.S. government agency responsible for administering Social Security programs. It provides comprehensive information and services related to retirement, disability, Medicare, and other social insurance benefits. The site targets U.S. residents and citizens seeking authoritative guidance and access to benefits. The SSA holds a strong market position as the primary federal agency in this domain, with a long-established history dating back to 1935. Technically, the website is built on Drupal 10, leveraging modern web technologies including Google Tag Manager and New Relic for analytics and performance monitoring. The site demonstrates excellent mobile optimization, accessibility, and SEO practices, ensuring a high-quality user experience. Security is robust, with HTTPS enforced, multiple security headers present, and no visible vulnerabilities or exposed sensitive data. Privacy compliance is well addressed with clear policies and cookie consent mechanisms. The security posture is strong, though the site could benefit from publishing explicit security policies, incident response contacts, and vulnerability disclosure information to enhance transparency and trust. The WHOIS data is privacy protected, which is typical for government domains, but the .gov TLD and consistent official branding strongly affirm legitimacy. Overall, the SSA website is a highly professional, secure, and trustworthy government resource. Strategic recommendations include enhancing security transparency, adding vulnerability disclosure channels, and maintaining rigorous third-party script audits to sustain security and compliance standards.

Scanned

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

NIS2 and GDPR posture

GDPR outside view
58/ 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

4 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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 ssa.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
95
Security headers
30
Email security
70
DNS health
80
Network security
100
GDPR outside view
58
Average
72

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

SSA operates as a critical government entity providing essential social insurance services to millions of Americans. Its business model is non-commercial, focused on public service delivery. The website supports multiple languages, reflecting inclusivity and broad accessibility. SSA's partnership ecosystem includes related government domains such as USA.gov and the Office of the Inspector General. The site’s digital maturity is high, with integrated analytics and performance tools indicating ongoing optimization efforts. Growth indicators include recent updates and active news sections. The agency’s operations are transparent and aligned with federal standards, reinforcing its authoritative market presence.

Security posture

The SSA website exhibits a mature security posture with enforced HTTPS, comprehensive security headers, and no detected vulnerabilities in the publicly accessible content. Privacy policies and cookie consent mechanisms align with GDPR and other privacy regulations. However, the absence of explicit security policies, incident response contacts, and vulnerability disclosure mechanisms represents a compliance gap. The site’s use of third-party analytics and monitoring tools is standard but requires continuous oversight to mitigate supply chain risks. Overall, the security culture appears strong but could be improved by enhancing transparency and formalizing incident response communications.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and standards.
  2. Establish and publicize a vulnerability disclosure program or security.txt file.
  3. Provide clear incident response contact information for security issues.
  4. Regularly audit and update third-party scripts to prevent supply chain vulnerabilities.
  5. Enhance user trust by detailing data protection officer contacts and certifications.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Social Security Administration
Description
Official website of the U.S. Social Security Administration providing information and services related to Social Security benefits, Medicare, and related programs.
Key services
Benefit eligibility checking, Benefit application, Medicare sign-up and management, Benefit management and payment services, Social Security card and number services
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 10, Google Tag Manager, New Relic Browser Agent, BOOMR (Boomerang) performance monitoring, js-cookie
Frameworks
Drupal CMS
Performance
fast
Mobile
excellent
Accessibility
excellent
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Use of security headers
  • No exposed sensitive data in HTML
  • Secure forms with CSRF tokens (implied by Drupal)
  • Privacy policy and cookie consent mechanisms

Analytics and tracking

Services
Google Tag Manager, New Relic Browser Agent, Boomerang
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
New Relic Browser Agent, Boomerang (performance monitoring)
Transparency
basic

Site quality

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

Key observations

  1. Official U.S. government website with .gov domain
  2. Comprehensive multilingual support
  3. Strong emphasis on accessibility and privacy
  4. Use of modern web technologies and performance monitoring
  5. No signs of malicious or suspicious content
  6. No direct contact emails or phone numbers visible on homepage; contact via official contact page
  7. No explicit terms of service page found
  8. Privacy and cookie policies are present and comprehensive
Technical notes

Notes

The website is powered by Drupal 10, a modern and secure CMS platform widely used in government. It integrates Google Tag Manager and New Relic for analytics and performance monitoring, indicating a mature digital infrastructure. The site is well-optimized for mobile devices and accessibility, adhering to federal standards. Performance monitoring scripts like Boomerang are used to ensure fast load times. The hosting provider is not explicitly identified but is likely a government or government-approved cloud provider. The technical implementation reflects a balance of security, performance, and usability suitable for a high-traffic government portal.
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. 56/100 −17Medium27 findingsView report
  2. 73/100Medium27 findingsView report
Reviews of this site

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