sfty.io

We performed a comprehensive analysis of sfty.io on 2026-07-04. The website returned an HTTP 200 status code with a server response time of 21870ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 270 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 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-08-22, which is 49 days from now. The security headers analysis reveals a score of 100/100 (excellent). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy. All recommended security headers are in place, providing comprehensive protection against common web attacks. Our technology detection scan identified 5 technologies across 5 categories powering sfty.io. The detected stack includes Next.js chunks, React, Google Tag Manager, LinkedIn Insight Tag, and Vercel. 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, sfty.io receives an overall trust score of 74/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, sfty.io receives a trust score of 74/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 Let's Encrypt with 49 days until expiration. Areas of concern include: 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 sfty.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 sfty.io and identified 5 distinct technologies across 5 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 sfty.io. UI Library: React — handles the user interface rendering and component management for sfty.io. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for sfty.io. Advertising: LinkedIn Insight Tag — handles advertising pixel tracking and conversion measurement for sfty.io. Hosting: Vercel — provides the server infrastructure for sfty.io. We also extracted the following tracking identifiers: Google Tag Manager container GTM-5TNTR5X. These IDs can be used to identify other websites operated by the same organization.

sfty.io delivers its homepage in 21870ms (server response time), which is considered slow by industry standards. The total page weight is 270 KB, and we detected 123 resource requests loading assets from 15 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 4 CSS files and 0 out of 31 JavaScript files are minified. Minifying the remaining 35 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 sfty.io produces approximately 0.13g 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 270 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for sfty.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.

sfty.io resolves to the IPv4 address 35.167.216.18, 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 3 A record(s) configured. The domain name system is managed by 4 name servers: ns-1420.awsdns-49.org, ns-2016.awsdns-60.co.uk, ns-224.awsdns-28.com, and ns-957.awsdns-55.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. 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 sfty.io. 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 sfty.io contains 608 words of visible text content. This is a moderate amount of content. The page is structured with 9 H2 headings, 9 H3 headings, 0 H4 headings. The page includes 21 images. 5 images (24%) 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 76% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 38 internal links pointing to other pages on the same domain and 14 external links pointing to third-party websites. There are 31 external JavaScript files, 4 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior) and Schema.org structured data (WebPage and WebSite). Notable missing features: XML Sitemap. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on sfty.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 5 platforms: Facebook (@SafetyCultureTeam), Twitter (@SafetyCultureHQ), Instagram (@safetyculturehq), Linkedin (@safetyculturehq), and Youtube (@SafetyCultureHQ). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for sfty.io is well-optimized at 54 characters: "iAuditor - Inspection Software & Mobile Inspection App". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 141 characters (well-optimized): "SafetyCulture (formerly iAuditor) is a mobile-first platform that allows you to digitize all elements of your operations...". 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://safetyculture.com/iauditor, 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 ("iAuditor - Inspection Software & Mobile Inspection App..."), 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: 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.