Skip to main content

Security report for centralhealthline.ca

thehealthline.ca · Healthcare · Canada

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

Security score

65/100

Risk levelMedium

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

The website centralhealthline.ca serves as a regional health information portal focused on Central Ontario, providing residents and healthcare professionals with access to health services directories, news, careers, events, and resources. The platform is positioned as a trusted community health resource with strong ties to Ontario government health initiatives and local health units. The business model centers on information dissemination and referral services rather than direct healthcare provision. Technically, the site is built on ASP.NET Web Forms with supporting JavaScript libraries such as jQuery and Modernizr. It employs Google Analytics and Google Tag Manager for user tracking and analytics. Hosting infrastructure leverages Google Cloud DNS services, indicating a reliable hosting environment. The site demonstrates moderate performance and basic mobile optimization, with room for improvement in accessibility and SEO. From a security perspective, the site uses HTTPS and domain transfer protections but lacks DNSSEC and important security headers, which could be improved to enhance security posture. Privacy compliance is partial, with a privacy policy present but no cookie consent mechanism or GDPR compliance indicators. No incident response or security policy information is published, which is a gap in transparency. Overall, the website is a credible and professional health information resource with good content quality and business credibility. Security and privacy practices require enhancement to meet modern standards and regulatory requirements. Strategic improvements in security headers, DNSSEC, cookie consent, and incident response transparency would strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

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

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

  2. GDPR outside view

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

    • 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

  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

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

Keep watching centralhealthline.ca

This scan found 26 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
62
Security headers
50
Email security
70
DNS health
55
Network security
100
GDPR outside view
53
Average
65

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

Centralhealthline.ca operates as a regional health information and referral service targeting residents and healthcare professionals in Central Ontario. Its competitive advantage lies in its comprehensive local health service listings, government affiliation, and trusted branding with Ontario Health atHome. The business model is informational and community service-oriented, likely funded or supported by public health entities. The site’s partnership ecosystem includes Ontario government health sites and local health units, enhancing its authority and reach. Growth indicators include regular news updates and event listings, although career listings are currently inactive. The platform’s operations focus on accessibility of health information rather than commercial transactions.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and domain transfer protections in place. However, the absence of DNSSEC and security headers such as Content-Security-Policy and X-Frame-Options reduces its defense-in-depth. No exposed sensitive data or vulnerable libraries were detected in the provided content. The lack of published security policies and incident response contacts indicates limited transparency and preparedness. Privacy compliance gaps exist due to missing cookie consent mechanisms and GDPR indicators. Overall, the security posture is adequate for an informational site but should be enhanced to protect user data and comply with evolving regulations.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement standard security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Add a cookie consent banner/mechanism to comply with privacy regulations such as GDPR.
  4. Publish a clear security policy and incident response contact information on the website.
  5. Conduct a privacy compliance audit and update policies to reflect GDPR and other relevant regulations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
thehealthline.ca
Description
Local health services, news, careers and events for Central, Ontario including Central, North York, Etobicoke, York Toronto, York Region and South Simcoe.
Key services
Health services directory, Health news, Health careers listings, Health events, Health resources and library
Content quality
good
Branding
consistent

Technology

Stack
ASP.NET Web Forms, jQuery, Google Analytics, Google Tag Manager, Modernizr
Frameworks
ASP.NET
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
65/100
Good practices seen
  • HTTPS enabled
  • Use of clientTransferProhibited and clientUpdateProhibited domain status

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is a regional health information portal for Central Ontario.
  2. Content is well structured with clear categories for health services and topics.
  3. No privacy or cookie consent banners detected, indicating partial privacy compliance.
  4. No visible security policy or incident response information published.
  5. Use of Google Analytics and Tag Manager indicates moderate user tracking.
  6. No suspicious or malicious content detected.
  7. WHOIS data is privacy protected but domain age and status indicate legitimacy.
  8. Website uses ASP.NET Web Forms technology with some legacy elements.
  9. Mobile optimization is basic but functional.
  10. No social media links detected in the provided content.
Technical notes

Notes

The website is built on a legacy ASP.NET Web Forms platform with modern JavaScript libraries like jQuery and Modernizr. It uses Google Analytics and Tag Manager for analytics and tracking. Hosting is supported by Google Cloud DNS services, ensuring reliable DNS resolution. The site’s performance is moderate with basic mobile optimization and accessibility features. SEO is basic with meta tags present but could be improved with structured data and enhanced semantic markup. The technical stack is stable but shows signs of aging technology that could benefit from modernization to improve maintainability, performance, and security.
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 centralhealthline.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 centralhealthline.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.