Skip to main content

Security report for ccohs.ca

Canadian Centre for Occupational Health and Safety · Government · Canada

Medium risk. 6 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

71/100

Risk levelMedium

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

The Canadian Centre for Occupational Health and Safety (CCOHS) is a Canadian government agency dedicated to promoting safe and healthy working environments by providing comprehensive occupational health and safety information, training, and resources. The website serves as a national authoritative source for workers, employers, and health and safety professionals across Canada, offering a wide range of services including courses, databases, and business safety portals. The organization is well positioned in the government sector with consistent branding and a clear mission. Technically, the website employs modern web technologies including jQuery and the WET-BOEW framework, ensuring good accessibility, mobile optimization, and SEO practices. It integrates Google Analytics and Dynatrace for performance and usage monitoring. The site is well structured with clear navigation and professional design, reflecting a mature digital infrastructure. From a security perspective, the site uses HTTPS and secure form handling, with no visible vulnerabilities or exposed sensitive data. However, the absence of explicit security headers and a cookie consent mechanism indicates areas for improvement in compliance and security hardening. The WHOIS data is unavailable, which is unusual but likely due to registry policies; this does not detract from the site's legitimacy given its government affiliation. Overall, the website presents a low risk profile with strong business credibility and technical maturity. Strategic recommendations include implementing cookie consent for privacy compliance, adding security headers, publishing incident response and security policies, and providing a vulnerability disclosure channel to enhance trust and security posture.

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

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

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics, Facebook, Twitter, LinkedIn

      What to do: Document all third-party data sharing in your privacy policy

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

Keep watching ccohs.ca

This scan found 20 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
67
Security headers
65
Email security
75
DNS health
85
Network security
100
GDPR outside view
35
Average
71

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

CCOHS operates as a government entity providing occupational health and safety information and services primarily to Canadian workers and employers. Its market positioning is strong as the official national resource, supported by the Government of Canada. The business model is service-oriented, focusing on education, information dissemination, and compliance support. Revenue streams likely include government funding and paid services such as training and database subscriptions. The target customer segments include small to medium businesses, health and safety professionals, and workers. The partnership ecosystem includes other government departments and health organizations. The website's comprehensive content and service offerings indicate a mature operation with a focus on public service and compliance support.

Security posture

The website demonstrates a good security maturity level with HTTPS enforced and secure form handling. No critical vulnerabilities or exposed sensitive data were detected. However, the lack of security headers such as Content Security Policy (CSP), X-Frame-Options, and HSTS reduces the overall security posture. There is no visible incident response or security policy page, nor a vulnerability disclosure program, which are important for transparency and readiness. Privacy compliance is partial, with a privacy policy present but no cookie consent mechanism. Overall, the security culture appears cautious but could benefit from formalizing policies and improving technical controls.

Recommendations

  1. Implement comprehensive security headers including CSP, HSTS, and X-Frame-Options to enhance protection against common web attacks.
  2. Add a cookie consent banner to comply with privacy regulations and improve user transparency.
  3. Publish an incident response policy and contact information for security incidents to improve readiness and trust.
  4. Establish a vulnerability disclosure program or security.txt file to encourage responsible reporting of security issues.
  5. Regularly review and update privacy and security policies to maintain compliance with evolving regulations such as GDPR and NIS2.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Canadian Centre for Occupational Health and Safety
Description
The Canadian Centre for Occupational Health and Safety (CCOHS) promotes a safe and healthy working environment by providing occupational health and safety information and advice.
Key services
Health and safety information, Training courses, Databases, Business Safety Portal, Consultation and support services
Content quality
excellent
Branding
consistent

Technology

Stack
jQuery 3.5.1, WET-BOEW 4.0.65, Google Analytics (UA and GA4), Ruxit (Dynatrace) monitoring
Frameworks
WET-BOEW (Web Experience Toolkit)
Performance
moderate
Mobile
good
Accessibility
excellent
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Secure forms with validation
  • No vulnerable libraries detected

Analytics and tracking

Services
Google Analytics UA, Google Analytics GA4, Dynatrace Ruxit
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Dynatrace Ruxit
Transparency
excellent

Site quality

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

Key observations

  1. Website is fully accessible with rich content and navigation.
  2. Strong government branding and authoritative occupational health and safety information.
  3. No signs of phishing, malware, or suspicious content.
  4. No explicit privacy cookie banner found, which could be improved.
  5. WHOIS data missing, but no negative impact on trust due to official nature.
Technical notes

Notes

The website uses a modern and government-standard technology stack including jQuery 3.5.1 and the WET-BOEW framework, which supports accessibility and responsive design. Google Analytics (both UA and GA4) and Dynatrace Ruxit are used for analytics and performance monitoring. The site is well structured with semantic HTML and ARIA roles, supporting accessibility. Performance is moderate with room for optimization. No CMS is explicitly detected, suggesting a custom or government-managed platform. The absence of security headers and cookie consent mechanisms indicates technical debt in security and privacy compliance areas. Hosting provider details are not evident from the data.
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 ccohs.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 ccohs.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.