Skip to main content

Security report for rudraksha.ca

Technology · N/a

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

62/100

Risk levelMedium

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

The website at https://www.rudraksha.ca/login_up.php is a login portal for Plesk Obsidian 18.0.78, a widely used web hosting control panel software. It is designed for web hosting administrators and resellers to manage hosting services and server configurations. The site presents a professional but basic interface consistent with Plesk branding, focusing on functionality rather than marketing or public business presence. The lack of public business information, privacy policy, and terms of service suggests this is an internal or restricted access portal rather than a public-facing commercial website. Technically, the site uses standard Plesk UI libraries, JavaScript frameworks like RequireJS and Prototype.js, and includes a cookie consent mechanism compliant with GDPR principles. However, no explicit HTTPS enforcement or security headers were detected in the provided content, which could pose security risks if not properly configured at the server level. The site includes CSRF protection tokens and password input controls with show/hide functionality, indicating some security best practices. From a security perspective, the absence of WHOIS data for the domain www.rudraksha.ca raises concerns about domain legitimacy or registration status. This, combined with missing public contact information and privacy policies, reduces trustworthiness for external users. No WAF or blocking mechanisms were detected, and the content is fully accessible. The site does not contain any adult or questionable content and is safe for general audiences. Overall, the site appears to be a functional, internal web hosting control panel login page with limited public-facing business information and moderate technical implementation. Security posture could be improved by enforcing HTTPS, adding security headers, and publishing privacy and terms policies. The domain's WHOIS data absence warrants further investigation to confirm legitimacy and registration status.

Scanned

NIS2 and GDPR posture

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

7 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 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. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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 Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  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

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

Keep watching rudraksha.ca

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. 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
37
Security headers
55
Email security
70
DNS health
45
Network security
100
GDPR outside view
65
Average
62

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 website serves as a portal for Plesk Obsidian, a commercial web hosting control panel software used globally by hosting providers and resellers. The business model revolves around licensing Plesk software to hosting companies who then manage customer domains and subscriptions. The target customers are web hosting administrators and resellers rather than end consumers. The site does not provide direct sales or marketing content, indicating it is likely an administrative interface rather than a commercial storefront. No partnership or subsidiary domains were identified. The lack of public contact or company information limits insights into revenue streams or growth indicators. The presence of official Plesk branding and versioning suggests the site is part of a legitimate hosting infrastructure.

Security posture

The security maturity level is moderate with some best practices observed such as CSRF token usage and password input controls. However, critical security headers are missing from the provided data, and HTTPS enforcement is not visible, which are significant gaps. The absence of WHOIS data for the domain reduces trust and raises questions about domain registration legitimacy. No incident response or security policy information is publicly available. GDPR cookie consent is implemented, indicating some compliance awareness. No vulnerabilities or malware indicators were found in the content. Overall, the site would benefit from enhanced security configurations and transparency to improve its security posture and trustworthiness.

Recommendations

  1. Enforce HTTPS with HSTS to secure all communications and prevent interception.
  2. Implement and verify security headers such as Content-Security-Policy, X-Frame-Options, and X-XSS-Protection.
  3. Publish a clear privacy policy and terms of service to improve compliance and user trust.
  4. Obtain and maintain accurate WHOIS registration data for the domain to enhance legitimacy.
  5. Regularly update Plesk software and dependencies to mitigate vulnerabilities and improve security.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
This website is a login page for Plesk Obsidian web hosting control panel, version 18.0.78, web host edition. It provides access to server management and hosting services.
Key services
Web hosting control panel, Server management, Subscription and domain management
Content quality
basic
Branding
consistent

Technology

Stack
Plesk Obsidian 18.0.78, JavaScript (RequireJS, Prototype.js), CSS (Plesk UI Library), HTML5, Manifest for PWA, Sentry for error reporting
Frameworks
Plesk UI Library
Platforms
Web hosting control panel
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
45/100
Good practices seen
  • Use of CSRF token (forgery_protection_token meta tag)
  • Password input field with show/hide toggle

Analytics and tracking

Services
Sentry (error tracking)
Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
Sentry
Transparency
poor

Site quality

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

Key observations

  1. Website is a Plesk Obsidian web hosting control panel login page.
  2. No public business or contact information is provided on the page.
  3. No privacy policy or terms of service links detected.
  4. Cookie consent banner present with GDPR cookie categories.
  5. No WHOIS data available for domain www.rudraksha.ca, indicating possible unregistered domain or private/internal use.
  6. No external advertising or marketing detected.
  7. No social media or contact emails found.
  8. Site uses standard Plesk UI libraries and scripts.
  9. No security headers or HTTPS enforcement visible in provided data.
  10. No WAF or blocking mechanisms detected.
Technical notes

Notes

The website is built on Plesk Obsidian 18.0.78, utilizing JavaScript libraries including RequireJS and Prototype.js, and styled with Plesk UI Library CSS. It includes a manifest for progressive web app capabilities and integrates Sentry for error tracking. The site is moderately optimized for performance and mobile use but lacks advanced SEO and accessibility features. The HTML structure is valid but minimal, focusing on login functionality. No CMS or third-party hosting provider information is evident. The technical stack is typical for a web hosting control panel but could be modernized with improved security headers and HTTPS enforcement.
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 rudraksha.ca. 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 rudraksha.ca.

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.