xn--hhr917d3fecva.xyz

We performed a comprehensive analysis of xn--hhr917d3fecva.xyz on 2026-07-01. The website returned an HTTP 200 status code with a server response time of 10127ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 64 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by Let's Encrypt (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 11 domain(s) (Subject Alternative Names) and expires on 2026-08-30, which is 60 days from now. The security headers analysis reveals a score of 100/100 (excellent). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy. All recommended security headers are in place, providing comprehensive protection against common web attacks. Our technology detection scan identified 1 technologies across 1 categories powering xn--hhr917d3fecva.xyz. The detected stack includes Google Analytics 4. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, xn--hhr917d3fecva.xyz receives an overall trust score of 79/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, xn--hhr917d3fecva.xyz receives a trust score of 79/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, a valid SSL certificate issued by Let's Encrypt with 60 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DNSSEC providing authenticated DNS responses. Areas of concern include: the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked xn--hhr917d3fecva.xyz 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 xn--hhr917d3fecva.xyz and identified 1 distinct technologies across 1 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for xn--hhr917d3fecva.xyz. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-EHV3NGYEQ0. These IDs can be used to identify other websites operated by the same organization.

xn--hhr917d3fecva.xyz delivers its homepage in 10127ms (server response time), which is considered slow by industry standards. The total page weight is 64 KB, and we detected 244 resource requests loading assets from 18 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 22 JavaScript files are minified. Minifying the remaining 23 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. From an environmental perspective, each page view of xn--hhr917d3fecva.xyz produces approximately 0.03g 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 64 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for xn--hhr917d3fecva.xyz. 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.

xn--hhr917d3fecva.xyz resolves to the IPv4 address 160.251.152.42, 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 1 A record(s) configured. The domain name system is managed by 2 name servers: ns1.cbsv.jp and ns2.cbsv.jp. 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 xn--hhr917d3fecva.xyz is handled by xn--hhr917d3fecva.xyz with 1 MX records configured: xn--hhr917d3fecva.xyz. 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 enabled for xn--hhr917d3fecva.xyz, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites.

The homepage of xn--hhr917d3fecva.xyz contains 276 words of visible text content. This is a relatively short page — adding more descriptive content could improve search engine visibility. The page is structured with 0 H2 headings, 5 H3 headings, 7 H4 headings. The page includes 73 images. 49 images (67%) 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 33% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 70 internal links pointing to other pages on the same domain and 74 external links pointing to third-party websites. There are 22 external JavaScript files, 1 CSS stylesheets, and 0 iframes on the page. Notable missing features: XML Sitemap, robots.txt, and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.

The title tag for xn--hhr917d3fecva.xyz is good at 9 characters: "痴漢動画へようこそ". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 108 characters (well-optimized): "痴漢動画へようこそでは痴漢関連の無料エロ動画を毎日更新しています。尚、騙しリンクはありませんので安心してご覧ください。電車内やバス内で痴漢願望があり実行したら犯罪になりますので、痴漢動画で発散しちゃいましょう！（笑）". 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://xn--hhr917d3fecva.xyz/, preventing duplicate content issues, the page language is declared as ja, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to xn--hhr917d3fecva.xyz on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing. The meta keywords tag contains 5 terms including 痴漢動画, 無料痴漢動画, 痴漢, 痴漢AV, and 痴漢エロ. 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.