rokass.ru

We performed a comprehensive analysis of rokass.ru on 2026-07-07. The website returned an HTTP 200 status code with a server response time of 3093ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 420 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 2 domain(s) (Subject Alternative Names) and expires on 2026-08-28, which is 52 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 3 technologies across 3 categories powering rokass.ru. The detected stack includes Bootstrap, Google Fonts, and jQuery 2.2.4.. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, rokass.ru receives an overall trust score of 68/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, rokass.ru receives a trust score of 68/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 Let's Encrypt with 52 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none policy, and DNSSEC providing authenticated DNS responses. 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, and 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 rokass.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 rokass.ru and identified 3 distinct technologies across 3 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. CSS Framework: Bootstrap — provides the styling and responsive layout system for rokass.ru. Fonts: Google Fonts — delivers web fonts for typography for rokass.ru. JavaScript Library: jQuery (version 2.2.4.) — provides utility functions and DOM manipulation for rokass.ru.

rokass.ru delivers its homepage in 3093ms (server response time), which is considered slow by industry standards. The total page weight is 420 KB, and we detected 1040 resource requests loading assets from 10 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: 5 out of 9 CSS files and 17 out of 22 JavaScript files are minified. Minifying the remaining 9 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 rokass.ru produces approximately 0.21g of CO₂, earning a carbon rating of B. 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 420 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for rokass.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.

rokass.ru resolves to the IPv4 address 92.53.96.141 and also supports IPv6 (2a03:6f00:1::5c35:608d), demonstrating modern network infrastructure readiness. The domain has 1 A record(s) configured. The domain name system is managed by 4 name servers: ns1.timeweb.ru, ns2.timeweb.ru, ns3.timeweb.org, and ns4.timeweb.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 rokass.ru is handled by mail.ru with 1 MX records configured: emx.mail.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 (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 enabled for rokass.ru, 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 rokass.ru contains 3,443 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 2 H2 headings, 2 H3 headings, 0 H4 headings. The page includes 274 images. 211 images (77%) 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 23% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 392 internal links pointing to other pages on the same domain and 14 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 22 external JavaScript files, 9 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), robots.txt (controls search engine crawling behavior), and Schema.org structured data (LocalBusiness, Organization, PostalAddress, SearchAction, and WebSite).

The title tag for rokass.ru is too long at 95 characters: "Профессиональные услуги по автоматизации бизнеса: магазины, рестораны, кафе в ...". At 95 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 148 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://rokass.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 ("Профессиональные услуги по автоматизации бизнеса: магазины,..."), 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: LocalBusiness, Organization, PostalAddress, SearchAction, 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 5 terms including Услуги по автоматизации магазина, столовой, кафе и ресторана. Сервисный центр.Интернет-магазин оборудования, заказать, 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.