calendardate.com

HTTPS HTTP/2 HSTS Gzip Cloudflare Crawled in 37,500ms · June 27, 2026 16:13 UTC

calendardate.com Website Overview & Technology Report

🤖 AI Summary
We performed a comprehensive analysis of calendardate.com on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 33592ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 14 KB, and the site is served behind a CDN (Content Delivery Network). Warning: The website does not have a valid SSL certificate. Visitors may see security warnings in their browser, and data transmitted to and from this website is not encrypted. The security headers analysis reveals a score of 35/100 (below average). The following security headers are properly configured: Strict-Transport-Security (HSTS) and X-Content-Type-Options. However, the site is missing Content-Security-Policy, X-Frame-Options, 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 3 technologies across 3 categories powering calendardate.com. The detected stack includes Google AdSense, Cloudflare, and WP Rocket. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, calendardate.com receives an overall trust score of 70/100, classified as "Likely Safe".
70
/ 100
Trust Score
35
/ 100
Security Headers
HTTP Response
Status200 OK
Response Time33592ms
ProtocolHTTP/2
Page Size14 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Servercloudflare
Total Requests59
3rd Party Domains1
Redirect1 hop(s)
Detected Technologies (3)
📢 Google AdSense ☁️ Cloudflare ⚡ WP Rocket
Security Headers
Content-Security-Policy
Not set
Strict-Transport-Security (HSTS)
Set ✓
X-Frame-Options
Not set
X-Content-Type-Options
Set ✓
Referrer-Policy
Not set
Permissions-Policy
Not set
SSL Certificate
IssuerGoogle Trust Services
Issuer FullcountryName=US, organizationName=Google Trust Services, commonName=WE1
SubjectcommonName=calendardate.com
Type
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm
Issued
Expires— (? days)
SANs

calendardate.com Trust Score & Safety Analysis

🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, calendardate.com receives a trust score of 70/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, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a quarantine policy, and DKIM (DomainKeys Identified Mail) providing cryptographic email verification. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking), 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 calendardate.com 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.
70
/ 100
Likely Safe
Trust Signals
Valid HTTPS
HSTS enabled
SPF configured
DMARC configured (p=quarantine)
DKIM configured
⚠️ DNSSEC not enabled
Robots.txt found
⚠️ Missing Content-Security-Policy
⚠️ Missing X-Frame-Options
⚠️ Missing Referrer-Policy
Blacklist Checks (8/8 clean)
Google Safe Browsing clean
Phishtank clean
Urlhaus clean
Openphish clean
Dnsfilter clean
Spamhaus Dbl clean
Surbl clean
Virustotal clean

calendardate.com Technology Stack & Detected Technologies

🤖 AI Summary
Our technology detection engine scanned calendardate.com 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. Advertising: Google AdSense — handles advertising pixel tracking and conversion measurement for calendardate.com. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for calendardate.com. Performance: WP Rocket — optimizes page loading speed and performance for calendardate.com.
Advertising
📢 Google AdSense(95%)
CDN
☁️ Cloudflare(100%)
Performance
⚡ WP Rocket(95%)

calendardate.com Performance, Speed & Core Web Vitals

🤖 AI Summary
calendardate.com delivers its homepage in 33592ms (server response time), which is considered slow by industry standards. The total page weight is 14 KB, and we detected 59 resource requests loading assets from 1 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 1 CSS files and 1 out of 2 JavaScript files are minified. Minifying the remaining 2 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 calendardate.com produces approximately 0.01g 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 14 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for calendardate.com. 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.
Core Web Vitals data not available
Requires CrUX API key configuration
Carbon Footprint
CO₂ per page view0.01g
RatingA
Page Weight & Optimization
HTML Size14 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Total Requests59
3rd Party Domains1
CSS Minified0/1
JS Minified1/2

calendardate.com DNS Records, Email Authentication & Domain Registration

🤖 AI Summary
calendardate.com resolves to the IPv4 address 172.67.72.210 and also supports IPv6 (2606:4700:20::ac43:48d2), demonstrating modern network infrastructure readiness. The domain has 3 A record(s) configured. The domain name system is managed by 2 name servers: gracie.ns.cloudflare.com and tadeo.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 calendardate.com is handled by calendardate.com with 1 MX records configured: _dc-mx.98662c650f12.calendardate.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 quarantine policy — a moderate setting, directing unauthorized emails to spam/junk folders. DKIM (DomainKeys Identified Mail) is configured, adding a cryptographic signature to outgoing emails that receiving servers can verify to confirm the email hasn't been tampered with in transit. DNSSEC is not enabled for calendardate.com. 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 3 active subdomains for calendardate.com: ftp.calendardate.com, mail.calendardate.com, and www.calendardate.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
172.67.72.210
104.26.12.212
104.26.13.212
AAAA
2606:4700:20::ac43:48d2
NS
gracie.ns.cloudflare.com
tadeo.ns.cloudflare.com
MX
_dc-mx.98662c650f12.calendardate.com
Email & Authentication
SPF
DMARC p=quarantine
DKIM
DNSSEC
MX Providercalendardate.com
Registrar
Organisation
Country
Contact
Registered
Expires
Domain Age
IPv6 SupportYes ✓
Subdomains (3 found)
ftp.calendardate.com mail.calendardate.com www.calendardate.com

calendardate.com Page Content, Images & Accessibility

🤖 AI Summary
The homepage of calendardate.com contains 236 words of visible text content. This is a relatively short page — adding more descriptive content could improve search engine visibility. The page is structured with 0 H2 headings, 4 H3 headings, 0 H4 headings. The page includes 4 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 47 internal links pointing to other pages on the same domain and 0 external links pointing to third-party websites. There are 2 external JavaScript files, 1 CSS stylesheets, and 0 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.
236
Words
4
Images
100%
Alt Text Score
14
Page Size (KB)
Content Structure
H1
H2 Tags0
H3 Tags4
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links47
External Links0
Assets & Features
JavaScript Files2
JS Minified1/2
CSS Files1
CSS Minified0/1
Iframes0
Images4
Missing Alt0
SitemapNo
Robots.txtYes ✓
PWAYes ✓
AMPNo
RSS FeedNo

calendardate.com SEO Analysis, Meta Tags & Open Graph

🤖 AI Summary
The title tag for calendardate.com is good at 16 characters: "CalendarDate.com". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 45 characters (acceptable): "Calendars and holidays from around the world.". 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. A favicon is configured. No Open Graph tags are configured. When someone shares a link to calendardate.com 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 40 terms including 2026 calendar, 2027 calendar, calendars, printable calendars, and today's. 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.
Google SERP Preview
CalendarDate.com
https://calendardate.com
Calendars and holidays from around the world.
Meta Tags
TitleCalendarDate.com...
Title Length16 chars
Meta Desc Length45 chars
H1
Language
Canonical
Meta Robotsnot set
Meta Keywords2026 calendar, 2027 calendar, calendars, printable calendars...
Schema.org & Social
Schema Types
OG Type
OG ImageNot set
Twitter Card
FaviconSet ✓