Skip to main content

Security report for arsmed.lv

Medicinas sabiedriba "ARS", SIA · Healthcare · Latvia

High risk. 10 critical or high findings in GDPR outside view, Network security and 2 other checks.

Security score

36/100

Risk levelHigh

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

Medicinas sabiedriba "ARS", SIA operates the website arsmed.lv, a Latvian healthcare center providing medical services. The website targets a general audience seeking healthcare in Latvia and is presented in Latvian with language options for English and Russian. The business appears to be a small local healthcare provider founded around 2016, with consistent branding and a professional online presence. Technically, the site uses WordPress with the Divi theme and common plugins such as Contact Form 7 and Yoast SEO, indicating a moderate level of digital maturity. The website is mobile-optimized and SEO-friendly but lacks explicit privacy and terms of service pages, which are important for compliance and trust.

Scanned

NIS2 and GDPR posture

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

10 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

  2. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
  3. 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 arsmed.lv

This scan found 29 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
47
Security headers
15
Email security
70
DNS health
60
Network security
0
GDPR outside view
25
Average
36

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 · found on this site
  • 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 company positions itself as a healthcare service provider in Latvia, leveraging a straightforward service model focused on medical care. The website content and WHOIS data align with a legitimate Latvian legal entity. The absence of detailed business certifications or partnerships suggests a focused local operation. The use of multilingual support indicates an intent to serve a broader regional audience. The business model is service-oriented, with revenue likely derived from patient services. Growth indicators or partnerships are not evident from the data provided.

Security posture

The website employs HTTPS, which is mandatory for secure communications. However, no security headers such as Content Security Policy or HSTS were detected, which could improve protection against common web attacks. The lack of explicit privacy policies and incident response information indicates gaps in compliance and security transparency. No vulnerabilities or exposed sensitive data were found in the analysis, but the absence of security best practices and policies suggests room for improvement. The security score is moderate, reflecting basic protections but missing advanced safeguards.

Recommendations

  1. Implement and publish a comprehensive privacy policy and terms of service to enhance compliance and user trust.
  2. Add security headers like CSP, HSTS, and X-Frame-Options to strengthen website security.
  3. Establish and disclose an incident response plan and vulnerability disclosure policy to improve security readiness.
  4. Ensure all forms have proper input validation and anti-CSRF protections to prevent exploitation.
  5. Regularly audit and update all CMS components and plugins to mitigate vulnerabilities.

Contact details published on the site

Addresses
Legal name
Medicinas sabiedriba "ARS", SIA
Registration number
40103021886
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Medicinas sabiedriba "ARS", SIA
Description
Medicīnas centrs ARS
Key services
medical services
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Divi theme, Contact Form 7, Yoast SEO, Google Fonts
Frameworks
WordPress
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
60/100
Good practices seen
  • HTTPS implied by canonical URL

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Marketing tools
Yoast SEO
Transparency
basic

Site quality

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

Key observations

  1. Website is a healthcare service provider based in Latvia.
  2. Content is in Latvian with language alternates for English and Russian.
  3. Uses WordPress CMS with Divi theme and common plugins.
  4. No explicit privacy or terms of service pages found.
  5. Cookie consent mechanism is present.
  6. No exposed emails or phone numbers found in the HTML content provided.
  7. WHOIS data is partially incomplete but shows legitimate registrant info.
  8. No security headers detected in the provided data.
  9. No signs of WAF or blocking mechanisms.
  10. No adult or questionable content detected.
Technical notes

Notes

The website is built on WordPress using the Divi theme, a popular and flexible CMS platform. It uses standard plugins for SEO and contact forms, indicating a conventional but effective technical stack. Performance is moderate, with Google Fonts and external resources loaded. Mobile optimization is good, and SEO metadata is well implemented with Open Graph and JSON-LD structured data. However, the absence of advanced security headers and incomplete WHOIS data suggest some technical debt and potential risks. Hosting provider details are not disclosed, limiting full infrastructure assessment.
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 arsmed.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 arsmed.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.