73hq.com

We performed a comprehensive analysis of 73hq.com on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 14331ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 38 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. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, 73hq.com receives an overall trust score of 53/100, classified as "Caution Advised".

After conducting a thorough safety and legitimacy analysis, 73hq.com 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 73hq.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.

Our automated technology detection scan was unable to identify specific technologies on 73hq.com. This could indicate that the site uses server-side rendering without client-side technology fingerprints, employs aggressive code obfuscation, or uses custom-built solutions that don't match known technology signatures.

73hq.com delivers its homepage in 14331ms (server response time), which is considered slow by industry standards. The total page weight is 38 KB, and we detected 56 resource requests loading assets from 1 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 1 CSS files and 0 out of 1 JavaScript files are minified. Minifying the remaining 2 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 73hq.com produces approximately 0.02g 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 38 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for 73hq.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.

73hq.com resolves to the IPv4 address 104.21.45.250 and also supports IPv6 (2606:4700:3037::6815:2dfa), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: felipe.ns.cloudflare.com and kara.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 73hq.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 1 active subdomains for 73hq.com: www.73hq.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of 73hq.com contains 2,187 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 18 H2 headings, 51 H3 headings, 10 H4 headings. The page includes 8 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 43 internal links pointing to other pages on the same domain and 0 external links pointing to third-party websites. There are 1 external JavaScript files, 1 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages) and Schema.org structured data (AggregateRating, Casino, Country, Game, GeoCoordinates, ImageObject, Offer, PostalAddress, QuantitativeValue, and WebSite). Notable missing features: robots.txt. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on 73hq.com: 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 3 platforms: Facebook (@73h), Twitter (@73h), and Instagram (@73h). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for 73hq.com is good at 63 characters: "73h Brasil | Slots, Crash, Cassino ao Vivo e Apostas Esportivas". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 172 characters (slightly long): "73h é um site de jogos e apostas para o público brasileiro, com slots, jogos de crash, mesas ao vivo e apostas esportiva...". 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://73hq.com/, preventing duplicate content issues, the page language is declared as pt, 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 ("73h Brasil | Slots, Crash, Cassino ao Vivo e Apostas Esporti..."), 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. The site implements Schema.org structured data with the following types: AggregateRating, Casino, Country, Game, GeoCoordinates, ImageObject, Offer, PostalAddress, QuantitativeValue, 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.