fei36.ru

We performed a comprehensive analysis of fei36.ru on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 15324ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 260 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-05, which is 38 days from now. The security headers analysis reveals a score of 30/100 (below average). The following security headers are properly configured: X-Frame-Options and X-Content-Type-Options. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), 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 5 technologies across 5 categories powering fei36.ru. The detected stack includes WordPress 7.0, WooCommerce, Google Fonts, jQuery, and Font Awesome. The primary e-commerce platform is WooCommerce. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, fei36.ru receives an overall trust score of 68/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, fei36.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 38 days until expiration, 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, 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 fei36.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 fei36.ru and identified 5 distinct technologies across 5 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. CMS: WordPress (version 7.0) — manages the content and page structure for fei36.ru. Ecommerce: WooCommerce — powers the online store and shopping functionality for fei36.ru. Fonts: Google Fonts — delivers web fonts for typography for fei36.ru. JavaScript Library: jQuery — provides utility functions and DOM manipulation for fei36.ru. Icon Set: Font Awesome — provides additional functionality for fei36.ru.

fei36.ru delivers its homepage in 15324ms (server response time), which is considered slow by industry standards. The total page weight is 260 KB, and we detected 291 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: 3 out of 8 CSS files and 4 out of 12 JavaScript files are minified. Minifying the remaining 13 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 fei36.ru produces approximately 0.13g 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 260 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for fei36.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.

fei36.ru resolves to the IPv4 address 5.101.114.102, 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 3 name servers: dns1.dns-root.ru, dns2.dns-root.org, and dns3.dns-root.pro. Having 3 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 fei36.ru is handled by fei36.ru with 1 MX records configured: mail.fei36.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 fei36.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 fei36.ru: mail.fei36.ru and www.fei36.ru. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of fei36.ru contains 1,693 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 10 H2 headings, 55 H3 headings, 24 H4 headings. The page includes 1 image. All images have proper alt text attributes ✓, which is excellent for both accessibility (screen readers) and SEO (search engines can understand image content). The link structure consists of 246 internal links pointing to other pages on the same domain and 0 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 12 external JavaScript files, 8 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: Schema.org structured data (BreadcrumbList, CollectionPage, EntryPoint, ImageObject, PropertyValueSpecification, SearchAction, WebSite, and organization) and RSS feed for content syndication. Notable missing features: XML Sitemap and robots.txt. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on fei36.ru: Visa. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates.

The title tag for fei36.ru is too long at 140 characters: "Планета событий ⋆ Все самое интересное и актуально в мире и России. Последние но...". At 140 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 122 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://wikitrucks.ru/, preventing duplicate content issues, the page language is declared as ru-ru, and the meta robots directive is set to index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1. 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. 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: BreadcrumbList, CollectionPage, EntryPoint, ImageObject, PropertyValueSpecification, SearchAction, WebSite, and 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.