castle64.com

HTTPS HTTP/1.1 Gzip Crawled in 29,841ms · June 27, 2026 16:22 UTC

castle64.com Website Overview & Technology Report

🤖 AI Summary
We performed a comprehensive analysis of castle64.com on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 1796ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 0.0% size reduction. The total page weight is 18 KB. 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 0/100 (poor). No security headers are configured, which is a significant security concern. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-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 1 technologies across 1 categories powering castle64.com. The detected stack includes Google Analytics 4. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, castle64.com receives an overall trust score of 61/100, classified as "Likely Safe".
61
/ 100
Trust Score
0
/ 100
Security Headers
HTTP Response
Status200 OK
Response Time1796ms
ProtocolHTTP/1.1
Page Size18 KB
CompressionGzip
Compression Savings~0.0%
CDNNo
ServerApache/2.4.66 (Ubuntu)
Total Requests3
3rd Party Domains0
RedirectNone
Detected Technologies (1)
📊 Google Analytics 4
Security Headers
Content-Security-Policy
Not set
Strict-Transport-Security (HSTS)
Not set
X-Frame-Options
Not set
X-Content-Type-Options
Not set
Referrer-Policy
Not set
Permissions-Policy
Not set
SSL Certificate
IssuerLet's Encrypt
Issuer FullcountryName=US, organizationName=Let's Encrypt, commonName=YR1
SubjectcommonName=castle64.com
Type
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm
Issued
Expires— (? days)
SANs

castle64.com Trust Score & Safety Analysis

🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, castle64.com receives a trust score of 61/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, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none 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 castle64.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.
61
/ 100
Likely Safe
Trust Signals
Valid HTTPS
SPF configured
DMARC configured (p=none)
DKIM configured
⚠️ DNSSEC not enabled
Sitemap.xml 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

castle64.com Technology Stack & Detected Technologies

🤖 AI Summary
Our technology detection engine scanned castle64.com and identified 1 distinct technologies across 1 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for castle64.com.
Analytics
📊 Google Analytics 4(95%)

castle64.com Performance, Speed & Core Web Vitals

🤖 AI Summary
castle64.com delivers its homepage in 1796ms (server response time), which is considered somewhat slow by industry standards. The total page weight is 18 KB, and we detected 3 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 0.0% reduction in transfer size. This reduces bandwidth usage and improves page load times, especially for visitors on slower connections. From an environmental perspective, each page view of castle64.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 18 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for castle64.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 Size18 KB
CompressionGzip
Compression Savings~0.0%
CDNNo
Total Requests3
3rd Party Domains0
CSS Minified0/0
JS Minified0/0

castle64.com DNS Records, Email Authentication & Domain Registration

🤖 AI Summary
castle64.com resolves to the IPv4 address 45.79.192.119 and also supports IPv6 (2600:3c02::f03c:91ff:fe61:a11b), demonstrating modern network infrastructure readiness. The domain has 1 A record(s) configured. The domain name system is managed by 5 name servers: ns1.linode.com, ns2.linode.com, ns3.linode.com, ns4.linode.com, and ns5.linode.com. Having 5 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 castle64.com is handled by castle64.com with 1 MX records configured: mail.castle64.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 none policy — a monitoring-only setting that doesn't enforce any action on unauthorized emails. 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 castle64.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 2 active subdomains for castle64.com: mail.castle64.com and www.castle64.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
45.79.192.119
AAAA
2600:3c02::f03c:91ff:fe61:a11b
NS
ns1.linode.com
ns2.linode.com
ns3.linode.com
ns4.linode.com
ns5.linode.com
MX
mail.castle64.com
Email & Authentication
SPF
DMARC p=none
DKIM
DNSSEC
MX Providercastle64.com
Registrar
Organisation
Country
Contact
Registered
Expires
Domain Age
IPv6 SupportYes ✓
Subdomains (2 found)
mail.castle64.com www.castle64.com

castle64.com Page Content, Images & Accessibility

🤖 AI Summary
The homepage of castle64.com contains 1,570 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 1 H2 headings, 0 H3 headings, 0 H4 headings. The link structure consists of 26 internal links pointing to other pages on the same domain and 8 external links pointing to third-party websites. There are 0 external JavaScript files, 0 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages). Notable missing features: robots.txt and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.
1,570
Words
0
Images
100%
Alt Text Score
18
Page Size (KB)
Content Structure
H1
H2 Tags1
H3 Tags0
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links26
External Links8
Assets & Features
JavaScript Files0
JS Minified0/0
CSS Files0
CSS Minified0/0
Iframes0
Images0
Missing Alt0
SitemapYes ✓
Robots.txtNo
PWANo
AMPNo
RSS FeedNo

castle64.com SEO Analysis, Meta Tags & Open Graph

🤖 AI Summary
The title tag for castle64.com is well-optimized at 53 characters: "Free Office Football Pools, NFL / College Pools Picks". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 175 characters (slightly long): "The Original football pool site since the 90�s, supported bonus points for picking the survivor pools, confidence pools,...". 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 page language is declared as en. No Open Graph tags are configured. When someone shares a link to castle64.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 13 terms including nfl pool, football pool, nfl football pool, survivor pools, and confidence. 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
Free Office Football Pools, NFL / College Pools Picks
https://castle64.com
The Original football pool site since the 90�s, supported bonus points for picking the survivor pools, confidence pools, office football pools, NFL and College Football Pools.
Meta Tags
TitleFree Office Football Pools, NFL / College Pools Picks...
Title Length53 chars
Meta Desc Length175 chars
H1
Languageen
Canonical
Meta Robotsnot set
Meta Keywordsnfl pool, football pool, nfl football pool, survivor pools, ...
Schema.org & Social
Schema Types
OG Type
OG ImageNot set
Twitter Card
FaviconNot set