ehealthsask.ca

We performed a comprehensive analysis of ehealthsask.ca on 2026-07-01. The website returned an HTTP 200 status code with a server response time of 7321ms. The page is served over HTTP/1.1 protocol, however no compression (Gzip or Brotli) is enabled, which means the page is transferred at its full uncompressed size. The total page weight is 69 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by Entrust Limited (OV type). The connection is encrypted using TLS 1.2 with the ECDHE-RSA-AES128-GCM-SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 4 domain(s) (Subject Alternative Names) and expires on 2027-01-04, which is 187 days from now. The security headers analysis reveals a score of 50/100 (moderate). The following security headers are properly configured: Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options. However, the site is missing Strict-Transport-Security (HSTS), Referrer-Policy, and Permissions-Policy, which could expose the site and its users to cross-site scripting (XSS), clickjacking, and other web-based attacks. Our technology detection scan identified 7 technologies across 6 categories powering ehealthsask.ca. The detected stack includes Bootstrap 3.3.7, Matomo, Google Tag Manager, Cloudflare, StackPath, jQuery 2.2.1., and Font Awesome. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, ehealthsask.ca receives an overall trust score of 71/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, ehealthsask.ca receives a trust score of 71/100, which places it in the "Likely Safe" category. This score is calculated by evaluating multiple factors including SSL certificate validity, domain registration history, email authentication protocols, security header configuration, and blacklist status across major threat intelligence databases. The analysis identified several positive trust signals: a valid HTTPS connection protecting data in transit, a valid SSL certificate issued by Entrust Limited with 187 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a quarantine policy. Areas of concern include: missing Referrer-Policy, potentially leaking URL information to third parties, the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity, and DNSSEC is not enabled, leaving DNS queries vulnerable to spoofing attacks. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked ehealthsask.ca against 8 major blacklist databases including Google Safe Browsing, Phishtank, Urlhaus, Openphish, Dnsfilter, Spamhaus Dbl, Surbl, and Virustotal. The domain passed all 8 checks with a clean status, meaning it has not been flagged for phishing, malware distribution, spam, or other malicious activities by any of the tested threat intelligence providers.

Our technology detection engine scanned ehealthsask.ca and identified 7 distinct technologies across 6 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. CSS Framework: Bootstrap (version 3.3.7) — provides the styling and responsive layout system for ehealthsask.ca. Analytics: Matomo — tracks visitor behavior and provides traffic insights for ehealthsask.ca. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for ehealthsask.ca. CDN: Cloudflare and StackPath — accelerates content delivery by caching assets at edge locations worldwide for ehealthsask.ca. JavaScript Library: jQuery (version 2.2.1.) — provides utility functions and DOM manipulation for ehealthsask.ca. Icon Set: Font Awesome — provides additional functionality for ehealthsask.ca. We also extracted the following tracking identifiers: Google Tag Manager container GTM-MJZ7DQC. These IDs can be used to identify other websites operated by the same organization.

ehealthsask.ca delivers its homepage in 7321ms (server response time), which is considered slow by industry standards. The total page weight is 69 KB, and we detected 133 resource requests loading assets from 9 third-party domains. A high number of third-party domains can significantly impact page load time due to additional DNS lookups and TLS handshakes required for each domain. No compression is currently enabled on ehealthsask.ca. Enabling Brotli or Gzip compression could reduce page size by 60-80% for text-based assets (HTML, CSS, JavaScript), significantly improving load times and reducing bandwidth costs. This is one of the simplest and most impactful performance optimizations available. Asset minification status: 2 out of 5 CSS files and 3 out of 14 JavaScript files are minified. Minifying the remaining 14 unminified file(s) could further reduce page weight by 10-30% for those assets. Minification is a best practice that reduces download sizes without affecting functionality. From an environmental perspective, each page view of ehealthsask.ca produces approximately 0.03g of CO₂, earning a carbon rating of A. This places the website among the cleanest on the web, demonstrating efficient use of server resources and optimized content delivery. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 69 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for ehealthsask.ca. This typically means the site doesn't have enough real-world Chrome user traffic to generate statistically significant field data, or the domain is not included in the CrUX dataset. Core Web Vitals (LCP, INP, CLS) are important Google ranking factors that measure real user experience.

ehealthsask.ca resolves to the IPv4 address 198.169.56.65, but does not support IPv6. IPv6 adoption is increasingly important as IPv4 address space becomes exhausted, and some ISPs and regions are transitioning to IPv6-only connectivity. The domain has 1 A record(s) configured. The domain name system is managed by 2 name servers: ns1.ehealthsask.ca and ns2.ehealthsask.ca. Having 2 name servers provides good redundancy — if one fails, the others can continue serving DNS queries. The choice of name servers often indicates the DNS hosting provider or CDN service being used. Email for ehealthsask.ca is handled by Microsoft 365 with 3 MX records configured: ehealthsask-ca.mail.protection.outlook.com, mailgateway111.ehealthsask.ca, and mailgateway112.ehealthsask.ca. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. SPF (Sender Policy Framework) is configured, which specifies which mail servers are authorized to send email on behalf of this domain. This helps prevent email spoofing and improves email deliverability. DMARC (Domain-based Message Authentication, Reporting and Conformance) is configured with a quarantine policy — a moderate setting, directing unauthorized emails to spam/junk folders. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is not enabled for ehealthsask.ca. While not critical for most websites, DNSSEC adds an important security layer by ensuring DNS responses haven't been tampered with during transit. Enabling DNSSEC is recommended for domains handling sensitive data or financial transactions.

The homepage of ehealthsask.ca contains 317 words of visible text content. This is a moderate amount of content. The page is structured with 0 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 20 images. 18 images (90%) are missing alt text attributes, which is a significant concern for both accessibility and SEO. Screen readers rely on alt text to describe images to visually impaired users, and search engines use alt text to understand image content. Only 10% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 78 internal links pointing to other pages on the same domain and 4 external links pointing to third-party websites. There are 14 external JavaScript files, 5 CSS stylesheets, and 1 iframes on the page. Notable missing features: XML Sitemap, robots.txt, and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 3 platforms: Facebook (@EHealthSaskatchewan), Twitter (@ehealthsask), and Linkedin (@ehealth-saskatchewan). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for ehealthsask.ca is good at 20 characters: "eHealth Saskatchewan". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 153 characters (well-optimized): "Official website for eHealth Saskatchewan. Empowering patients, enabling care. Find information and online services for ...". Google typically displays up to 155-160 characters of the meta description in search results. A compelling meta description with a clear call-to-action can significantly improve click-through rates from search results. The canonical url is correctly set to https://www.ehealthsask.ca:443/, preventing duplicate content issues and the page language is declared as en. No Open Graph tags are configured. When someone shares a link to ehealthsask.ca on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing. The meta keywords tag contains 14 terms including Saskatchewan, health card, birth, death, and marriage. Note: Google has officially confirmed that it does not use the meta keywords tag as a ranking signal. However, some other search engines (Bing, Yandex) may still reference it.