Skip to main content

Security report for computecanada.ca

Compute Canada Corp. · Technology · Canada

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

Security score

61/100

Risk levelMedium

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

Compute Canada Corp. was a Canadian organization providing national advanced research computing services. The website indicates that as of April 1, 2022, these services are now coordinated by the Digital Research Alliance of Canada, signaling a transition in service management. The website content is minimal and primarily serves as a redirect notice to the new coordinating body. The target audience includes Canadian academic and research institutions requiring high-performance computing resources. The business model appears to be government or publicly funded research infrastructure provision, with a medium-sized organizational footprint founded in 2011. Technically, the website uses legacy technologies such as Bootstrap 3 and jQuery 1.11.1, with basic mobile responsiveness and accessibility. There is no evidence of modern CMS or advanced analytics tools. Security configurations are minimal, with no DNSSEC enabled, no security headers detected, and no privacy or cookie policies present. The domain is registered with Go Daddy Domains Canada, Inc, with consistent WHOIS data matching the business identity and Canadian location. The security posture is basic, lacking advanced protections and policies, but no critical vulnerabilities or malware indicators were found. The absence of privacy and cookie policies and contact information reduces compliance and trustworthiness. Overall, the website is safe, professional, but outdated and minimally maintained, reflecting its deprecated status. Strategic recommendations include updating security configurations, adding privacy and cookie policies, improving mobile and accessibility features, and clearly providing contact information to enhance trust and compliance.

Scanned

NIS2 and GDPR posture

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

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

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

Keep watching computecanada.ca

This scan found 25 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
52
Security headers
30
Email security
65
DNS health
85
Network security
100
GDPR outside view
35
Average
61

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention computecanada.ca, from OffSeq Breach.

Total records
443
Employees
0
Customers
442
Third parties
1
Weak passwords
7%

28 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for computecanada.ca.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Compute Canada held a significant position as a national provider of advanced research computing services in Canada, serving academic and research institutions. The transition to the Digital Research Alliance of Canada suggests a strategic consolidation or evolution of national HPC services. The business model is likely government-funded infrastructure provision, focusing on enabling research through computing resources. The company has a moderate size and a clear sector focus on technology and research computing. The partnership with the Digital Research Alliance of Canada is critical to its current operational context. The website's minimal content and lack of marketing or commercial features indicate a non-commercial, service-oriented approach. Growth indicators are limited due to the transition, but the legacy brand retains recognition in the Canadian research community.

Security posture

The website demonstrates a low to moderate security maturity level. Key gaps include the absence of DNSSEC, lack of security headers, no visible incident response or vulnerability disclosure policies, and missing privacy and cookie policies. No forms or data collection mechanisms reduce attack surface but also limit user engagement. The WHOIS data is transparent and consistent, supporting legitimacy. There is no evidence of exposed sensitive data or vulnerable libraries, but the use of outdated jQuery version could pose risks if exploited. Incident response readiness and security culture indicators are not visible. Compliance with GDPR or other privacy regulations is not demonstrated. Overall, the security posture is basic and would benefit from modernization and policy implementation.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to harden the website.
  3. Publish comprehensive privacy and cookie policies to improve compliance and user trust.
  4. Update legacy JavaScript libraries like jQuery to current secure versions to mitigate vulnerabilities.
  5. Add clear contact information and incident response contacts to enhance transparency and security readiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Compute Canada Corp.
Description
Compute Canada was a national advanced research computing service provider in Canada. As of April 1, 2022, the Digital Research Alliance of Canada coordinates these services.
Key services
Advanced research computing services, National HPC coordination
Content quality
basic
Branding
moderate

Technology

Stack
Bootstrap 3, jQuery 1.11.1
Frameworks
Bootstrap
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
40/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is no longer maintained and redirects users to the Digital Research Alliance of Canada for current services.
  2. Minimal content with a clear notice about service transition.
  3. No privacy, cookie, or terms of service policies found.
  4. No contact emails or phone numbers explicitly provided on the page.
  5. No forms or data collection mechanisms present.
  6. Basic technical implementation with legacy jQuery and Bootstrap 3.
  7. No security headers or advanced security configurations detected.
  8. No analytics or tracking scripts found.
  9. No advertising or marketing tools detected.
  10. Website is safe with no adult or questionable content.
Technical notes

Notes

The website is built using Bootstrap 3 and jQuery 1.11.1, indicating legacy front-end technology. The HTML is valid but minimal, with basic meta tags and no structured data or Open Graph tags. The site is mobile responsive at a basic level but lacks advanced accessibility features. Hosting and domain registration are handled by Go Daddy Domains Canada, Inc. Performance is moderate with external dependencies on Google CDN for jQuery. No CMS or modern frameworks detected. No analytics or tracking scripts are present, indicating minimal data collection. The site lacks modern SEO optimizations and security configurations, reflecting its deprecated status and minimal maintenance.
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 computecanada.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 computecanada.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.