Skip to main content

Security report for paranice.nl

Nice Software B.V. · Healthcare · Netherlands

Partial score · DNS & email only

28/100

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

Nice Software B.V. operates the paranice.nl website, providing specialized software solutions for paramedical care, medical specialist rehabilitation, and geriatric rehabilitation in the Netherlands. Their offerings include electronic patient dossiers (EPD), planning, declaration management, and mobile applications tailored to healthcare providers. The company targets healthcare institutions such as hospitals, rehabilitation centers, and care organizations, positioning itself as an established player with a mature domain and active partnerships. The website content is professional, well-structured, and provides clear contact channels, supporting a positive business image. Technically, the website uses a traditional web stack with jQuery, Bootstrap, and several JavaScript libraries. Hosting and domain registration are managed by Claranet Benelux B.V., a reputable provider. However, the site lacks a valid SSL certificate and does not support HTTPS, which is a significant security and trust concern. The site implements Google Analytics and Google reCAPTCHA v3 for analytics and bot protection, and it includes GDPR-compliant privacy and cookie policies with consent mechanisms. From a security perspective, the absence of HTTPS and modern TLS protocols severely impacts the security posture. Minimal security headers and lack of DNSSEC or domain protection locks further reduce security confidence. While forms use reCAPTCHA and secure cookies, the overall security configuration is basic and requires urgent improvement to protect user data and maintain trust. Overall, the website is functional and business-appropriate but suffers from critical security shortcomings. Addressing SSL/TLS issues and enhancing security headers would significantly improve the security posture and user trust. The business appears legitimate and established, but the security gaps present risks that should be prioritized.

Scanned

NIS2 and GDPR posture

GDPR outside view
0/ 100 · Critical
Checks completed
6of 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

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

    • Critical

      Unable to retrieve SSL certificate

      Could not establish secure connection to retrieve certificate information

      What to do: Check if the server is accessible and SSL/TLS is properly configured

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

Keep watching paranice.nl

This scan found 14 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
0
Email security
50
DNS health
70
Network security
20
GDPR outside view
0
Average
28

Not counted

  • Security headers: did not complete in this scan.
  • 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 company targets a niche healthcare software market focused on paramedical and rehabilitation care in the Netherlands. Their business model is B2B software provision with a focus on compliance with healthcare regulations and efficient care administration. The mature domain age and active partner logos indicate stable market presence. The company leverages digital marketing tools like Google Analytics and maintains GDPR compliance, which supports customer trust. However, the lack of HTTPS may hinder customer confidence and limit growth opportunities. The partnership ecosystem includes Data Access Europe, which likely supports development and hosting. The company’s growth potential depends on modernizing its technical infrastructure and improving security to meet industry standards.

Security posture

The current security posture is weak due to the absence of HTTPS and valid SSL certificates, exposing users to potential data interception risks. The lack of modern TLS protocols and HSTS implementation further weakens transport security. DNSSEC is not enabled, and domain protection locks are missing, increasing risk of domain hijacking. Security headers are minimal, and no vulnerability disclosures or incident response contacts are provided. The use of Google reCAPTCHA and secure cookie flags are positive controls. Overall, the site is vulnerable to man-in-the-middle attacks and lacks advanced security controls, which could impact compliance with GDPR and healthcare data protection requirements.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site immediately.
  2. Enable modern TLS protocols (TLS 1.2 or 1.3) and disable all insecure protocols (SSL2, SSL3, TLS1.0, TLS1.1).
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  4. Enable DNSSEC to protect DNS integrity and prevent spoofing.
  5. Add domain protection locks to prevent unauthorized domain transfers.
  6. Enhance security headers including Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy.
  7. Update JavaScript libraries to current secure versions to mitigate known vulnerabilities.
  8. Publish an incident response policy and contact channels for security issues.
  9. Consider adding a terms of service page to clarify user agreements.
  10. Maintain and regularly review privacy and cookie policies to ensure ongoing GDPR compliance.
Technical notes

Notes

The website is built on a classic web stack using jQuery 1.12.0, jQuery UI, Bootstrap, and Cycle2 plugins, indicating a traditional but somewhat outdated front-end technology. Google Analytics and Google reCAPTCHA v3 are integrated for analytics and bot mitigation. Hosting is managed by Claranet Benelux B.V., a reputable provider. The site is mobile responsive with good SEO meta tags and Open Graph data. However, the lack of HTTPS and modern TLS protocols is a critical technical deficiency. Performance data is unavailable, but the presence of multiple JavaScript libraries and external resources suggests moderate load times. Accessibility features are basic, and no CMS is detected. The site would benefit from modernization of its tech stack and improved security infrastructure to reduce technical debt and enhance user trust.
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 paranice.nl. 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 paranice.nl.

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.