demand.supply

We performed a comprehensive analysis of demand.supply on 2026-06-29. The website returned an HTTP 200 status code with a server response time of 37579ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 114 KB, and the site is served behind a CDN (Content Delivery Network). The website uses a secure HTTPS connection with a valid SSL certificate issued by Google Trust Services (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and ECDSA-SHA256 signature algorithm. The certificate covers 4 domain(s) (Subject Alternative Names) and expires on 2026-08-14, which is 46 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 4 technologies across 4 categories powering demand.supply. The detected stack includes Nuxt.js, React, Google Tag Manager, and Cloudflare. The site uses Nuxt.js as its primary framework. The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, demand.supply receives an overall trust score of 60/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, demand.supply receives a trust score of 60/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 Google Trust Services with 46 days until expiration, and a well-established domain registered for over 12.0 years, indicating long-term commitment and legitimacy. 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 demand.supply 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 Gandi SAS based in CA, with a registration date of 2014-06-22 and expiration date of 2027-06-22.

Our technology detection engine scanned demand.supply 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. Framework: Nuxt.js — provides the application framework and routing for demand.supply. UI Library: React — handles the user interface rendering and component management for demand.supply. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for demand.supply. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for demand.supply. We also extracted the following tracking identifiers: Google Tag Manager container GTM-TPPF4GQJ. These IDs can be used to identify other websites operated by the same organization.

demand.supply delivers its homepage in 37579ms (server response time), which is considered slow by industry standards. The total page weight is 114 KB, and we detected 256 resource requests loading assets from 7 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: 1 out of 8 CSS files and 0 out of 1 JavaScript files are minified. Minifying the remaining 8 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. The site is served through a Content Delivery Network (CDN), which caches static assets at edge servers around the world. This means visitors from different geographic regions receive content from the nearest edge server, significantly reducing latency. CDN usage is particularly important for websites with a global audience, as it can reduce page load times by 40-60% for distant visitors. From an environmental perspective, each page view of demand.supply produces approximately 0.06g 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 114 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for demand.supply. 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.

demand.supply resolves to the IPv4 address 104.17.38.115 and also supports IPv6 (2606:4700::6811:2673), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: alexis.ns.cloudflare.com and wally.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. 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 demand.supply. 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 Gandi SAS (CA). It was first registered on 2014-06-22 and is set to expire on 2027-06-22, making it 12.0 years old. Our subdomain enumeration scan discovered 1 active subdomains for demand.supply: api.demand.supply. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of demand.supply contains 909 words of visible text content. This is a moderate amount of content. The page is structured with 10 H2 headings, 3 H3 headings, 0 H4 headings. The page includes 25 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 34 internal links pointing to other pages on the same domain and 7 external links pointing to third-party websites. There are 1 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 (Organization, ReadAction, WebPage, and WebSite). 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 demand.supply: Discover. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates.

The title tag for demand.supply is well-optimized at 42 characters: "Sulvo - Ad Revenue Recovery for Publishers". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 131 characters (well-optimized): "Recover lost publisher ad revenue from ad blockers, AI agents, bot traffic, and weak demand with Sulvo's patented ad-tec...". 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://sulvo.com/, preventing duplicate content issues, the page language is declared as en-us, the meta robots directive is set to index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Sulvo - Ad Revenue Recovery for Publishers..."), 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: Organization, ReadAction, WebPage, and WebSite. 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. The meta keywords tag contains 7 terms including sulvo, ad revenue recovery, ad blocker recovery, header bidding, and prebid. Note: Google has officially confirmed that it does not use the meta keywords tag as a ranking signal. However, some other search engines (Bing, Yandex) may still reference it.