zenduty.com

We performed a comprehensive analysis of zenduty.com on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 2099ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 669 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by Amazon (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_128_GCM_SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-10-24, which is 116 days from now. The security headers analysis reveals a score of 80/100 (good). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy. However, the site is missing Content-Security-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 11 technologies across 9 categories powering zenduty.com. The detected stack includes Gatsby, React, Tailwind CSS, Webpack, Google Analytics 4, Microsoft Clarity, Google Tag Manager, LinkedIn Insight Tag, Twitter Pixel, Intercom, and Amazon CloudFront. The site uses Gatsby 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, zenduty.com receives an overall trust score of 80/100, classified as "Very Likely Safe".

After conducting a thorough safety and legitimacy analysis, zenduty.com receives a trust score of 80/100, which places it in the "Very 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 116 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a quarantine policy. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, 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 zenduty.com 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 zenduty.com and identified 11 distinct technologies across 9 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Framework: Gatsby — provides the application framework and routing for zenduty.com. UI Library: React — handles the user interface rendering and component management for zenduty.com. CSS Framework: Tailwind CSS — provides the styling and responsive layout system for zenduty.com. Build Tool: Webpack — bundles and optimizes the JavaScript and CSS assets for zenduty.com. Analytics: Google Analytics 4 and Microsoft Clarity — tracks visitor behavior and provides traffic insights for zenduty.com. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for zenduty.com. Advertising: LinkedIn Insight Tag and Twitter Pixel — handles advertising pixel tracking and conversion measurement for zenduty.com. Chat: Intercom — provides live chat and customer communication for zenduty.com. CDN: Amazon CloudFront — accelerates content delivery by caching assets at edge locations worldwide for zenduty.com. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-12ECK65TRM, Google Tag Manager container GTM-TXL8QKK, and Intercom App ID s7qfpz3u. These IDs can be used to identify other websites operated by the same organization.

zenduty.com delivers its homepage in 2099ms (server response time), which is considered slow by industry standards. The total page weight is 669 KB, and we detected 532 resource requests loading assets from 23 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 0 out of 18 JavaScript files are minified. Minifying the remaining 18 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 zenduty.com produces approximately 0.33g 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 669 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for zenduty.com. 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.

zenduty.com resolves to the IPv4 address 18.233.34.131 and also supports IPv6 (2600:1f18:769c:fe02::11), demonstrating modern network infrastructure readiness. The domain has 3 A record(s) configured. The domain name system is managed by 4 name servers: ns-1405.awsdns-47.org, ns-1844.awsdns-38.co.uk, ns-357.awsdns-44.com, and ns-635.awsdns-15.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 zenduty.com is handled by Google Workspace with 5 MX records configured: aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com and 2 more. 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 (Domain-based Message Authentication, Reporting and Conformance) is configured with a quarantine policy — a moderate setting, directing unauthorized emails to spam/junk folders. 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 zenduty.com. 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 zenduty.com contains 1,186 words of visible text content. This is a substantial amount of content that provides good opportunities for search engine indexing. The page is structured with 13 H2 headings, 2 H3 headings, 2 H4 headings. The page includes 350 images. 167 images (48%) 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 52% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 97 internal links pointing to other pages on the same domain and 41 external links pointing to third-party websites. There are 18 external JavaScript files, 0 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages), robots.txt (controls search engine crawling behavior), Schema.org structured data (AggregateRating, ContactPoint, Offer, Organization, PriceSpecification, QuantitativeValue, and WebApplication), and Progressive Web App (PWA) manifest (enabling app-like installation). We detected the following payment methods accepted on zenduty.com: Discover and JCB. 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 3 platforms: Twitter (@xurrenthq), Linkedin (@xurrent), and Youtube (@zenduty). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for zenduty.com is too long at 90 characters: "End-to-end Incident Management and Response Orchestration | Xurrent IMR (Formerl...". At 90 characters, the title will likely be truncated in Google search results (recommended: 50-60 characters). Consider shortening it while keeping the most important keywords at the beginning. The meta description is 395 characters (slightly long): "Resolve critical product and downtime issues before your customers are impacted. Zenduty integrates with all your monito...". 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://zenduty.com/, preventing duplicate content issues, the page language is declared as en, the meta robots directive is set to index, follow, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("End-to-end Incident Management and Response Orchestration | ..."), 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: AggregateRating, ContactPoint, Offer, Organization, PriceSpecification, QuantitativeValue, and WebApplication. 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 3 terms including Xurrent IMR, Zenduty, and Incident management. 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.