uj3wazyk5u4hnvtk.onion.ly

We performed a comprehensive analysis of uj3wazyk5u4hnvtk.onion.ly on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 2814ms. 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. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, uj3wazyk5u4hnvtk.onion.ly receives an overall trust score of 50/100, classified as "Caution Advised".

After conducting a thorough safety and legitimacy analysis, uj3wazyk5u4hnvtk.onion.ly receives a trust score of 50/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 and DKIM (DomainKeys Identified Mail) providing cryptographic email verification. 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 uj3wazyk5u4hnvtk.onion.ly 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 automated technology detection scan was unable to identify specific technologies on uj3wazyk5u4hnvtk.onion.ly. 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.

uj3wazyk5u4hnvtk.onion.ly delivers its homepage in 2814ms (server response time), which is considered slow by industry standards. The total page weight is 1 KB, and we detected 2 resource requests loading assets from 0 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 0 CSS files and 1 out of 1 JavaScript files are minified. All assets are properly minified, reducing file sizes by removing whitespace, comments, and shortening variable names. Minification is a best practice that reduces download sizes without affecting functionality. From an environmental perspective, each page view of uj3wazyk5u4hnvtk.onion.ly 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 uj3wazyk5u4hnvtk.onion.ly. 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.

uj3wazyk5u4hnvtk.onion.ly resolves to the IPv4 address 103.224.182.238, 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: ns1.abovedomains.com and ns2.abovedomains.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 uj3wazyk5u4hnvtk.onion.ly is handled by above.com with 1 MX records configured: park-mx.above.com. 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 (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 not enabled for uj3wazyk5u4hnvtk.onion.ly. 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 25 active subdomains for uj3wazyk5u4hnvtk.onion.ly: admin.uj3wazyk5u4hnvtk.onion.ly, api.uj3wazyk5u4hnvtk.onion.ly, app.uj3wazyk5u4hnvtk.onion.ly, apps.uj3wazyk5u4hnvtk.onion.ly, blog.uj3wazyk5u4hnvtk.onion.ly, cdn.uj3wazyk5u4hnvtk.onion.ly, community.uj3wazyk5u4hnvtk.onion.ly, and dev.uj3wazyk5u4hnvtk.onion.ly. Plus 17 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of uj3wazyk5u4hnvtk.onion.ly contains 5 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 1 internal link pointing to other pages on the same domain and 0 external links pointing to third-party websites. There are 1 external JavaScript files, 0 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.

The title tag for uj3wazyk5u4hnvtk.onion.ly is good at 8 characters: "onion.ly". The length is acceptable, though it may be slightly truncated in some search result displays. No meta description is configured for uj3wazyk5u4hnvtk.onion.ly. 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. No Open Graph tags are configured. When someone shares a link to uj3wazyk5u4hnvtk.onion.ly 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.