one.store

We performed a comprehensive analysis of one.store on 2026-06-29. The website returned an HTTP 200 status code with a server response time of 11834ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 70 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 3 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 20/100 (poor). The following security headers are properly configured: Strict-Transport-Security (HSTS). However, the site is missing Content-Security-Policy, 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 7 technologies across 6 categories powering one.store. The detected stack includes Magento, WooCommerce, Vite, Google Analytics 4, Crisp, Cloudflare, and YouTube Embed. The primary e-commerce platform is Magento. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, one.store receives an overall trust score of 70/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, one.store receives a trust score of 70/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 Google Trust Services with 46 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a none 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, 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 one.store 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 one.store and identified 7 distinct technologies across 6 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Ecommerce: Magento and WooCommerce — powers the online store and shopping functionality for one.store. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for one.store. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for one.store. Chat: Crisp — provides live chat and customer communication for one.store. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for one.store. Video: YouTube Embed — provides video hosting and playback for one.store.

one.store delivers its homepage in 11834ms (server response time), which is considered slow by industry standards. The total page weight is 70 KB, and we detected 101 resource requests loading assets from 19 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 2 CSS files and 3 out of 11 JavaScript files are minified. Minifying the remaining 9 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 one.store produces approximately 0.03g 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 70 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for one.store. 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.

one.store resolves to the IPv4 address 104.26.6.211 and also supports IPv6 (2606:4700:20::ac43:4937), demonstrating modern network infrastructure readiness. The domain has 3 A record(s) configured. The domain name system is managed by 2 name servers: buck.ns.cloudflare.com and gail.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. Email for one.store 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 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 not enabled for one.store. 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. Our subdomain enumeration scan discovered 5 active subdomains for one.store: admin.one.store, api.one.store, app.one.store, cdn.one.store, and www.one.store. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of one.store contains 800 words of visible text content. This is a moderate amount of content. The page is structured with 7 H2 headings, 4 H3 headings, 0 H4 headings. The page includes 33 images. 26 images (79%) 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 21% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 27 internal links pointing to other pages on the same domain and 14 external links pointing to third-party websites. There are 11 external JavaScript files, 2 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. The website has social media presence across 6 platforms: Facebook (@onestorehq), Twitter (@onestorehq), Instagram (@onestorehq), Linkedin (@onestorehq), Youtube (@UCdm8bRLc0zIU1fN1UE36tvg), and Tiktok (@onestorehq). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for one.store is well-optimized at 39 characters: "OneStore™ | ONE App to Replace Them All". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 260 characters (slightly long): "OneStore is a AI-powered customer engagement & customer data platform: Recover abandoned carts. Drive sales, AOV, loyalt...". 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 page language is declared as en, the meta robots directive is set to index, follow, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to one.store on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing. 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 meta keywords tag contains 11 terms including social, proof, notifications, conversion, and ecommerce. 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.