intv.ru

🤖 AI Summary

After conducting a thorough safety and legitimacy analysis, intv.ru receives a trust score of 56/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 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, 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 intv.ru 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.

🤖 AI Summary

Our automated technology detection scan was unable to identify specific technologies on intv.ru. 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.

🤖 AI Summary

intv.ru delivers its homepage in 25541ms (server response time), which is considered slow by industry standards. The total page weight is 35 KB, and we detected 22 resource requests loading assets from 3 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. From an environmental perspective, each page view of intv.ru 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 35 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for intv.ru. 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.

🤖 AI Summary

intv.ru resolves to the IPv4 address 91.236.136.105, 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 4 name servers: ns1.webhost1.com, ns2.webhost1.com, ns3.webhost1.org, and ns4.webhost1.org. 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 intv.ru is handled by intv.ru with 1 MX records configured: mail.intv.ru. 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 intv.ru. 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 4 active subdomains for intv.ru: ftp.intv.ru, mail.intv.ru, smtp.intv.ru, and www.intv.ru. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

🤖 AI Summary

The homepage of intv.ru contains 1,284 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 4 H2 headings, 8 H3 headings, 0 H4 headings. The page includes 4 images. 1 images (25%) 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 75% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 8 internal links pointing to other pages on the same domain and 5 external links pointing to third-party websites. There are 0 external JavaScript files, 0 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior). Notable missing features: XML Sitemap and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.

🤖 AI Summary

The title tag for intv.ru is well-optimized at 31 characters: "INTV — 1998 / 2026. Возвращение". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 169 characters (slightly long): "В 1998 я зарегистрировал intv.com и хотел сделать мировой центр видео. В 2005 пришёл YouTube. В 2026 я вернулся — с деце...". 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://intv.ru/, preventing duplicate content issues, the page language is declared as ru, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("INTV — 1998 / 2026. Возвращение..."), OG description, OG image (social sharing thumbnail), OG type (article). 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.

🤖 AI Summary

Related domain discovery works by finding other websites that share the same IP address, Google Tag Manager container ID, Google Analytics property, or advertising pixel IDs with intv.ru. This data becomes available after batch-crawling the domain database — individual domain lookups cannot populate this section. No tracking IDs were detected on this page that could be used for cross-domain matching.