Skip to main content

Security report for openweathermap.org

OpenWeather Ltd. · Technology · United Kingdom

Medium risk. 5 critical or high findings in Security headers, SSL/TLS and 1 other check.

Security score

63/100

Risk levelMedium

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

OpenWeather Ltd. is a well-established UK-based company specializing in providing comprehensive weather data services globally. Their offerings include current, forecast, and historical weather data accessible via a variety of APIs, alongside specialized dashboards tailored for sectors such as renewable energy and extreme weather monitoring. The company targets developers and businesses requiring reliable and accurate meteorological information. Their market position is strong, supported by over a decade of domain presence and ISO certifications. Technically, the website employs modern web technologies including Bootstrap, Font Awesome, Google Fonts, and integrates analytics and error monitoring tools such as Google Analytics and Sentry. Hosting is managed via AWS infrastructure, ensuring scalability and reliability. The site is mobile-optimized with good SEO and accessibility features, though some improvements could be made in accessibility and security headers. From a security perspective, the site uses HTTPS and cookie consent mechanisms, with no visible exposed sensitive data or vulnerabilities. However, explicit incident response and vulnerability disclosure policies are not found, representing an area for enhancement. Privacy compliance is strong with comprehensive policies and GDPR-aligned consent banners. Overall, OpenWeather presents a professional, trustworthy, and technically sound web presence with a high level of business credibility. Strategic recommendations include enhancing security headers, publishing incident response details, and improving accessibility to further strengthen their security posture and user trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
95/ 100 · Low
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

5 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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • 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. 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.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

  3. DNS health

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

    • High

      Unregistered MX Record

      MX record points to unregistered domain: aspmx1.googlemail.com

      What to do: Remove or fix MX record pointing to unregistered domain

      • RFC 5321 §5.1
      • NIS2 21(2)(i)
      • IR 2024/2690 12.4: Implementing Regulation (EU) 2024/2690, Annex point 12.4: Asset inventory
      • NIST CM-8: NIST SP 800-53 Rev. 5 CM-8: System Component Inventory

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

Keep watching openweathermap.org

This scan found 22 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. 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
77
Security headers
15
Email security
85
DNS health
65
Network security
40
GDPR outside view
95
Average
63

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

OpenWeather operates in the technology and energy sectors, providing weather data APIs and dashboards that serve a global customer base including developers, businesses, and specialized industries like renewable energy. Their business model is subscription-based with pay-as-you-go options and a marketplace for prepared data sets. The company demonstrates competitive advantages through extensive data archives (46+ years), ISO certifications, and a broad product portfolio. Partnerships and related domains indicate a mature ecosystem supporting their services. Growth indicators include active social media presence and continuous product development. SecurityPosture: The company maintains a good security posture with HTTPS, cookie consent, and error monitoring. However, the absence of a public incident response or vulnerability disclosure policy suggests room for maturity. Compliance with GDPR is evident, but further transparency on data retention and incident handling would be beneficial. No critical vulnerabilities or suspicious patterns were detected. Recommendations include formalizing security policies, enhancing security headers, and expanding user support channels for security incidents.

Security posture

OpenWeather's security posture is solid with mandatory HTTPS usage, cookie consent mechanisms, and integration of Sentry for error tracking. The website does not expose sensitive information in its HTML content. However, the lack of visible security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options is a gap. No explicit incident response or vulnerability disclosure pages were found, which could hinder timely reporting and handling of security issues. GDPR compliance is well addressed through privacy and cookie policies. The company holds ISO 27001 certification, indicating adherence to recognized information security management standards. No known vulnerabilities or suspicious domains were detected. Overall, the security score is good but could be improved by implementing recommended headers and publishing clear security policies.

Recommendations

  1. Implement and enforce security headers including CSP, HSTS, and X-Frame-Options to mitigate common web vulnerabilities.
  2. Publish a dedicated incident response and vulnerability disclosure policy page to facilitate security issue reporting and management.
  3. Add a security.txt file at the root domain to standardize vulnerability disclosure contact information.
  4. Enhance website accessibility features to improve compliance with accessibility standards and user experience for all users.
  5. Regularly audit third-party scripts and dependencies to ensure no vulnerable libraries are included.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
OpenWeather Ltd.
Description
OpenWeather provides comprehensive weather data services, including current, forecast, and historical weather information. They offer a wide range of APIs for solar radiation, road risk assessment, solar energy prediction, and more with global coverage.
Key services
Current weather data, Forecast APIs (hourly, daily, climatic), Historical weather data, Weather maps, Specialized dashboards (Energy, Extreme Weather, General Weather Dashboard)
Content quality
excellent
Branding
consistent

Technology

Stack
Bootstrap 3.4.1, Font Awesome 4.7.0, Google Fonts (Oswald, Roboto), Google Analytics, Raven.js (Sentry error tracking), JavaScript, Vue.js (implied by data-v- scoped styles), Leaflet (for maps)
Frameworks
Bootstrap
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • Use of HTTPS
  • Cookie consent banner with opt-in/out
  • No exposed sensitive data in HTML
  • Use of Sentry for error monitoring

Analytics and tracking

Services
Google Analytics, Google Tag Manager, Sentry
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Sentry (Raven.js)
Transparency
good

Site quality

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

Key observations

  1. Website provides extensive weather data services with multiple API offerings and dashboards.
  2. Strong presence of trust indicators including ISO certifications and social media.
  3. Good privacy and cookie compliance with explicit banners and policies.
  4. Use of modern web technologies and analytics tools.
  5. No signs of blocking or WAF interference.
  6. No exposed sensitive data or obvious security vulnerabilities in the HTML content.
  7. Contact information is available primarily via email and support center links.
  8. No explicit incident response or vulnerability disclosure pages found.
Technical notes

Notes

The website is built using a combination of Bootstrap 3.4.1, Font Awesome 4.7.0, Google Fonts, and Vue.js components (inferred from scoped styles). It uses Leaflet for interactive maps and integrates Google Analytics and Sentry for analytics and error monitoring. Hosting is on AWS infrastructure, as indicated by DNS servers. The site is mobile-optimized with responsive design and includes SEO-friendly meta tags. Performance is moderate, with room for optimization in loading speed and accessibility. No CMS was detected, suggesting a custom or static site architecture. Technical risks are minimal but include the need for updated security headers and potential modernization of legacy libraries like Bootstrap 3.
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. 63/100Medium30 findingsView report
  2. 63/100Medium30 findingsView report
  3. 63/100Medium30 findingsView report
Reviews of this site

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

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.