HomeDirectory 221.com

21.com

HTTPS HTTP/2 HSTS Gzip Amazon CloudFront Next.js Crawled in 25,885ms · June 27, 2026 14:37 UTC

21.com Website Overview & Technology Report

🤖 AI Summary
We performed a comprehensive analysis of 21.com on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 9218ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 2717 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 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 9 technologies across 9 categories powering 21.com. The detected stack includes Next.js chunks, React, Vite, Google Analytics 4, Google Tag Manager, Sentry, reCAPTCHA v3, Amazon CloudFront, and NitroPack. The site uses Next.js as its primary framework (version chunks). The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, 21.com receives an overall trust score of 75/100, classified as "Likely Safe".
75
/ 100
Trust Score
65
/ 100
Security Headers
HTTP Response
Status200 OK
Response Time9218ms
ProtocolHTTP/2
Page Size2717 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Servercloudflare
Total Requests799
3rd Party Domains10
RedirectNone
Detected Technologies (9)
🔧 Next.js ⚛️ React 🔨 Vite 📊 Google Analytics 4 🏷️ Google Tag Manager 📡 Sentry 🔒 reCAPTCHA v3 ☁️ Amazon CloudFront ⚡ NitroPack
Security Headers
Content-Security-Policy
Not set
Strict-Transport-Security (HSTS)
Set ✓
X-Frame-Options
Set ✓
X-Content-Type-Options
Set ✓
Referrer-Policy
Set ✓
Permissions-Policy
Not set
SSL Certificate
IssuerGoogle Trust Services
Issuer FullcountryName=US, organizationName=Google Trust Services, commonName=WE1
SubjectcommonName=21.com
Type
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm
Issued
Expires— (? days)
SANs

21.com Trust Score & Safety Analysis

🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, 21.com receives a trust score of 75/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, 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 21.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.
75
/ 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
Blacklist Checks (8/8 clean)
Google Safe Browsing clean
Phishtank clean
Urlhaus clean
Openphish clean
Dnsfilter clean
Spamhaus Dbl clean
Surbl clean
Virustotal clean

21.com Technology Stack & Detected Technologies

🤖 AI Summary
Our technology detection engine scanned 21.com and identified 9 distinct technologies across 9 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 chunks) — provides the application framework and routing for 21.com. UI Library: React — handles the user interface rendering and component management for 21.com. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for 21.com. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for 21.com. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for 21.com. Monitoring: Sentry — monitors application performance and errors for 21.com. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for 21.com. CDN: Amazon CloudFront — accelerates content delivery by caching assets at edge locations worldwide for 21.com. Performance: NitroPack — optimizes page loading speed and performance for 21.com. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-6PBSYREQ9J and Google Tag Manager container GTM-PF8WCWLB. These IDs can be used to identify other websites operated by the same organization.
Framework
🔧 Next.js chunks(100%)
UI Library
⚛️ React(95%)
Build Tool
🔨 Vite(95%)
Analytics
📊 Google Analytics 4(95%)
Tag Manager
🏷️ Google Tag Manager(95%)
Monitoring
📡 Sentry(95%)
Security
🔒 reCAPTCHA v3(95%)
CDN
☁️ Amazon CloudFront(95%)
Performance
⚡ NitroPack(95%)
Tracking IDs
ga4_idG-6PBSYREQ9J
gtm_idGTM-PF8WCWLB

21.com Performance, Speed & Core Web Vitals

🤖 AI Summary
21.com delivers its homepage in 9218ms (server response time), which is considered slow by industry standards. The total page weight is 2717 KB, and we detected 799 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: 0 out of 4 CSS files and 0 out of 50 JavaScript files are minified. Minifying the remaining 54 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 21.com produces approximately 1.33g of CO₂, earning a carbon rating of F. The website's carbon footprint could be reduced by optimizing images, enabling compression, reducing third-party scripts, and leveraging caching. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 2717 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for 21.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 view1.33g
RatingF
Page Weight & Optimization
HTML Size2717 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Total Requests799
3rd Party Domains10
CSS Minified0/4
JS Minified0/50

21.com DNS Records, Email Authentication & Domain Registration

🤖 AI Summary
21.com resolves to the IPv4 address 104.18.20.225 and also supports IPv6 (2606:4700::6812:15e1), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: clint.ns.cloudflare.com and serenity.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 21.com is handled by Google Workspace with 1 MX records configured: smtp.google.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 21.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 21.com: cdn.21.com and www.21.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
104.18.20.225
104.18.21.225
AAAA
2606:4700::6812:15e1
NS
clint.ns.cloudflare.com
serenity.ns.cloudflare.com
MX
smtp.google.com
Email & Authentication
SPF
DMARC p=quarantine
DKIM
DNSSEC
MX ProviderGoogle Workspace
Registrar
Organisation
Country
Contact
Registered
Expires
Domain Age
IPv6 SupportYes ✓
Subdomains (2 found)
cdn.21.com www.21.com

21.com Page Content, Images & Accessibility

🤖 AI Summary
The homepage of 21.com contains 1,418 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 4 H2 headings, 0 H3 headings, 6 H4 headings. The page includes 514 images. 224 images (44%) are missing alt text attributes, which is a significant concern for both accessibility and SEO. Screen readers rely on alt text to describe images to visually impaired users, and search engines use alt text to understand image content. Only 56% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 150 internal links pointing to other pages on the same domain and 5 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 50 external JavaScript files, 4 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. We detected the following payment methods accepted on 21.com: Visa, Mastercard, Discover, Apple Pay, and Google Pay. 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 4 platforms: Facebook (@people), Twitter (@21com_official), Instagram (@21com_official), and Tiktok (@21com_official). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
1,418
Words
514
Images
56%
Alt Text Score
2717
Page Size (KB)
Content Structure
H121.com Online Casino and Sportsbook
H2 Tags4
H3 Tags0
H4 Tags6
H5 Tags0
H6 Tags0
Internal Links150
External Links5
Assets & Features
JavaScript Files50
JS Minified0/50
CSS Files4
CSS Minified0/4
Iframes0
Images514
Missing Alt224
SitemapNo
Robots.txtYes ✓
PWAYes ✓
AMPNo
RSS FeedNo
Payment Methods Detected
💳 Visa💳 Mastercard💳 Discover💳 Apple Pay💳 Google Pay
Social Media Presence
Facebook: @peopleTwitter: @21com_officialInstagram: @21com_officialTiktok: @21com_official

21.com SEO Analysis, Meta Tags & Open Graph

🤖 AI Summary
The title tag for 21.com is well-optimized at 39 characters: "21.com - Crypto Casino & Sports Betting". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 111 characters (well-optimized): "Enjoy Slots, Live Casino games & Shows, Sportsbetting and instant Fiat & crypto payments at 21.com. Play Great!". 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, the meta robots directive is set to index, follow, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("21.com - Crypto Casino & Sports Betting..."), 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.
Google SERP Preview
21.com - Crypto Casino & Sports Betting
https://21.com
Enjoy Slots, Live Casino games & Shows, Sportsbetting and instant Fiat & crypto payments at 21.com. Play Great!
Meta Tags
Title21.com - Crypto Casino & Sports Betting...
Title Length39 chars
Meta Desc Length111 chars
H121.com Online Casino and Sportsbook
Languageen
Canonical
Meta Robotsindex, follow
Meta Keywordsnot set
Schema.org & Social
Schema Types
OG Typewebsite
OG ImageSet ✓
Twitter Cardsummary_large_image
FaviconSet ✓
Open Graph Preview
21.com
21.com - Crypto Casino & Sports Betting
Enjoy Slots, Live Casino games & Shows, Sportsbetting and instant Fiat & crypto payments at 21.com. Play Great!