Skip to main content

Security report for weather.gov

National Weather Service · Government · United States

Medium risk. 4 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

73/100

Risk levelMedium

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

The National Weather Service (NWS) website serves as the official platform for the NOAA National Weather Service, providing comprehensive weather forecasts, alerts, and safety information to the public and government agencies. As a US government entity under the Department of Commerce, the NWS holds a primary market position in weather-related services across the United States. The website targets a broad audience including the general public, emergency responders, and governmental bodies, offering critical services such as local and national weather forecasts, severe weather warnings, and educational resources. Technically, the website employs a mature infrastructure utilizing legacy but stable technologies like jQuery and jQuery UI, integrated with modern analytics tools such as Google Tag Manager and DigitalGov Analytics. The site is served over HTTPS, ensuring secure communications, and includes multiple external trusted domains for content and analytics. While the site performs moderately well, there is room for improvement in mobile optimization and accessibility to enhance user experience. From a security perspective, the site demonstrates good practices with HTTPS enforcement and no visible exposure of sensitive data. However, the absence of key security headers and a cookie consent mechanism indicates areas for enhancement to meet modern compliance standards. The lack of a published vulnerability disclosure or security.txt file and explicit incident response contacts suggests opportunities to improve transparency and incident readiness. Overall, the NWS website is a highly credible and trustworthy government resource with excellent content quality and professional presentation. Strategic improvements in privacy compliance, security headers, and mobile accessibility would further strengthen its security posture and user trust.

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

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"

  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

  3. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • High

      No SPF record found

      SPF helps prevent email spoofing

      What to do: Add SPF record: "v=spf1 include:_spf.yourmailprovider.com ~all"

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

Keep watching weather.gov

This scan found 19 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
70
Email security
50
DNS health
80
Network security
100
GDPR outside view
53
Average
73

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention weather.gov, from OffSeq Breach.

Total records
509
Employees
34
Customers
406
Third parties
69
Weak passwords
14%

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for weather.gov.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

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 Weather Service operates as a critical government agency providing essential weather information and warnings nationwide. Its market positioning as the authoritative weather source in the US is reinforced by its .gov domain and affiliation with NOAA and the Department of Commerce. The business model is service-oriented, focusing on public safety and information dissemination rather than commercial revenue. The website supports a wide ecosystem of partner domains including NOAA and commerce.gov, enhancing its reach and credibility. Growth indicators include active social media engagement and comprehensive service offerings. The absence of commercial advertising and affiliate programs aligns with its government service mandate.

Security posture

The security maturity of the NWS website is solid with mandatory HTTPS usage and no apparent exposure of sensitive information. The use of trusted external analytics and content delivery domains reduces risk. However, the lack of security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security represents a gap in defense-in-depth strategies. The missing cookie consent mechanism may pose compliance risks under privacy regulations. No explicit incident response or vulnerability disclosure information is provided, which could hinder rapid response to security events. Overall, the site is secure but would benefit from adopting additional best practices and transparency measures.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Strict-Transport-Security.
  2. Deploy a cookie consent banner/mechanism to comply with privacy regulations and inform users about tracking.
  3. Publish a vulnerability disclosure policy or security.txt file to enhance transparency and encourage responsible reporting.
  4. Provide explicit incident response contact information for security issues to improve readiness and trust.
  5. Enhance mobile responsiveness and accessibility features to improve user experience across devices.

Contact details published on the site

Addresses
Legal name
National Weather Service
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
National Weather Service
Description
NOAA National Weather Service providing weather forecasts, warnings, and safety information to protect life and property.
Key services
Weather forecasts, Weather alerts and warnings, Climate data, Safety information, Weather-related educational resources
Content quality
excellent
Branding
consistent

Technology

Stack
jQuery 1.10.2, jQuery UI 1.10.3, Google Tag Manager, YouTube iframe API, DAP DigitalGov Analytics
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of secure external scripts from trusted domains

Analytics and tracking

Services
Google Analytics, DAP DigitalGov Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Google Analytics (gtag.js), DAP DigitalGov Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is official US government weather service site.
  2. Content is comprehensive and relevant to weather forecasts and safety.
  3. No signs of malicious or suspicious content.
  4. WHOIS data is incomplete but domain is a .gov domain indicating government ownership.
  5. No cookie consent mechanism detected despite use of tracking scripts.
  6. Social media presence is strong with official accounts linked.
  7. No security.txt or explicit vulnerability disclosure found.
  8. No contact emails or phone numbers explicitly listed in HTML; contact form and physical address provided.
  9. Site uses HTTPS and modern analytics tools.
  10. Mobile optimization and accessibility could be improved.
Technical notes

Notes

The website uses a stable but somewhat dated technology stack centered on jQuery 1.10.2 and jQuery UI 1.10.3, supplemented by modern analytics tools like Google Tag Manager and DigitalGov Analytics. The site is served over HTTPS with external scripts loaded from trusted domains such as YouTube and Google. Performance is moderate with room for improvement in mobile optimization and accessibility. The absence of a detected CMS suggests a custom or government-developed platform. Technical risks include potential vulnerabilities from legacy libraries and missing security headers. Modernization opportunities include upgrading JavaScript libraries and enhancing compliance with privacy and security standards.
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. 74/100 +3Medium26 findingsView report
  2. 71/100Medium27 findingsView report
Reviews of this site

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