Skip to main content

Security report for meteo.lt

Lietuvos hidrometeorologijos tarnyba prie Aplinkos ministerijos · Government · Lithuania

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

Security score

65/100

Risk levelMedium

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

Meteo.lt is the official Lithuanian government meteorological service operated under the Ministry of Environment. It provides comprehensive weather forecasts, climate data, warnings, and meteorological monitoring services to the public and government agencies. The website is well-structured, professionally designed, and offers a wide range of meteorological information including real-time data, forecasts, and specialized services such as APIs and archival data access. The target audience includes general public users, businesses, and governmental bodies requiring accurate weather information. Technically, the website is built on WordPress and utilizes modern web technologies including jQuery and Google reCAPTCHA for form security. It implements GDPR-compliant cookie consent mechanisms with detailed user controls. The site is mobile-optimized and accessible, with good SEO practices and clear navigation. Performance is moderate, with room for optimization. From a security perspective, the site enforces HTTPS and uses Google reCAPTCHA to protect forms. However, it lacks visible security headers such as CSP or HSTS, which could enhance security posture. No vulnerabilities or exposed sensitive data were detected. The absence of WHOIS data for the .lt domain is noted but likely due to registry restrictions rather than malicious intent. Overall, Meteo.lt presents a trustworthy and professional government service website with strong privacy compliance and good technical implementation. Strategic improvements in security headers and publishing a security policy would further strengthen its security posture.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
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

7 findings rated critical or high. Fix these first.

  1. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

  2. 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';…

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

Keep watching meteo.lt

This scan found 23 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
70
Network security
100
GDPR outside view
40
Average
65

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

Meteo.lt holds a strong market position as Lithuania's official meteorological authority, providing essential weather and climate services. Its business model is public service oriented, funded and operated by the government. The website supports multiple user segments including citizens, businesses, and government agencies. Key competitive advantages include official status, comprehensive data offerings, and integration with international meteorological organizations such as WMO. The presence of APIs and archival data indicates a focus on data accessibility and transparency. Social media engagement and multilingual support enhance outreach. Growth indicators include recent news updates and mobile app promotion. The partnership ecosystem includes WMO and related meteorological data providers.

Security posture

The website demonstrates a mature security posture with HTTPS enforced and use of Google reCAPTCHA to mitigate automated abuse. Cookie consent is implemented with granular user controls, supporting GDPR compliance. However, the absence of key security headers (CSP, HSTS, X-Frame-Options) represents a gap that could expose the site to certain web-based attacks. No evidence of vulnerabilities or data leaks was found. Incident response and security policy information are not publicly available, which could hinder transparency and readiness. Publishing a security.txt file and incident response contacts would improve security culture and user trust. Overall, the site is secure but could benefit from enhanced security best practices.

Recommendations

  1. Implement and configure security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), X-Frame-Options, and X-XSS-Protection.
  2. Publish a clear security policy and incident response contact information on the website.
  3. Add a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  4. Regularly audit and update third-party libraries and plugins to avoid vulnerabilities.
  5. Enhance website performance optimization to improve user experience and reduce load times.

Contact details published on the site

Addresses
Legal name
Lietuvos hidrometeorologijos tarnyba prie Aplinkos ministerijos
VAT number
LT907432416
Registration number
290743240
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Lietuvos hidrometeorologijos tarnyba prie Aplinkos ministerijos
Description
Lithuanian government meteorological service providing weather forecasts, climate data, warnings, and related meteorological information.
Key services
Weather forecasts, Climate information, Meteorological warnings, Data APIs, Monitoring and archival data
Content quality
good
Branding
consistent

Technology

Stack
jQuery, WordPress, CookieYes (cookie consent), Google reCAPTCHA
Frameworks
WordPress
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent with granular controls
  • Google reCAPTCHA on forms

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Google Analytics (_ga cookie)
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content and multiple services
  2. Strong compliance with GDPR and cookie consent regulations
  3. Official government meteorological service with clear contact info
  4. Uses WordPress CMS with modern frontend technologies
  5. No visible security headers detected, room for improvement
  6. WHOIS data unavailable, but domain appears legitimate
  7. No signs of adult or questionable content
  8. Social media presence on major platforms
  9. Multiple subdomains for API and archival data
Technical notes

Notes

The website is built on WordPress CMS with jQuery and uses CookieYes for cookie consent management and Google reCAPTCHA for form protection. The site is mobile responsive and accessible, with good SEO metadata including Open Graph tags and alternate language links. Performance is moderate, with potential for improvement in loading speed. The technical stack is modern but could be enhanced by adding security headers and optimizing resource delivery. Hosting provider details are not explicitly found. The site uses multiple subdomains for API and archival services, indicating a modular infrastructure. Overall, the technical implementation supports the business needs effectively but has room for security and performance enhancements.
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 meteo.lt. 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 meteo.lt.

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.