Skip to main content

Security report for 911.gov

National 911 Program · Government · United States

Partial score · DNS & email only

49/100

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

The National 911 Program website (911.gov) serves as the official U.S. government portal providing leadership, coordination, and resources related to 911 emergency services. It is managed under the National Highway Traffic Safety Administration (NHTSA) and targets public safety officials, emergency communication professionals, and the general public. The site offers comprehensive information on current projects, important issues, webinars, newsletters, and various resources to support and promote optimal 911 services nationwide. Technically, the website employs modern web technologies including HTML5, CSS3 with Tailwind CSS, JavaScript with Alpine.js, and integrates Google Tag Manager for analytics. The site is mobile-optimized, accessible, and demonstrates good SEO practices. It uses HTTPS exclusively, ensuring secure communication. From a security perspective, the site follows best practices such as secure forms and encrypted connections. However, it lacks explicit security headers and a security.txt file, which could enhance its security posture. Privacy compliance is strong with a comprehensive privacy policy linked to the parent transportation department, though no cookie consent mechanism was detected. Overall, the website is trustworthy, professional, and authoritative, with no signs of malicious activity or content blocking. The lack of WHOIS data is typical for government domains and does not detract from its legitimacy. Strategic recommendations include adding security headers, implementing a cookie consent mechanism, and publishing incident response contacts to further strengthen security and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
Checks completed
6of 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. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • Critical

      Unable to retrieve SSL certificate

      Could not establish secure connection to retrieve certificate information

      What to do: Check if the server is accessible and SSL/TLS is properly configured

  2. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • Critical

      Domain Expired

      Domain expired 126 days ago

      What to do: Renew domain registration immediately

  3. 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 911.gov

This scan found 14 issues across 5 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. The full timeline opens with your unlock code.

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
0
Email security
70
DNS health
30
Network security
100
GDPR outside view
53
Average
51
After the cap
49

Not counted

  • Security headers: did not complete in this scan.
  • 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 · found on this site
  • 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 National 911 Program operates as a critical government entity within the transportation and public safety sectors. It holds a strong market position as the authoritative source for 911 emergency communication leadership and resources in the United States. The program's business model is non-commercial, focusing on federal coordination, policy support, and community engagement through educational content and funding initiatives. Its partnership ecosystem includes various government agencies and stakeholders in emergency communications. The website's content and structure indicate a mature digital presence with ongoing initiatives such as NG911 and cybersecurity awareness, reflecting growth and adaptation to evolving public safety needs.

Security posture

The website demonstrates a mature security posture with mandatory HTTPS usage and secure form handling. The presence of a vulnerability disclosure policy linked from the parent department indicates a proactive approach to security. However, the absence of explicit security headers like Content-Security-Policy and the lack of a security.txt file represent areas for improvement. No vulnerabilities or exposed sensitive data were detected in the HTML content. Incident response contact information is not publicly visible, which could be enhanced to improve transparency and readiness. Overall, the site aligns well with government security standards but could benefit from additional hardening measures.

Recommendations

  1. Implement HTTP security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to enhance protection against common web attacks.
  2. Add a security.txt file at the root of the domain to facilitate responsible vulnerability disclosure and improve security communication.
  3. Introduce a cookie consent banner or mechanism if cookies are used to comply with privacy regulations and enhance user trust.
  4. Publish clear incident response contact information on the website to improve transparency and facilitate security incident reporting.
  5. Regularly review and update third-party scripts and analytics tools to minimize potential security risks and ensure compliance.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
National 911 Program
Description
911.gov is the home of the National 911 Program, which provides federal leadership and coordination in supporting and promoting optimal 9-1-1 services.
Key services
Federal leadership and coordination of 911 services, Providing resources and tools for 911 community, Promoting Next Generation 911 (NG911) initiatives, Hosting webinars and newsletters, Supporting legislation and policy development
Content quality
excellent
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, Alpine.js, Google Tag Manager
Frameworks
Tailwind CSS
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Secure forms with proper labels
  • No exposed sensitive data in HTML
  • Use of Google Tag Manager for analytics

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

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 resources on 911 emergency services
  3. No signs of malicious or suspicious content
  4. No WHOIS data available due to privacy or registry restrictions
  5. Good mobile and accessibility support
  6. Use of modern frontend technologies and Google Tag Manager
  7. No cookie consent mechanism detected
  8. No direct phone numbers found, only email and physical address
  9. No social media links explicitly found in HTML content
Technical notes

Notes

The website is built using modern frontend technologies including Tailwind CSS for styling and Alpine.js for interactivity, indicating a contemporary and maintainable codebase. Google Tag Manager is used for analytics, suggesting centralized management of tracking scripts. The site is mobile-optimized and accessible, with semantic HTML and ARIA attributes supporting usability. Performance appears moderate, with no obvious blocking scripts or heavy resources detected in the HTML. The absence of a detected CMS suggests a custom or static site architecture, which can reduce attack surface but requires disciplined maintenance. Opportunities exist to improve security headers and implement a cookie consent mechanism to align with best practices and regulatory requirements.
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 911.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 911.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.