Get a snapshot of 34web.ru's online performance, security posture, and technology profile.
34web.ru Website Overview & Technology Report
We performed a comprehensive analysis of 34web.ru on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 8889ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 156 KB. 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 50/100 (moderate). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Frame-Options, and X-Content-Type-Options. However, the site is missing Content-Security-Policy, 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, 34web.ru receives an overall trust score of 74/100, classified as "Likely Safe".
Evaluate trustworthiness based on age, SSL, email authentication, security headers, and blacklist status across 8 threat databases.
34web.ru Trust Score & Safety Analysis
After conducting a thorough safety and legitimacy analysis, 34web.ru receives a trust score of 74/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, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, DKIM (DomainKeys Identified Mail) providing cryptographic email verification, 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, 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 34web.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.
Security Headers
Blacklist Checks 8/8 Clean ✓
Discover every technology powering this website — from CMS and frameworks to analytics, payments, and marketing tools.
34web.ru Technology Stack & Detected Technologies
Our automated technology detection scan was unable to identify specific technologies on 34web.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.
Response time, compression, CDN usage, Core Web Vitals, and environmental impact metrics for 34web.ru.
34web.ru Performance & Web Vitals Report
34web.ru delivers its homepage in 8889ms (server response time), which is considered slow by industry standards. The total page weight is 156 KB, and we detected 151 resource requests loading assets from 9 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: 1 out of 5 CSS files and 1 out of 8 JavaScript files are minified. Minifying the remaining 11 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 34web.ru produces approximately 0.08g 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 156 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for 34web.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.
Complete DNS record analysis including email authentication (SPF, DMARC, DKIM), registrar details, and subdomain discovery.
34web.ru DNS Records, Email Authentication & Domain Registration
34web.ru resolves to the IPv4 address 81.200.153.136, 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.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 34web.ru is handled by reg.ru with 2 MX records configured: mxs1.reg.ru and mxs2.reg.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 reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. DKIM (DomainKeys Identified Mail) is configured, adding a cryptographic signature to outgoing emails that receiving servers can verify to confirm the email hasn't been tampered with in transit. DNSSEC is enabled for 34web.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. Our subdomain enumeration scan discovered 3 active subdomains for 34web.ru: mail.34web.ru, smtp.34web.ru, and www.34web.ru. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
Subdomains 3 found
TXT Records / Service Verifications 4
Content structure, media assets, cookie usage, payment methods, and social media presence for 34web.ru.
34web.ru Page Content Analysis
The homepage of 34web.ru contains 728 words of visible text content. This is a moderate amount of content. The page is structured with 0 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 16 images. 1 images (6%) 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 94% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 54 internal links pointing to other pages on the same domain and 16 external links pointing to third-party websites. There are 8 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), robots.txt (controls search engine crawling behavior), and Progressive Web App (PWA) manifest (enabling app-like installation). Notable missing features: Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.
Evaluate on-page SEO factors including meta tags, Schema.org markup, content metrics, social presence, and environmental impact.
34web.ru SEO Analysis, Meta Tags & Content
The title tag for 34web.ru is good at 61 characters: "34ВЕБ - IT компания. Разработка и внедрение интернет сервисов". The length is acceptable, though it may be slightly truncated in some search result displays.
The meta description is 144 characters (well-optimized): "Разрабатываем эффективные веб-проекты для B2B, B2C и e-commerce ✔ Сайты, SEO продвижение, 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 canonical url is correctly set to https://34web.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 ("34ВЕБ - 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.