deathdate.org

🤖 AI Summary

After conducting a thorough safety and legitimacy analysis, deathdate.org receives a trust score of 58/100, which places it in the "Caution Advised" 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. 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 deathdate.org 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.

🤖 AI Summary

Our technology detection engine scanned deathdate.org and identified 9 distinct technologies across 8 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 deathdate.org. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for deathdate.org. Advertising: Meta Pixel and Google AdSense — handles advertising pixel tracking and conversion measurement for deathdate.org. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for deathdate.org. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for deathdate.org. Fonts: Google Fonts — delivers web fonts for typography for deathdate.org. JavaScript Library: jQuery — provides utility functions and DOM manipulation for deathdate.org. Performance: WP Rocket — optimizes page loading speed and performance for deathdate.org. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-SRM5E57KQB. These IDs can be used to identify other websites operated by the same organization.

🤖 AI Summary

deathdate.org delivers its homepage in 5688ms (server response time), which is considered slow by industry standards. The total page weight is 107 KB, and we detected 87 resource requests loading assets from 10 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: 3 out of 6 CSS files and 8 out of 16 JavaScript files are minified. Minifying the remaining 11 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 deathdate.org 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 107 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for deathdate.org. 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.

🤖 AI Summary

deathdate.org resolves to the IPv4 address 104.21.80.17 and also supports IPv6 (2606:4700:3031::6815:5011), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: dora.ns.cloudflare.com and noah.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 deathdate.org is handled by deathdate.org with 1 MX records configured: mail.deathdate.org. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. SPF is not configured, meaning any server could potentially send emails pretending to be from this domain. This is a significant email security concern. DMARC is not configured, leaving the domain vulnerable to email spoofing and phishing attacks that impersonate this domain. 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 deathdate.org. 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. Our subdomain enumeration scan discovered 1 active subdomains for deathdate.org: www.deathdate.org. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

🤖 AI Summary

The homepage of deathdate.org contains 928 words of visible text content. This is a moderate amount of content. The page is structured with 6 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 2 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 39 internal links pointing to other pages on the same domain and 3 external links pointing to third-party websites. There are 16 external JavaScript files, 6 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: Schema.org structured data (BreadcrumbList, EntryPoint, ImageObject, ListItem, Organization, ReadAction, SearchAction, WebPage, and WebSite) and RSS feed for content syndication. Notable missing features: XML Sitemap and robots.txt. Adding these could improve search engine discoverability and rich result eligibility.

🤖 AI Summary

The title tag for deathdate.org is well-optimized at 53 characters: "Death Date Calculator - Dare to Find your Death Date?". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 140 characters (well-optimized): "Old or young it doesn’t really matter. The Death Clock is ticking for us all. If you dare use our Death Calculator and f...". 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.deathdate.org/, preventing duplicate content issues, the page language is declared as en-us, the meta robots directive is set to max-snippet:-1,max-image-preview:standard,max-video-preview:-1, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Death Date Calculator - Dare to Find your Death Date?..."), 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. A Twitter Card of type summary_large_image is configured, which controls how links appear when shared on Twitter/X. The "summary_large_image" type displays a large image preview, which typically generates higher engagement rates than the basic card type. The site implements Schema.org structured data with the following types: BreadcrumbList, EntryPoint, ImageObject, ListItem, Organization, ReadAction, SearchAction, WebPage, 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.

🤖 AI Summary

Related domain discovery works by finding other websites that share the same IP address, Google Tag Manager container ID, Google Analytics property, or advertising pixel IDs with deathdate.org. This data becomes available after batch-crawling the domain database — individual domain lookups cannot populate this section. We extracted the following tracking IDs that can be used for cross-referencing: ga4_id: G-SRM5E57KQB.