contentstack.io

We performed a comprehensive analysis of contentstack.io on 2026-06-29. The website returned an HTTP 200 status code with a server response time of 92628ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 576 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 Amazon (DV type). The connection is encrypted using TLS 1.2 with the ECDHE-RSA-AES128-GCM-SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 1 domain(s) (Subject Alternative Names) and expires on 2026-12-21, which is 175 days from now. The security headers analysis reveals a score of 70/100 (good). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Content-Type-Options, and Referrer-Policy. However, the site is missing X-Frame-Options 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 10 technologies across 8 categories powering contentstack.io. The detected stack includes Next.js chunks, React, Vite, Google Analytics 4, Google Tag Manager, Meta Pixel, LinkedIn Insight Tag, Google Ads, Marketo, and Google Fonts. The site uses Next.js as its primary framework (version chunks). The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, contentstack.io receives an overall trust score of 79/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, contentstack.io receives a trust score of 79/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, a valid SSL certificate issued by Amazon with 175 days until expiration, DMARC email authentication with a none policy, and DNSSEC providing authenticated DNS responses. Areas of concern include: no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking) and the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked contentstack.io 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 contentstack.io and identified 10 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. Framework: Next.js (version chunks) — provides the application framework and routing for contentstack.io. UI Library: React — handles the user interface rendering and component management for contentstack.io. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for contentstack.io. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for contentstack.io. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for contentstack.io. Advertising: Meta Pixel, LinkedIn Insight Tag, and Google Ads — handles advertising pixel tracking and conversion measurement for contentstack.io. Marketing: Marketo — provides marketing automation capabilities for contentstack.io. Fonts: Google Fonts — delivers web fonts for typography for contentstack.io. We also extracted the following tracking identifiers: Google Tag Manager container GTM-KH4PBVN. These IDs can be used to identify other websites operated by the same organization.

contentstack.io delivers its homepage in 92628ms (server response time), which is considered slow by industry standards. The total page weight is 576 KB, and we detected 317 resource requests loading assets from 31 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 2 CSS files and 0 out of 25 JavaScript files are minified. Minifying the remaining 27 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 contentstack.io produces approximately 0.28g of CO₂, earning a carbon rating of C. This is an average carbon footprint. Optimizing images and reducing unnecessary scripts could further improve this score. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 576 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for contentstack.io. 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.

contentstack.io resolves to the IPv4 address 52.35.10.203, 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 2 A record(s) configured. The domain name system is managed by 4 name servers: ns-114.awsdns-14.com, ns-1302.awsdns-34.org, ns-1986.awsdns-56.co.uk, and ns-743.awsdns-28.net. 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. Email for contentstack.io is handled by gandi.net with 2 MX records configured: spool.mail.gandi.net and fb.mail.gandi.net. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. 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 (Domain-based Message Authentication, Reporting and Conformance) is configured with a none policy — a monitoring-only setting that doesn't enforce any action on unauthorized emails. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is enabled for contentstack.io, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites. Our subdomain enumeration scan discovered 7 active subdomains for contentstack.io: api.contentstack.io, cdn.contentstack.io, docs.contentstack.io, smtp.contentstack.io, static.contentstack.io, webmail.contentstack.io, and www.contentstack.io. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of contentstack.io contains 934 words of visible text content. This is a moderate amount of content. The page is structured with 18 H2 headings, 12 H3 headings, 0 H4 headings. The page includes 67 images. 13 images (19%) 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 81% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 171 internal links pointing to other pages on the same domain and 19 external links pointing to third-party websites. The high number of internal links suggests a well-interconnected site structure, which helps search engines discover and crawl all pages efficiently. There are 25 external JavaScript files, 2 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: Schema.org structured data (EntryPoint, ImageObject, Organization, SearchAction, 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 contentstack.io: Discover. 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 6 platforms: Facebook (@contentstack), Twitter (@contentstack), Instagram (@contentstack), Linkedin (@contentstack), Youtube (@contentstack), and Github (@contentstack). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for contentstack.io is well-optimized at 42 characters: "Agentic Experience Platform | Contentstack". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 347 characters (slightly long): "Contentstack is the creator of the industry’s first Agentic Experience Platform (AXP). By unifying a composable Content ...". 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.contentstack.com, 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 ("Agentic Experience Platform | Contentstack..."), 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: EntryPoint, ImageObject, Organization, SearchAction, 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.