xhendra.ar

We performed a comprehensive analysis of xhendra.ar on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 3494ms. The page is served over HTTP/1.1 protocol, however no compression (Gzip or Brotli) is enabled, which means the page is transferred at its full uncompressed size. The total page weight is 12 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by Sectigo Limited (OV 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-10-11, which is 103 days from now. The security headers analysis reveals a score of 35/100 (below average). The following security headers are properly configured: Strict-Transport-Security (HSTS) and X-Frame-Options. However, the site is missing Content-Security-Policy, 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 4 technologies across 4 categories powering xhendra.ar. The detected stack includes Bootstrap 3.4.1, Google Analytics 4, StackPath, and Google Fonts. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, xhendra.ar receives an overall trust score of 69/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, xhendra.ar receives a trust score of 69/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, and a valid SSL certificate issued by Sectigo Limited with 103 days until expiration. 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 xhendra.ar 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 xhendra.ar and identified 4 distinct technologies across 4 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 (version 3.4.1) — provides the styling and responsive layout system for xhendra.ar. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for xhendra.ar. CDN: StackPath — accelerates content delivery by caching assets at edge locations worldwide for xhendra.ar. Fonts: Google Fonts — delivers web fonts for typography for xhendra.ar. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-H049D8X10Q. These IDs can be used to identify other websites operated by the same organization.

xhendra.ar delivers its homepage in 3494ms (server response time), which is considered slow by industry standards. The total page weight is 12 KB, and we detected 35 resource requests loading assets from 11 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. No compression is currently enabled on xhendra.ar. Enabling Brotli or Gzip compression could reduce page size by 60-80% for text-based assets (HTML, CSS, JavaScript), significantly improving load times and reducing bandwidth costs. This is one of the simplest and most impactful performance optimizations available. Asset minification status: 2 out of 8 CSS files and 0 out of 8 JavaScript files are minified. Minifying the remaining 14 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 xhendra.ar produces approximately 0.01g 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 12 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for xhendra.ar. 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.

xhendra.ar resolves to the IPv4 address 13.89.172.8, 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-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, and ns4-04.azure-dns.info. 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. SPF is not configured, meaning any server could potentially send emails pretending to be from this domain. This is a significant email security concern. 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 xhendra.ar. 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.

The homepage of xhendra.ar contains 101 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 2 H2 headings, 1 H3 headings, 0 H4 headings. The page includes 6 images. 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 7 internal links pointing to other pages on the same domain and 5 external links pointing to third-party websites. There are 8 external JavaScript files, 8 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 xhendra.ar is good at 14 characters: "XH Hub | Login". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 10 characters (acceptable): "User login". 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 page language is declared as es and a favicon is configured. No Open Graph tags are configured. When someone shares a link to xhendra.ar 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.