humo.app

We performed a comprehensive analysis of humo.app on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 51795ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 256 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 1 domain(s) (Subject Alternative Names) and expires on 2026-07-19, which is 21 days from now. 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 8 technologies across 8 categories powering humo.app. The detected stack includes Webpack, Microsoft Clarity, Google Tag Manager, Meta Pixel, Intercom, New Relic, reCAPTCHA v3, and Google Fonts. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, humo.app receives an overall trust score of 58/100, classified as "Caution Advised".

After conducting a thorough safety and legitimacy analysis, humo.app receives a trust score of 58/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: a valid HTTPS connection protecting data in transit and a valid SSL certificate issued by Let's Encrypt with 21 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, 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 humo.app 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. The domain is registered through Porkbun LLC based in US, with a registration date of 2025-08-14 and expiration date of 2026-08-14.

Our technology detection engine scanned humo.app and identified 8 distinct technologies across 8 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Build Tool: Webpack — bundles and optimizes the JavaScript and CSS assets for humo.app. Analytics: Microsoft Clarity — tracks visitor behavior and provides traffic insights for humo.app. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for humo.app. Advertising: Meta Pixel — handles advertising pixel tracking and conversion measurement for humo.app. Chat: Intercom — provides live chat and customer communication for humo.app. Monitoring: New Relic — monitors application performance and errors for humo.app. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for humo.app. Fonts: Google Fonts — delivers web fonts for typography for humo.app. We also extracted the following tracking identifiers: Google Tag Manager container GTM-M6CM29, Meta (Facebook) Pixel ID 776488579087398, and Intercom App ID ld9mkn53. These IDs can be used to identify other websites operated by the same organization.

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

humo.app resolves to the IPv4 address 52.20.84.62, 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.squadhelp.com and ns2.squadhelp.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. 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 humo.app. 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 domain is registered through Porkbun LLC (US). It was first registered on 2025-08-14 and is set to expire on 2026-08-14, making it 0.9 years old. Our subdomain enumeration scan discovered 1 active subdomains for humo.app: www.humo.app. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of humo.app contains 495 words of visible text content. This is a moderate amount of content. The page is structured with 3 H2 headings, 7 H3 headings, 0 H4 headings. The page includes 16 images. 2 images (12%) 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 88% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 40 internal links pointing to other pages on the same domain and 5 external links pointing to third-party websites. There are 3 external JavaScript files, 3 CSS stylesheets, and 1 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. We detected the following payment methods accepted on humo.app: Visa, Mastercard, American Express, and Apple Pay. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates. The website has social media presence across 2 platforms: Facebook (@tr) and Github (@newrelic). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for humo.app is good at 20 characters: "Humo.app is for sale". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 171 characters (slightly long): "Humo.app is available for sale at $7,199. It is a great fit for a fitness brand and gyms,a Medical & Dental Brand,a Food...". 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://www.fortune.domains/name/humo.app, preventing duplicate content issues, the page language is declared as en, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Humo.app is for sale at fortune.domains..."), 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.