sattamatka.wiki

We performed a comprehensive analysis of sattamatka.wiki on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 8620ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 1458 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 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 11 technologies across 9 categories powering sattamatka.wiki. The detected stack includes Angular, Vite, Google Analytics 4, Google Tag Manager, Meta Pixel, Google Ads, Twitter Pixel, VWO, New Relic, Cloudflare, and jQuery. The site uses Angular as its primary framework. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, sattamatka.wiki receives an overall trust score of 53/100, classified as "Caution Advised".

After conducting a thorough safety and legitimacy analysis, sattamatka.wiki receives a trust score of 53/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, 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 sattamatka.wiki 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.

Our technology detection engine scanned sattamatka.wiki and identified 11 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: Angular — provides the application framework and routing for sattamatka.wiki. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for sattamatka.wiki. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for sattamatka.wiki. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for sattamatka.wiki. Advertising: Meta Pixel, Google Ads, and Twitter Pixel — handles advertising pixel tracking and conversion measurement for sattamatka.wiki. A/B Testing: VWO — enables experimentation and conversion optimization for sattamatka.wiki. Monitoring: New Relic — monitors application performance and errors for sattamatka.wiki. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for sattamatka.wiki. JavaScript Library: jQuery — provides utility functions and DOM manipulation for sattamatka.wiki. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-SF0EQEXKPW, Google Tag Manager container GTM-TKQZL95, and Meta (Facebook) Pixel ID 1060020737679640. These IDs can be used to identify other websites operated by the same organization.

sattamatka.wiki resolves to the IPv4 address 104.21.10.127 and also supports IPv6 (2606:4700:3032::6815:a7f), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: derek.ns.cloudflare.com and wren.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. 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 sattamatka.wiki. 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 sattamatka.wiki: www.sattamatka.wiki. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The title tag for sattamatka.wiki is too long at 84 characters: "WADUK88 $ Trusted Online Gaming Site with Easy Jackpots & Viral Games Every Day ...". At 84 characters, the title will likely be truncated in Google search results (recommended: 50-60 characters). Consider shortening it while keeping the most important keywords at the beginning. The meta description is 391 characters (slightly long): "WADUK88 hadir sebagai trusted online gaming site dengan akses cepat, tampilan modern, dan pengalaman bermain yang semaki...". 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://sattamatka.wiki/, preventing duplicate content issues, the page language is declared as id-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 ("WADUK88 $ Trusted Online Gaming Site with Easy Jackpots & Vi..."), 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 is configured, which controls how links appear when shared on Twitter/X. The "summary" 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: AggregateOffer, AggregateRating, Brand, BreadcrumbList, ItemList, ListItem, Organization, PostalAddress, Product, and Store. 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. The meta keywords tag contains 6 terms including waduk88, waduk88 login, waduk88 daftar, link alternatif waduk88, and waduk88 link. 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.