Skip to main content

Security report for laac.lv

Latvijas Amerikas acu centrs · Healthcare · Latvia

Medium risk. 4 critical or high findings in Security headers and SSL/TLS.

Security score

60/100

Risk levelMedium

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

Latvijas Amerikas acu centrs is a healthcare service provider specializing in eye care and vision correction services, including state-funded eye surgeries and cataract operations. The website targets a Latvian-speaking audience and presents itself as a regional medical center focused on ophthalmology. The digital infrastructure is built on Joomla CMS with Bootstrap framework, leveraging modern web technologies such as jQuery, Google Tag Manager, Google Analytics, Facebook Pixel, and Cookiebot for cookie consent management. The site is mobile-optimized and provides multiple interactive forms for patient inquiries and service requests, indicating a moderate level of digital maturity. From a security perspective, the website enforces HTTPS and implements cookie consent mechanisms, which are positive indicators of privacy awareness. However, the absence of explicit security headers and a privacy policy page reduces the overall security posture. The lack of WHOIS data due to query limits restricts the ability to fully verify domain legitimacy and registration details. No direct contact information or security incident response channels were found, which could be improved to enhance trust and compliance. Overall, the website demonstrates a good level of professionalism and technical implementation suitable for a healthcare provider, but it would benefit from enhanced privacy disclosures, security header implementation, and clearer contact information to improve compliance and user trust. Strategic recommendations include publishing a comprehensive privacy policy, adding security.txt for vulnerability disclosures, and implementing standard security headers to strengthen the security posture.

Scanned

NIS2 and GDPR posture

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

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 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

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

Keep watching laac.lv

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. 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
62
Security headers
20
Email security
75
DNS health
80
Network security
40
GDPR outside view
83
Average
60

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

The business operates in the healthcare sector, specifically ophthalmology, serving the Latvian market. It appears to be a medium-sized entity focused on providing eye care services, including vision correction and state-funded surgeries. The business model is service-oriented, targeting patients requiring specialized eye treatments. The website content and structure suggest a stable regional presence with a focus on patient engagement through online forms. The use of third-party analytics and marketing tools indicates an interest in digital marketing and user behavior analysis. However, the absence of detailed business registration information and contact details online limits transparency. There is no evidence of parent or subsidiary companies, and no partner domains were identified. The company could enhance its competitive advantage by improving online trust signals and compliance documentation.

Security posture

The website maintains a basic to moderate security posture with HTTPS enabled and cookie consent implemented, reflecting compliance with common privacy regulations. The use of Google Tag Manager and Facebook Pixel introduces third-party tracking, which is disclosed via cookie consent but lacks a detailed privacy policy. No security headers such as Content-Security-Policy or X-Frame-Options were detected, which are recommended to mitigate common web vulnerabilities. The absence of a security.txt file and incident response contact channels indicates limited readiness for vulnerability reporting and incident management. No exposed sensitive data or vulnerable libraries were identified in the provided content. Overall, the security maturity is adequate for a healthcare website but requires improvements to meet higher compliance and security standards.

Recommendations

  1. Publish a comprehensive privacy policy page detailing data processing and GDPR compliance.
  2. Implement standard security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Add a security.txt file to facilitate vulnerability disclosure and improve incident response readiness.
  4. Provide clear and accessible contact information including security and general inquiry emails and phone numbers.
  5. Regularly audit and update third-party scripts and libraries to mitigate potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Latvijas Amerikas acu centrs
Description
Latvijas Amerikas acu centrs
Key services
eye care, vision correction, state funded eye surgery, cataract surgery
Content quality
good
Branding
consistent

Technology

Stack
jQuery, Bootstrap, Google Tag Manager, Google Analytics, Facebook Pixel, Cookiebot
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • Cookie consent implemented
  • Use of Google Tag Manager for controlled script loading

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
Meta Platforms, Inc.
Tracking pixels
Facebook Pixel
Marketing tools
Cookiebot
Transparency
good

Site quality

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

Key observations

  1. Website uses HTTPS and modern web technologies.
  2. Cookie consent is implemented with detailed cookie categories.
  3. Multiple forms present for user inquiries and service requests with client-side validation.
  4. No explicit privacy policy or terms of service pages found in the provided content.
  5. No direct contact emails or phone numbers found in the HTML content.
  6. Social media links not explicitly found in the provided content.
  7. WHOIS data unavailable due to query limit error.
  8. No security.txt or vulnerability disclosure information found.
  9. No data protection officer contact information found.
  10. Website content is in Latvian language targeting local audience.
Technical notes

Notes

The website is built on Joomla CMS using Bootstrap for responsive design and jQuery for client-side scripting. It integrates Google Tag Manager for managing analytics and marketing tags, Google Analytics for visitor tracking, and Facebook Pixel for retargeting. Cookiebot is used for cookie consent management, indicating attention to privacy compliance. The site loads multiple CSS and JS resources, some asynchronously, which supports moderate performance. Accessibility features are basic but present, with some ARIA roles and labels. SEO optimization is supported by meta tags and alternate hreflang links for multilingual support. Hosting provider details are not evident from the content. The site is mobile-optimized and uses modern web standards but could improve performance and accessibility further by optimizing scripts and enhancing semantic markup.
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 laac.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 laac.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.