zeroum.bet

We performed a comprehensive analysis of zeroum.bet on 2026-07-06. The website returned an HTTP 200 status code with a server response time of 42678ms. The page is served over HTTP/2 protocol, however no compression (Gzip or Brotli) is enabled, which means the page is transferred at its full uncompressed size. The total page weight is 857 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 Amazon (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_128_GCM_SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-09-24, which is 80 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 8 technologies across 8 categories powering zeroum.bet. The detected stack includes Angular 20.3.2, React, Vite, Google Analytics 4, Google Tag Manager, Zendesk, reCAPTCHA v3, and Google Fonts. The site uses Angular as its primary framework (version 20.3.2). The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, zeroum.bet receives an overall trust score of 66/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, zeroum.bet receives a trust score of 66/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 Amazon with 80 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a none policy. 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 zeroum.bet 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 zeroum.bet and identified 8 distinct technologies across 8 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 (version 20.3.2) — provides the application framework and routing for zeroum.bet. UI Library: React — handles the user interface rendering and component management for zeroum.bet. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for zeroum.bet. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for zeroum.bet. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for zeroum.bet. Support: Zendesk — handles customer support tickets and knowledge bases for zeroum.bet. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for zeroum.bet. Fonts: Google Fonts — delivers web fonts for typography for zeroum.bet. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-SOFT and Google Tag Manager container GTM-MKXS32TF. These IDs can be used to identify other websites operated by the same organization.

zeroum.bet delivers its homepage in 42678ms (server response time), which is considered slow by industry standards. The total page weight is 857 KB, and we detected 431 resource requests loading assets from 8 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. No compression is currently enabled on zeroum.bet. Enabling Brotli or Gzip compression could reduce page size by 60-80% for text-based assets (HTML, CSS, JavaScript), significantly improving load times and reducing bandwidth costs. This is one of the simplest and most impactful performance optimizations available. Asset minification status: 0 out of 2 CSS files and 0 out of 2 JavaScript files are minified. Minifying the remaining 4 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 zeroum.bet produces approximately 0.42g of CO₂, earning a carbon rating of D. 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 857 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for zeroum.bet. 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.

zeroum.bet resolves to the IPv4 address 52.85.154.23, but does not support IPv6. IPv6 adoption is increasingly important as IPv4 address space becomes exhausted, and some ISPs and regions are transitioning to IPv6-only connectivity. The domain has 4 A record(s) configured. The domain name system is managed by 4 name servers: ns-1116.awsdns-11.org, ns-1664.awsdns-16.co.uk, ns-497.awsdns-62.com, and ns-606.awsdns-11.net. Having 4 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 zeroum.bet is handled by Google Workspace with 5 MX records configured: aspmx.l.google.com, smtp.google.com, and alt1.aspmx.l.google.com and 2 more. 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 was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is not enabled for zeroum.bet. 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 homepage of zeroum.bet contains 745 words of visible text content. This is a moderate amount of content. The page is structured with 0 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 301 images. 126 images (42%) 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 58% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 170 internal links pointing to other pages on the same domain and 8 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 2 external JavaScript files, 2 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), Schema.org structured data (ContactPoint, Organization, PostalAddress, WebPage, and WebSite), and Progressive Web App (PWA) manifest (enabling app-like installation). Notable missing features: robots.txt. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on zeroum.bet: Visa. 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 2 platforms: Twitter (@zeroumbet) and Instagram (@zeroum.bet). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for zeroum.bet is too long at 84 characters: "Zeroum | Plataforma Nova de Apostas Esportivas e Cassino Online | A Melhor do Br...". 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 161 characters (slightly long): "Zeroum oferece as melhores apostas esportivas e jogos de cassino online no Brasil. Jogue com segurança, aproveite prêmio...". 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://zeroum.bet/, preventing duplicate content issues, the page language is declared as pt, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Zeroum | Plataforma Nova de Apostas Esportivas e Cassino Onl..."), 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. The site implements Schema.org structured data with the following types: ContactPoint, Organization, PostalAddress, WebPage, and WebSite. 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 apostas esportivas Brasil, cassino online Brasil, sites de apostas confiáveis, plataforma de apostas esportivas, and plataforma de cassino. 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.