rajabandotdamai32.com

We performed a comprehensive analysis of rajabandotdamai32.com on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 3422ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 264 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-17, which is 79 days from now. 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 6 technologies across 6 categories powering rajabandotdamai32.com. The detected stack includes React, Vite, Google Analytics 4, Cloudflare, Netlify, and Google Fonts. The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, rajabandotdamai32.com receives an overall trust score of 63/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, rajabandotdamai32.com receives a trust score of 63/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, a valid SSL certificate issued by Google Trust Services with 79 days until expiration, and SPF (Sender Policy Framework) email authentication preventing email spoofing. 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, DNSSEC is not enabled, leaving DNS queries vulnerable to spoofing attacks, and the domain is relatively new (72 days old), which is sometimes associated with fraudulent websites. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked rajabandotdamai32.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. The domain is registered through NameCheap, Inc. based in CA, with a registration date of 2026-04-24 and expiration date of 2027-04-24.

Our technology detection engine scanned rajabandotdamai32.com and identified 6 distinct technologies across 6 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. UI Library: React — handles the user interface rendering and component management for rajabandotdamai32.com. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for rajabandotdamai32.com. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for rajabandotdamai32.com. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for rajabandotdamai32.com. Hosting: Netlify — provides the server infrastructure for rajabandotdamai32.com. Fonts: Google Fonts — delivers web fonts for typography for rajabandotdamai32.com. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-0LSM1YJSPZ. These IDs can be used to identify other websites operated by the same organization.

rajabandotdamai32.com delivers its homepage in 3422ms (server response time), which is considered slow by industry standards. The total page weight is 264 KB, and we detected 132 resource requests loading assets from 16 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 14 CSS files and 3 out of 22 JavaScript files are minified. Minifying the remaining 33 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 rajabandotdamai32.com produces approximately 0.13g 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 264 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for rajabandotdamai32.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.

rajabandotdamai32.com resolves to the IPv4 address 172.67.207.43 and also supports IPv6 (2606:4700:3036::ac43:cf2b), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: kimora.ns.cloudflare.com and rex.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 rajabandotdamai32.com is handled by stackmail.com with 1 MX records configured: mx.stackmail.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 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 rajabandotdamai32.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. The domain is registered through NameCheap, Inc. (CA). It was first registered on 2026-04-24 and is set to expire on 2027-04-24, making it 0.2 years old. Our subdomain enumeration scan discovered 1 active subdomains for rajabandotdamai32.com: www.rajabandotdamai32.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of rajabandotdamai32.com contains 1,300 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 8 H2 headings, 22 H3 headings, 14 H4 headings, 4 H5, and 0 H6 headings. The page includes 30 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 16 external links pointing to third-party websites. There are 22 external JavaScript files, 14 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: Schema.org structured data (AggregateRating, Answer, BreadcrumbList, FAQPage, IndividualProduct, ListItem, Offer, Organization, Person, Product, Question, Rating, Review, SpeakableSpecification, WebPage, and http://schema.org/Offer) and AMP (Accelerated Mobile Pages) version. Notable missing features: XML Sitemap and robots.txt. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 2 platforms: Instagram (@plazait) and Tiktok (@plazait). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for rajabandotdamai32.com is good at 63 characters: "Link Situs Togel Resmi RAJABANDOT: Portal Login Utama User 2026". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 161 characters (slightly long): "RAJABANDOT adalah situs togel resmi yang menyediakan portal login utama untuk taruhan angka aman, JP besar, dan akses an...". 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://rajabandotdamai11.com/, preventing duplicate content issues, the page language is declared as id, 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 ("Link Situs Togel Resmi RAJABANDOT: Portal Login Utama User 2..."), OG description, OG image (social sharing thumbnail), OG type (product). 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: AggregateRating, Answer, BreadcrumbList, FAQPage, IndividualProduct, ListItem, Offer, Organization, Person, Product, Question, Rating, Review, SpeakableSpecification, WebPage, and http://schema.org/Offer. 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.