Skip to main content

Security report for imed.hr

Poliklinika i dnevna bolnica IMED · Healthcare · Croatia

Medium risk. 5 critical or high findings in Security headers, Email security and 3 other checks.

Security score

58/100

Risk levelMedium

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

Poliklinika i dnevna bolnica IMED is a specialized healthcare provider based in Croatia, focusing on complex dental cases and combining dental medicine, implantology, orthodontics, aesthetic surgery, and ENT services. The website reflects a professional and modern digital presence, leveraging Nuxt.js and Tailwind CSS frameworks, with integrated analytics and cookie consent mechanisms. The site is well-structured, mobile-optimized, and provides essential contact information, although explicit privacy and terms of service policies are missing. Security posture is good with HTTPS and security headers in place, but lacks published incident response or vulnerability disclosure policies. Overall, the business appears legitimate and trustworthy with a solid technical foundation but could improve compliance documentation and transparency.

Scanned

NIS2 and GDPR posture

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

5 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 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. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • High

      SPF DNS Lookup Limit Exceeded

      SPF record requires 12 DNS lookups (max 10)

      What to do: Reduce includes and mechanisms to stay under limit

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

  4. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • High

      Weak SPF Policy

      SPF record has permissive policy allowing any server to send email

      What to do: Use -all or ~all qualifier for better email security

  5. Network security

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

    • High

      High-Risk Service Exposed: FTP

      Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer

      What to do: Consider restricting access to FTP or implementing strong authentication

      • 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

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

Keep watching imed.hr

This scan found 23 issues across 5 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
72
Security headers
45
Email security
60
DNS health
50
Network security
20
GDPR outside view
100
Average
58

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

IMED positions itself as a niche healthcare provider specializing in dental and related medical services, targeting patients requiring advanced treatments. The business model is service-oriented, focusing on clinical care. The website's use of modern web technologies and analytics indicates a commitment to digital maturity. However, the absence of detailed privacy and security policies suggests areas for compliance enhancement. The company operates in Croatia with a small-sized footprint, and no parent or subsidiary relationships were identified. The marketing ecosystem includes standard analytics and cookie consent tools but no aggressive advertising or affiliate programs.

Security posture

The website enforces HTTPS and includes standard security headers, reflecting a good baseline security posture. Use of Cookiebot indicates GDPR awareness and consent management. No exposed sensitive data or vulnerable libraries were detected in the HTML content. However, the lack of publicly available security policies, incident response contacts, or vulnerability disclosure mechanisms represents a compliance and transparency gap. The site does not appear to be behind a WAF or security challenge, and no critical vulnerabilities were identified from the content analysis. Overall, security maturity is moderate with room for improvement in policy publication and incident readiness.

Recommendations

  1. Publish a comprehensive privacy policy and terms of service to improve legal compliance and user trust.
  2. Develop and disclose a security policy and incident response plan with clear contact channels.
  3. Implement a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  4. Enhance accessibility features to improve inclusivity and compliance with standards.
  5. Regularly review and audit third-party scripts and analytics tools to mitigate potential security risks.

Contact details published on the site

Addresses
Legal name
Poliklinika i dnevna bolnica IMED
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Poliklinika i dnevna bolnica IMED
Description
Stručnjaci za najteže dentalne slučajeve. Objedinjujemo dentalnu medicinu, implantologiju, ortodonciju, estetsku kirurgiju i ORL.
Key services
dental medicine, implantology, orthodontics, aesthetic surgery, ENT (ORL)
Content quality
good
Branding
consistent

Technology

Stack
Nuxt.js, Tailwind CSS, Google Analytics, Microsoft Clarity, Cookiebot
Frameworks
Vue.js, Nuxt.js
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Cookie consent implemented
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics, Microsoft Clarity
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Microsoft Clarity
Marketing tools
Cookiebot
Transparency
basic

Site quality

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

Key observations

  1. Website is professionally designed and focused on specialized dental and medical services.
  2. Cookie consent is implemented via Cookiebot, indicating GDPR awareness.
  3. No explicit privacy policy or terms of service pages found, which is a compliance gap.
  4. Use of modern web technologies (Nuxt.js, Tailwind CSS) and analytics tools.
  5. No signs of WAF or content blocking; site fully accessible.
  6. Contact information is present but could be more comprehensive (no emails found).
  7. No security or incident response policies publicly disclosed.
  8. No vulnerability disclosure or security.txt found.
Technical notes

Notes

The website is built using modern JavaScript frameworks (Nuxt.js with Vue.js) and styled with Tailwind CSS, indicating a contemporary and maintainable tech stack. Performance is moderate with preloading and module preloading of scripts. Analytics and tracking are implemented via Google Analytics and Microsoft Clarity, alongside Cookiebot for consent management. The site is mobile-optimized and SEO-friendly with appropriate meta tags and Open Graph data. Hosting provider details are not explicit but the presence of multiple scripts from sameorigin.net suggests a third-party service for bot detection or security. Technical risks are low but depend on maintaining third-party script security and adding missing compliance documentation.
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 imed.hr. 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 imed.hr.

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.