otus.ru

We performed a comprehensive analysis of otus.ru on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 7940ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 311 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 13 domain(s) (Subject Alternative Names) and expires on 2026-07-23, which is 23 days from now. The security headers analysis reveals a score of 65/100 (moderate). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Content-Type-Options, Referrer-Policy, and Permissions-Policy. However, the site is missing Content-Security-Policy and X-Frame-Options, which could expose the site and its users to cross-site scripting (XSS), clickjacking, and other web-based attacks. Our technology detection scan identified 4 technologies across 4 categories powering otus.ru. The detected stack includes Next.js images, React, Webpack, and Google Analytics 4. The site uses Next.js as its primary framework (version images). The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, otus.ru receives an overall trust score of 78/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, otus.ru receives a trust score of 78/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 23 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a quarantine 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), 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 otus.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.

Our technology detection engine scanned otus.ru and identified 4 distinct technologies across 4 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Framework: Next.js (version images) — provides the application framework and routing for otus.ru. UI Library: React — handles the user interface rendering and component management for otus.ru. Build Tool: Webpack — bundles and optimizes the JavaScript and CSS assets for otus.ru. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for otus.ru. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-410987. These IDs can be used to identify other websites operated by the same organization.

otus.ru delivers its homepage in 7940ms (server response time), which is considered slow by industry standards. The total page weight is 311 KB, and we detected 229 resource requests loading assets from 5 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 5 CSS files and 0 out of 40 JavaScript files are minified. Minifying the remaining 45 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 otus.ru produces approximately 0.15g 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 311 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for otus.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.

otus.ru resolves to the IPv4 address 195.209.87.168, 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 5 A record(s) configured. The domain name system is managed by 2 name servers: ns1.ngenix-dns.ru and ns2.ngenix-dns.ru. 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 otus.ru is handled by lancloud.ru with 4 MX records configured: mx01.lancloud.ru, mx02.lancloud.ru, and mx03.lancloud.ru and 1 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 quarantine policy — a moderate setting, directing unauthorized emails to spam/junk folders. 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 otus.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 2 active subdomains for otus.ru: cdn.otus.ru and www.otus.ru. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of otus.ru contains 1,276 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 6 H2 headings, 0 H3 headings, 0 H4 headings, 0 H5, and 17 H6 headings. The page includes 21 images. 13 images (62%) 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 38% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 128 internal links pointing to other pages on the same domain and 5 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 40 external JavaScript files, 5 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 (Organization), 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.

The title tag for otus.ru is well-optimized at 52 characters: "ОТУС - образовательная платформа с IT-курсами онлайн". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 265 characters (slightly long): "Платформа онлайн-образования ОТУС: образовательных программ (IT-курсы) как для начинающих с нуля по программированию, ан...". 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 page language is declared as ru and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("ОТУС - образовательная платформа с IT-курсами онлайн..."), 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: Organization. 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.