ohtuleht.ee

We performed a comprehensive analysis of ohtuleht.ee on 2026-06-29. The website returned an HTTP 200 status code with a server response time of 19466ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 643 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 2 domain(s) (Subject Alternative Names) and expires on 2026-09-27, which is 90 days from now. The security headers analysis reveals a score of 80/100 (good). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy. However, the site is missing Content-Security-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 3 technologies across 3 categories powering ohtuleht.ee. The detected stack includes Next.js media, Vite, and Cloudflare. The site uses Next.js as its primary framework (version media). Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, ohtuleht.ee receives an overall trust score of 84/100, classified as "Very Likely Safe".

After conducting a thorough safety and legitimacy analysis, ohtuleht.ee receives a trust score of 84/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 Google Trust Services with 90 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, and DNSSEC providing authenticated DNS responses. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks 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 ohtuleht.ee 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 ohtuleht.ee and identified 3 distinct technologies across 3 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Framework: Next.js (version media) — provides the application framework and routing for ohtuleht.ee. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for ohtuleht.ee. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for ohtuleht.ee.

ohtuleht.ee delivers its homepage in 19466ms (server response time), which is considered slow by industry standards. The total page weight is 643 KB, and we detected 1050 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. 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: 0 out of 2 CSS files and 2 out of 25 JavaScript files are minified. Minifying the remaining 25 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 ohtuleht.ee produces approximately 0.31g of CO₂, earning a carbon rating of C. This is an average carbon footprint. Optimizing images and reducing unnecessary scripts could further improve this score. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 643 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for ohtuleht.ee. 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.

ohtuleht.ee resolves to the IPv4 address 104.20.31.219 and also supports IPv6 (2606:4700:10::6814:1fdb), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: olivia.ns.cloudflare.com and yichun.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. Email for ohtuleht.ee is handled by Microsoft 365 with 1 MX records configured: ohtuleht-ee.mail.protection.outlook.com. 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 reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is enabled for ohtuleht.ee, 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. Our subdomain enumeration scan discovered 5 active subdomains for ohtuleht.ee: app.ohtuleht.ee, cdn.ohtuleht.ee, m.ohtuleht.ee, mail.ohtuleht.ee, and www.ohtuleht.ee. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of ohtuleht.ee contains 3,436 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 21 H2 headings, 3 H3 headings, 0 H4 headings, 0 H5, and 121 H6 headings. The page includes 195 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 777 internal links pointing to other pages on the same domain and 11 external links pointing to third-party websites. The high number of internal links suggests a well-interconnected site structure, which helps search engines discover and crawl all pages efficiently. There are 25 external JavaScript files, 2 CSS stylesheets, and 14 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior) and Progressive Web App (PWA) manifest (enabling app-like installation). Notable missing features: XML Sitemap and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on ohtuleht.ee: Visa. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates. The website has social media presence across 3 platforms: Facebook (@Ohtuleht), Instagram (@ohtuleht), and Tiktok (@ohtuleht.ee). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for ohtuleht.ee is well-optimized at 30 characters: "Õhtuleht – meiega näed rohkem!". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 162 characters (slightly long): "Toome sinuni päevakajalised uudised, olulised mõtted ja seisukohad, spordimaailma võidud ja kaotused, värvikad persoonil...". 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.ohtuleht.ee/, preventing duplicate content issues, the page language is declared as et, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Õhtuleht – meiega näed rohkem!..."), OG description, OG image (social sharing thumbnail), OG type (website). These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol.