Skip to main content

Security report for mil.lv

Nacionālie bruņotie spēki · Government · Latvia

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

Security score

63/100

Risk levelMedium

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

The website mil.lv serves as the official online presence of the Latvian National Armed Forces, providing comprehensive information about military service, training, reserve forces, and national defense news. It targets Latvian citizens interested in military careers and national security, positioning itself as a key government resource. The site leverages Drupal 9 CMS and integrates analytics tools such as Matomo and Facebook Pixel, indicating a moderate level of digital maturity. However, the absence of a valid SSL certificate and HTTPS support is a critical security flaw that undermines user trust and data protection. While security headers are properly configured, the lack of modern TLS protocols and domain security features like DNSSEC and domain locks further weaken the security posture. The website includes links to multiple official government and military partner domains, reinforcing its legitimacy. Privacy and cookie policies are present but lack advanced consent mechanisms and GDPR compliance indicators. Overall, the site is functional and professional but requires urgent security improvements to meet modern standards.

Scanned

This is an earlier scan of mil.lv. View the latest report

NIS2 and GDPR posture

GDPR outside view
0/ 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

6 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

    • 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

  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 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 mil.lv

This scan found 24 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
90
Security headers
55
Email security
65
DNS health
70
Network security
100
GDPR outside view
0
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

Mil.lv operates as a government entity website under the Latvian Ministry of Defense, focusing on national defense communication and recruitment. Its business model is non-commercial, aimed at public service and information dissemination. The site maintains strong partnerships with related defense and security organizations, enhancing its ecosystem. The content is well-structured and relevant to its audience, with clear navigation and multilingual support. Growth indicators include active news updates and multimedia content. The absence of direct contact information and limited privacy compliance features suggest areas for operational enhancement. The site’s market position is authoritative within the Latvian defense sector, serving as a primary information hub for military affairs.

Security posture

The security posture of mil.lv is currently weak due to the lack of a valid SSL certificate and HTTPS support, which is a critical vulnerability for any modern website, especially a government site. While several security headers are implemented correctly, the absence of TLS protocols, OCSP stapling, and domain security mechanisms like DNSSEC and CAA records exposes the site to potential risks. No incident response or security policy information is publicly available, limiting transparency and preparedness. The site uses tracking technologies that require careful privacy management. Immediate remediation of SSL issues and enhancement of domain security controls are essential to improve trust and compliance.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 or TLS 1.3) and configure OCSP stapling for improved security and performance.
  3. Implement DNSSEC and CAA records to strengthen domain name system security.
  4. Add domain protection locks in WHOIS to prevent unauthorized domain changes.
  5. Publish clear security policies and incident response contact information to enhance transparency.
  6. Improve privacy compliance by implementing explicit cookie consent mechanisms and GDPR-aligned privacy policies.
Technical notes

Notes

The website is built on Drupal 9, a modern and widely used CMS, indicating a solid technical foundation. It uses Matomo and Facebook Pixel for analytics and tracking, showing an intent to monitor user engagement. The site’s performance is currently slow, possibly due to hosting or configuration issues. Mobile optimization is good, with responsive design and accessibility features present but basic. SEO is well addressed with proper meta tags and Open Graph data. However, the lack of HTTPS and SSL support is a major technical deficiency that impacts security and user trust. Hosting appears to be managed by Latvian government infrastructure, which should facilitate compliance and security improvements. Overall, the technical stack is modern but requires urgent security upgrades.
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. 59/100 −8Medium37 findingsView report
  2. 67/100Medium27 findingsView report
Reviews of this site

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

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.