Skip to main content

Security report for rrt.lt

Lietuvos Respublikos Ryšių reguliavimo tarnyba · Government · Lithuania

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

Security score

64/100

Risk levelMedium

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

Lietuvos Respublikos Ryšių reguliavimo tarnyba (RRT) is the national regulatory authority in Lithuania responsible for overseeing electronic communications, postal services, and railway transport markets. The agency provides regulatory oversight, consumer protection, spectrum management, and digital service regulation including emerging areas such as artificial intelligence. Positioned as a government entity, RRT serves Lithuanian citizens, service providers, and industry stakeholders with a comprehensive portfolio of regulatory functions. The website reflects a medium-sized government agency with a focus on transparency and public engagement.

Scanned

NIS2 and GDPR posture

GDPR outside view
10/ 100 · Critical
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

    • 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

  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 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 rrt.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
100
Security headers
25
Email security
80
DNS health
70
Network security
100
GDPR outside view
10
Average
64

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

RRT operates as a government regulatory body with a clear mandate in telecommunications and transportation sectors. Its business model is non-commercial, focusing on regulation, market oversight, and consumer protection. The agency maintains partnerships with various national and sector-specific organizations, as evidenced by linked partner domains. The website content and structure indicate a mature digital presence aimed at providing accessible information and services to the public and regulated entities. Growth indicators include expanding digital services regulation and active public consultations.

Security posture

The website demonstrates a solid security posture with enforced HTTPS and no visible exposure of sensitive data. However, it lacks some advanced security headers and does not publish a security.txt file or explicit vulnerability disclosure policy. The presence of cookie consent and use of reputable analytics tools indicate awareness of privacy and security best practices. Recommendations include enhancing HTTP security headers, publishing incident response contacts, and improving accessibility compliance to strengthen overall security maturity.

Recommendations

  1. Implement comprehensive security headers such as Content-Security-Policy and X-Frame-Options to mitigate common web attacks.
  2. Publish explicit privacy and terms of service pages to improve transparency and compliance with GDPR.
  3. Create and maintain a security.txt file to facilitate responsible vulnerability disclosure.
  4. Enhance accessibility features to meet WCAG standards and improve user experience for all visitors.
  5. Regularly audit third-party scripts and tracking tools to minimize privacy risks and ensure compliance.

Contact details published on the site

Addresses
Legal name
Lietuvos Respublikos ryšių reguliavimo tarnyba
VAT number
LT214422113
Registration number
1214 42211
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Lietuvos Respublikos Ryšių reguliavimo tarnyba
Description
Nacionalinė elektroninių ryšių, pašto ir geležinkelių transporto rinkų reguliavimo institucija.
Key services
Regulation of electronic communications, Postal services regulation, Railway transport market regulation, Consumer rights protection, Spectrum management, Certification and conformity assessment, Digital services oversight including AI regulation
Content quality
good
Branding
consistent

Technology

Stack
WordPress, jQuery, Google Tag Manager, Facebook Pixel
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of secure cookies consent banner

Analytics and tracking

Services
Google Analytics, Facebook Pixel
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Facebook Pixel, Google Analytics (via GTM)
Marketing tools
Facebook Pixel
Transparency
basic

Site quality

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

Key observations

  1. Website is a government regulatory agency site for Lithuania
  2. Content is comprehensive and well-structured
  3. No WHOIS data available for domain, possibly due to .lt registry restrictions or domain status
  4. HTTPS is enforced with modern tracking and analytics tools
  5. Cookie consent banner present with link to detailed cookie info
  6. No explicit privacy or terms of service pages found
  7. Contact information is clearly presented in footer
  8. No visible security.txt or vulnerability disclosure policy
  9. Social media presence on Facebook and LinkedIn
  10. No WAF or blocking detected, full content accessible
Technical notes

Notes

The website is built on WordPress CMS with jQuery and integrates Google Tag Manager and Facebook Pixel for analytics and marketing. The site is mobile-optimized with good SEO practices including meta tags and structured data in JSON-LD format. Performance is moderate with room for improvement in loading speed and accessibility. The absence of detailed hosting provider information limits full infrastructure assessment. Overall, the technical stack is modern and appropriate for a government regulatory website, but could benefit from enhanced security configurations and performance tuning.
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 rrt.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 rrt.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.