enterprise.health

We performed a comprehensive analysis of enterprise.health on 2026-07-06. The website returned an HTTP 200 status code with a server response time of 23475ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 234 KB, and the site is served behind a CDN (Content Delivery Network). The website uses a secure HTTPS connection with a valid SSL certificate issued by Google Trust Services (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and ECDSA-SHA256 signature algorithm. The certificate covers 3 domain(s) (Subject Alternative Names) and expires on 2026-09-20, which is 76 days from now. The security headers analysis reveals a score of 55/100 (moderate). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), and Referrer-Policy. However, the site is missing X-Frame-Options, X-Content-Type-Options, 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 6 technologies across 5 categories powering enterprise.health. The detected stack includes React, Google Analytics 4, Microsoft Clarity, Google Tag Manager, HubSpot, and Amazon CloudFront. The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, enterprise.health receives an overall trust score of 77/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, enterprise.health receives a trust score of 77/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, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, a valid SSL certificate issued by Google Trust Services with 76 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none policy, and DNSSEC providing authenticated DNS responses. Areas of concern include: no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking) and the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked enterprise.health 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 enterprise.health and identified 6 distinct technologies across 5 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. UI Library: React — handles the user interface rendering and component management for enterprise.health. Analytics: Google Analytics 4 and Microsoft Clarity — tracks visitor behavior and provides traffic insights for enterprise.health. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for enterprise.health. Marketing: HubSpot — provides marketing automation capabilities for enterprise.health. CDN: Amazon CloudFront — accelerates content delivery by caching assets at edge locations worldwide for enterprise.health. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-9L6D5P1TXJ and Google Tag Manager container GTM-T2FW2SH. These IDs can be used to identify other websites operated by the same organization.

enterprise.health delivers its homepage in 23475ms (server response time), which is considered slow by industry standards. The total page weight is 234 KB, and we detected 147 resource requests loading assets from 11 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. The website uses Gzip compression for text-based assets, achieving an estimated 60.0% reduction in transfer size. This reduces bandwidth usage and improves page load times, especially for visitors on slower connections. Asset minification status: 19 out of 19 CSS files and 10 out of 17 JavaScript files are minified. Minifying the remaining 7 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. The site is served through a Content Delivery Network (CDN), which caches static assets at edge servers around the world. This means visitors from different geographic regions receive content from the nearest edge server, significantly reducing latency. CDN usage is particularly important for websites with a global audience, as it can reduce page load times by 40-60% for distant visitors. From an environmental perspective, each page view of enterprise.health produces approximately 0.11g 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 234 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for enterprise.health. 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.

enterprise.health resolves to the IPv4 address 104.18.6.121 and also supports IPv6 (2606:4700::6812:779), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: jill.ns.cloudflare.com and ken.ns.cloudflare.com. 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. 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 none policy — a monitoring-only setting that doesn't enforce any action on unauthorized emails. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is enabled for enterprise.health, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites.

The homepage of enterprise.health contains 1,168 words of visible text content. This is a substantial amount of content that provides good opportunities for search engine indexing. The page is structured with 0 H2 headings, 5 H3 headings, 23 H4 headings, 4 H5, and 6 H6 headings. The page includes 26 images. 1 images (4%) 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 96% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 43 internal links pointing to other pages on the same domain and 36 external links pointing to third-party websites. There are 17 external JavaScript files, 19 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 4 platforms: Facebook (@EnterpriseHealth), Twitter (@ehocchealth), Linkedin (@enterprisehealth), and Youtube (@UCzPsN8wBDnHg0mgWPyejA6Q). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for enterprise.health is too long at 97 characters: "Transform Workforce Health | Enterprise System for Compliance and Performance | ...". At 97 characters, the title will likely be truncated in Google search results (recommended: 50-60 characters). Consider shortening it while keeping the most important keywords at the beginning. The meta description is 192 characters (slightly long): "Streamline workforce health management with Enterprise Health, enhancing compliance, visibility, and operational efficie...". 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.enterprisehealth.com, preventing duplicate content issues, the page language is declared as en, and a favicon is configured. Open Graph meta tags are configured with 2/4 recommended fields: OG title ("Transform Workforce Health | Enterprise System for Complianc..."), OG description, These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol. A Twitter Card of type summary is configured, which controls how links appear when shared on Twitter/X. The "summary" type displays a large image preview, which typically generates higher engagement rates than the basic card type.