heag.de

We performed a comprehensive analysis of heag.de on 2026-07-03. The website returned an HTTP 200 status code with a server response time of 7087ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 95 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by DigiCert Inc (OV type). The connection is encrypted using TLS 1.2 with the ECDHE-RSA-AES256-GCM-SHA384 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2027-01-29, which is 210 days from now. The security headers analysis reveals a score of 65/100 (moderate). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, and Referrer-Policy. However, the site is missing Content-Security-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 5 technologies across 4 categories powering heag.de. The detected stack includes WordPress, Matomo, Cloudflare, StackPath, and jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, heag.de receives an overall trust score of 80/100, classified as "Very Likely Safe".

After conducting a thorough safety and legitimacy analysis, heag.de receives a trust score of 80/100, which places it in the "Very 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 DigiCert Inc with 210 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a none policy. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, 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 heag.de 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 heag.de and identified 5 distinct technologies across 4 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. CMS: WordPress — manages the content and page structure for heag.de. Analytics: Matomo — tracks visitor behavior and provides traffic insights for heag.de. CDN: Cloudflare and StackPath — accelerates content delivery by caching assets at edge locations worldwide for heag.de. JavaScript Library: jQuery — provides utility functions and DOM manipulation for heag.de.

heag.de delivers its homepage in 7087ms (server response time), which is considered slow by industry standards. The total page weight is 95 KB, and we detected 14 resource requests loading assets from 0 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: 1 out of 3 CSS files and 4 out of 16 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 heag.de produces approximately 0.05g 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 95 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for heag.de. 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.

heag.de resolves to the IPv4 address 193.25.234.241, 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 6 name servers: a.ns.ecotel.net, b.ns.ecotel.net, c.ns.ecotel.net, dns.heag.de, dns2.heag.de, and dns3.heag.de. Having 6 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 heag.de is handled by itrm.de with 2 MX records configured: mail21.itrm.de and mail23.itrm.de. 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 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 not enabled for heag.de. 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 heag.de contains 309 words of visible text content. This is a moderate amount of content. The page is structured with 4 H2 headings, 5 H3 headings, 0 H4 headings. The page includes 11 images. All images have proper alt text attributes ✓, which is excellent for both accessibility (screen readers) and SEO (search engines can understand image content). The link structure consists of 37 internal links pointing to other pages on the same domain and 11 external links pointing to third-party websites. There are 16 external JavaScript files, 3 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: Schema.org structured data (BreadcrumbList, CollectionPage, EntryPoint, ListItem, PropertyValueSpecification, SearchAction, and WebSite). Notable missing features: XML Sitemap and robots.txt. Adding these could improve search engine discoverability and rich result eligibility.

The title tag for heag.de is too long at 73 characters: "HEAG Holding AG - Beteiligungsmanagement der Wissenschaftsstadt Darmstadt". At 73 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 134 characters (well-optimized): "Die HEAG steht für das Beteiligungsmanagement der Wissenschaftsstadt Darmstadt sowie für Energie, Verkehr und Immobilien...". 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.heag.de/, preventing duplicate content issues, the page language is declared as de, the meta robots directive is set to index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to heag.de 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 site implements Schema.org structured data with the following types: BreadcrumbList, CollectionPage, EntryPoint, ListItem, PropertyValueSpecification, SearchAction, and WebSite. Structured data helps search engines understand the page content and can enable rich results (featured snippets, knowledge panels, star ratings) in Google search results, which can significantly increase click-through rates.