🌐

onex.ru

✓ HTTP/1.1 ✓ Gzip 60.0% ⚡ 5388ms
onex.ru Overview

Get a snapshot of onex.ru's online performance, security posture, and technology profile.

onex.ru Website Overview & Technology Report

48
Trust Score
Caution Advised
0
Security
Headers: 0/6
5388ms
Response
Slow
1
Technologies
Detected
🤖 AI Analysis

We performed a comprehensive analysis of onex.ru on 2026-07-03. The website returned an HTTP 200 status code with a server response time of 5388ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 1 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 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 1 technologies across 1 categories powering onex.ru. The detected stack includes React. The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, onex.ru receives an overall trust score of 48/100, classified as "Caution Advised".

Status Code200 OK
HTTP VersionHTTP/1.1
Servernginx/1.18.0 (Ubuntu)
Page Size1 KB
Total Requests8
3rd Party Domains1
SSL Certificate
TLS Version
IP Address194.67.78.208
Categories.RU ⚙️ React
onex.ru Trust & Safety

Evaluate trustworthiness based on age, SSL, email authentication, security headers, and blacklist status across 8 threat databases.

onex.ru Trust Score & Safety Analysis

48
Trust Score
0
Security
🤖 Trust Analysis

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

SPF
+3
SSL Certificate
−10
Security Headers
−5

Security Headers

Content-Security-Policy✗ Missing
HSTS✗ Missing
X-Frame-Options✗ Missing
X-Content-Type-Options✗ Missing
Referrer-Policy✗ Missing
Permissions-Policy✗ Missing

Blacklist Checks 8/8 Clean ✓

Google Safe Browsing
Phishtank
Urlhaus
Openphish
Dnsfilter
Spamhaus Dbl
Surbl
Virustotal

🔍 Analyze Your Own Website

Check your site's trust score, security headers, tech stack and 50+ metrics — completely free.

Analyze Now →
onex.ru Technology Stack 1 detected

Discover every technology powering this website — from CMS and frameworks to analytics, payments, and marketing tools.

onex.ru Technology Stack & Detected Technologies

🤖 Stack Analysis

Our technology detection engine scanned onex.ru and identified 1 distinct technologies across 1 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. UI Library: React — handles the user interface rendering and component management for onex.ru.

⚛️ UI Library
onex.ru Performance & Web Vitals

Response time, compression, CDN usage, Core Web Vitals, and environmental impact metrics for onex.ru.

onex.ru Performance & Web Vitals Report

🤖 Performance Analysis

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

Response Time5388ms Slow
Page Size1 KB
CompressionGzip 60.0% savings
CDNNot detected
onex.ru DNS & Domain Info

Complete DNS record analysis including email authentication (SPF, DMARC, DKIM), registrar details, and subdomain discovery.

onex.ru DNS Records, Email Authentication & Domain Registration

🤖 DNS Analysis

onex.ru resolves to the IPv4 address 194.67.78.208, 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 2 name servers: maeve.ns.cloudflare.com and nash.ns.cloudflare.com. 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 onex.ru is handled by Google Workspace with 5 MX records configured: aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com and 2 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 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 onex.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.

IP Address194.67.78.208
Nameserversmaeve.ns.cloudflare.com
MX ProviderGoogle Workspace (aspmx.l.google.com)
SPF✓ Configured
DMARC✗ Not set
DKIM✗ Not found
DNSSEC✗ Not enabled
IPv6Not detected
WHOIS Privacy🔒 Private

TXT Records / Service Verifications 3

Globalsign ✓ Google ✓ +1 more
onex.ru Page Analysis

Content structure, media assets, cookie usage, payment methods, and social media presence for onex.ru.

onex.ru Page Content Analysis

🤖 Content Analysis

The homepage of onex.ru contains 4 words of visible text content. This is a relatively short page — adding more descriptive content could improve search engine visibility. The page is structured with 0 H2 headings, 0 H3 headings, 0 H4 headings. The link structure consists of 0 internal links pointing to other pages on the same domain and 0 external links pointing to third-party websites. There are 6 external JavaScript files, 1 CSS stylesheets, and 0 iframes on the page. Notable missing features: XML Sitemap, robots.txt, and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.

Word Count4 words
Images0 total · 100% alt coverage
Internal Links0
External Links0
JS Files6
CSS Files1
onex.ru SEO & Content Analysis

Evaluate on-page SEO factors including meta tags, Schema.org markup, content metrics, social presence, and environmental impact.

onex.ru SEO Analysis, Meta Tags & Content

🤖 SEO Analysis

The title tag for onex.ru is well-optimized at 32 characters: "". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. <strong>No meta description is configured</strong> for onex.ru. This is a critical SEO oversight — without a meta description, Google will auto-generate a snippet from page content, which may not accurately represent the page or entice users to click. Adding a unique, compelling meta description of 120-155 characters is strongly recommended. The page language is declared as <strong>ru</strong> and a <strong>favicon</strong> is configured. <strong>No Open Graph tags</strong> are configured. When someone shares a link to onex.ru on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing.</p> </div> <div class="data-row"><span class="data-key">Title</span><span class="data-val"><span style="font-size:13px;max-width:220px;"><title data-react-helmet="true"></span></span></div><div class="data-row"><span class="data-key">H1</span><span class="data-val"><span class="mono" style="font-size:12px;"></span></span></div><div class="data-row"><span class="data-key">Word Count</span><span class="data-val">4 words</span></div><div class="data-row"><span class="data-key">Images</span><span class="data-val">0 total</span></div><div class="data-row"><span class="data-key">Internal Links</span><span class="data-val">0</span></div><div class="data-row"><span class="data-key">External Links</span><span class="data-val">0</span></div><div class="data-row"><span class="data-key">JS Files</span><span class="data-val">6</span></div><div class="data-row"><span class="data-key">CSS Files</span><span class="data-val">1</span></div><div class="data-row"><span class="data-key">X-Powered-By</span><span class="data-val"><span class="mono">Express</span></span></div><div class="data-row"><span class="data-key">Minification</span><span class="data-val">JS: 0/6 minified · CSS: 0/1 minified</span></div><div class="data-row"><span class="data-key">Sitemap</span><span class="data-val"><span class="badge red">✗ Not found</span></span></div><div class="data-row"><span class="data-key">Robots.txt</span><span class="data-val"><span class="badge red">✗ Not found</span></span></div><div class="data-row"><span class="data-key">Canonical</span><span class="data-val"><span class="badge gray">Not set</span></span></div><div class="data-row"><span class="data-key">Language</span><span class="data-val">ru</span></div><div class="data-row"><span class="data-key">Open Graph</span><span class="data-val"><span class="badge gray">Not set</span></span></div><div class="data-row"><span class="data-key">Twitter Card</span><span class="data-val"><span class="badge gray">Not set</span></span></div><div class="data-row"><span class="data-key">PWA</span><span class="data-val"><span class="badge gray">Not detected</span></span></div><div class="data-row"><span class="data-key">RSS Feed</span><span class="data-val"><span class="badge gray">Not detected</span></span></div><div class="data-row"><span class="data-key">AMP</span><span class="data-val"><span class="badge gray">Not detected</span></span></div> <h3 style="font-size:16px;font-weight:700;margin:24px 0 12px;">Google SERP Preview</h3> <div style="background:var(--surface2);border:1px solid var(--border);border-radius:10px;padding:16px;margin:16px 0;"> <div style="font-size:18px;color:#1a0dab;font-weight:400;cursor:pointer;"><title data-react-helmet="true"></div> <div style="font-size:14px;color:#006621;margin:2px 0;">https://onex.ru</div> <div style="font-size:13px;color:var(--text2);line-height:1.4;"></div> </div> <h3 style="font-size:16px;font-weight:700;margin:24px 0 12px;">META TAGS & SCHEMA.ORG</h3> <div style="display:grid;grid-template-columns:1fr 1fr;gap:16px;"> <div> <h4 style="font-size:13px;font-weight:700;color:var(--text2);text-transform:uppercase;letter-spacing:0.06em;margin-bottom:8px;">META TAGS</h4> <div class="data-row"><span class="data-key">Title</span><span class="data-val"><span class="mono" style="font-size:12px;max-width:200px;word-break:break-all;"><title data-react-helmet="true"></span></span></div> <div class="data-row"><span class="data-key">Title Length</span><span class="data-val">32 chars <span class="badge green">Good</span></span></div> <div class="data-row"><span class="data-key">Meta Desc Length</span><span class="data-val">0 chars <span class="badge amber">Too short</span></span></div> <div class="data-row"><span class="data-key">H1</span><span class="data-val"><span class="mono" style="font-size:12px;">—</span></span></div> <div class="data-row"><span class="data-key">Language</span><span class="data-val">ru</span></div> <div class="data-row"><span class="data-key">Canonical</span><span class="data-val"><span class="badge gray">Not set</span></span></div> <div class="data-row"><span class="data-key">Meta Robots</span><span class="data-val"><span class="mono" style="font-size:12px;">—</span></span></div> </div> <div> <h4 style="font-size:13px;font-weight:700;color:var(--text2);text-transform:uppercase;letter-spacing:0.06em;margin-bottom:8px;">SCHEMA.ORG & SOCIAL</h4> <div class="data-row"><span class="data-key">Schema Types</span><span class="data-val"><span style="font-size:12px;">—</span></span></div> <div class="data-row"><span class="data-key">OG Type</span><span class="data-val">—</span></div> <div class="data-row"><span class="data-key">OG Image</span><span class="data-val"><span class="badge gray">Not set</span></span></div> <div class="data-row"><span class="data-key">Twitter Card</span><span class="data-val"><span class="badge gray">Not set</span></span></div> <div class="data-row"><span class="data-key">Favicon</span><span class="data-val"><span class="badge green">✓ Found</span></span></div> </div> </div> <style>@media(max-width:600px){[style*="grid-template-columns:1fr 1fr"]{grid-template-columns:1fr!important}}</style> </div> </div> <!-- ─── RELATED (NEW) ─── --> <div class="section-card" id="related"> <div class="section-header"> <div class="section-title"> <span class="domain-prefix">onex.ru</span> Related Domains </div> <p class="section-desc">Domains sharing tracking IDs, IP addresses, or analytics properties with onex.ru.</p> </div> <div class="section-body"> <h2 style="display:none;">onex.ru Related Domains & Cross-Referenced Sites</h2> <div style="padding:20px;text-align:center;color:var(--text2);font-size:14px;">Related domain data becomes available after batch crawling.</div> </div> </div> <!-- CTA BANNER 2 --> <div class="cta-banner" style="background: linear-gradient(135deg, #1E293B, #334155);"> <h3>📊 Compare With Your Competitors</h3> <p>See how your website stacks up against onex.ru in trust, speed, security, and technology.</p> <a href="https://bitverzo.com" class="cta-btn">Compare Now →</a> </div> <!-- ─── BROWSE BY CATEGORY ─── --> <div class="section-card" style="background:var(--surface);border:1px solid var(--border);"> <div class="section-body" style="padding:20px;"> <h3 style="font-size:16px;font-weight:700;color:var(--text);margin:0 0 14px;display:flex;align-items:center;gap:8px;"> 📂 Browse by Category </h3> <div style="display:flex;flex-wrap:wrap;gap:8px;"> <a href="/tech/react" style="display:inline-block;padding:6px 14px;background:var(--accent-sub);color:var(--accent);border:1px solid var(--accent-border);border-radius:20px;text-decoration:none;font-size:13px;font-weight:500;">⚙️ React</a> <a href="/tld/ru" style="display:inline-block;padding:6px 14px;background:var(--accent-sub);color:var(--accent);border:1px solid var(--accent-border);border-radius:20px;text-decoration:none;font-size:13px;font-weight:500;">🌐 .RU domains</a> <a href="/top/trust-score" style="display:inline-block;padding:6px 14px;background:var(--accent-sub);color:var(--accent);border:1px solid var(--accent-border);border-radius:20px;text-decoration:none;font-size:13px;font-weight:500;">🏆 Top Trust Scores</a> <a href="/categories" style="display:inline-block;padding:6px 14px;background:var(--accent-sub);color:var(--accent);border:1px solid var(--accent-border);border-radius:20px;text-decoration:none;font-size:13px;font-weight:500;">📋 All Categories</a> </div> </div> </div> <!-- ─── RELATED REPORTS (internal links) ─── --> <!-- Badge CTA --> <div style="background:linear-gradient(135deg,#7C3AED 0%,#a78bfa 100%);border-radius:16px;padding:28px 32px;margin:32px 0;color:white;text-align:center;"> <div style="font-size:20px;font-weight:700;margin-bottom:8px;">🛡 Is this your website?</div> <p style="margin-bottom:16px;opacity:0.9;">Show visitors your trust score — add a free badge to your site</p> <div style="display:flex;justify-content:center;align-items:center;gap:16px;flex-wrap:wrap;"> <img src="/badge/onex.ru" alt="Trust Score Badge" height="28" style="border-radius:4px;"> <a href="/embed" style="display:inline-block;padding:10px 24px;background:white;color:#7C3AED;border-radius:10px;font-weight:700;text-decoration:none;font-size:14px;">Get Your Badge →</a> </div> </div> </div><!-- /content --> <!-- ═══ FOOTER ═══ --> <footer class="report-footer"> <div>Last analyzed: July 03, 2026 19:39 UTC · Crawled in 7,517ms</div> <div style="margin-top:8px;"> <a href="https://bitverzo.com">Analyze another domain →</a> </div> <div style="margin-top:12px;font-size:11px;color:var(--text3);"> © 2026 Bitverzo.com · Free Website Analysis & Trust Score · <a href="/privacy" style="color:var(--text3);">Privacy</a> · <a href="/about" style="color:var(--text3);">About</a> </div> <p style="margin-top:8px;max-width:800px;margin-left:auto;margin-right:auto;font-size:11px;color:var(--text3);"> Bitverzo provides free, comprehensive website analysis including technology stack detection, SSL certificate verification, DNS record inspection, security header auditing, trust scoring, SEO metadata evaluation, and page content analysis for any domain. </p> </footer> <!-- SCROLL TO TOP --> <button class="scroll-top" id="scrollTop" onclick="window.scrollTo({top:0,behavior:'smooth'})">↑</button> <script> // Sticky nav pill tracking const sections = document.querySelectorAll('.section-card[id]'); const pills = document.querySelectorAll('.nav-pill[data-target]'); // Click navigation pills.forEach(pill => { pill.addEventListener('click', () => { const target = document.getElementById(pill.dataset.target); if (target) { const offset = 56 + 48 + 16; window.scrollTo({ top: target.offsetTop - offset, behavior: 'smooth' }); } }); }); // Scroll spy const observer = new IntersectionObserver(entries => { entries.forEach(entry => { if (entry.isIntersecting) { pills.forEach(p => p.classList.remove('active')); const pill = document.querySelector(`.nav-pill[data-target="${entry.target.id}"]`); if (pill) { pill.classList.add('active'); pill.scrollIntoView({ inline: 'center', behavior: 'smooth', block: 'nearest' }); } } }); }, { rootMargin: '-120px 0px -60% 0px', threshold: 0 }); sections.forEach(s => observer.observe(s)); // Scroll-to-top button window.addEventListener('scroll', () => { document.getElementById('scrollTop').classList.toggle('visible', window.scrollY > 400); }); </script> <script>window.ezstandalone=window.ezstandalone||{};ezstandalone.cmd=ezstandalone.cmd||[];ezstandalone.cmd.push(function(){ezstandalone.showAds({location:"top_of_page"});ezstandalone.showAds({location:"under_first_paragraph"});ezstandalone.showAds({location:"mid_content"});ezstandalone.showAds({location:"bottom_of_page"});});</script></body> </html>