Security report for one.store
Domains By Proxy, LLC (registrant proxy), business brand: OneStore · Technology · United States
Medium risk. 4 critical or high findings in Security headers, GDPR outside view and 1 other check.
OneStore is a US-based SaaS company founded in 2021 that provides an AI-powered customer engagement and marketing automation platform tailored for e-commerce businesses. The platform integrates with major e-commerce marketplaces and platforms such as Shopify, TikTok Shop, eBay, Etsy, and Amazon, offering features like abandoned cart recovery, social proof notifications, gamified popups, email and SMS marketing, and A/B testing. The website is professionally designed, mobile-optimized, and rich in customer testimonials and case studies, reflecting a strong market position with over 150,000 businesses served and thousands of positive reviews on the Shopify App Store. Technically, the website employs a modern tech stack including JavaScript libraries, Google Analytics, LeadDyno affiliate tracking, ProfitWell revenue analytics, and Iubenda for cookie consent management. Hosting and DNS are managed via Cloudflare, ensuring good performance and security. The site uses HTTPS with domain locking via EPP status codes but lacks DNSSEC. Cookie consent is implemented, but explicit privacy policy and terms of service pages were not found in the provided content. From a security perspective, the site follows good practices with HTTPS, cookie consent, and domain locking. However, it could improve by enabling DNSSEC, publishing security policies, and adding security headers like CSP and X-Frame-Options. No critical vulnerabilities or exposed sensitive data were detected. The WHOIS data shows privacy protection via Domains By Proxy, which is justified for this business type and consistent with the domain age and business profile. Overall, OneStore presents a trustworthy and professional e-commerce marketing platform with a solid technical foundation and good security posture. Strategic improvements in privacy transparency and security headers would enhance compliance and trust further.
Scanned
NIS2 and GDPR posture
- GDPR outside view
- 68/ 100 · Medium
- Checks completed
- 7of 7
NIS2 Art. 21(2)
- (a) Risk analysis and security policies: Not visible from outside
- (b) Incident handling: One indicator
- (c) Business continuity, backups and crisis management: Not visible from outside
- (d) Supply chain security: Not visible from outside
- (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
- (f) Assessing the effectiveness of security measures: Not visible from outside
- (g) Cyber hygiene and security training: Not visible from outside
- (h) Cryptography and encryption: Partly checked
- (i) HR security, access control and asset management: One indicator
- (j) Multi-factor authentication and secured communications: Not visible from outside
This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.
GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.
Priority findings
4 findings rated critical or high. Fix these first.
Security headers
Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.
- High
Missing X-Frame-Options header
Prevents clickjacking attacks
What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"
- CWE-1021
- OWASP A06:2025
- CAPEC-103
- ASVS V3.4.6
- OWASP Secure Headers: OWASP Secure Headers Project recommends X-Frame-Options: deny
- RFC 7034
- High
Missing Content-Security-Policy header
Controls resources the browser is allowed to load
What to do: Implement a Content-Security-Policy appropriate for your application
- ASVS V3.4.3
- OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…
- High
GDPR outside view
These are the privacy signals visitors and data protection authorities look for under GDPR.
- High
No Cookie Consent Banner found
GDPR requires explicit consent for non-essential cookies
What to do: Implement a cookie consent banner that appears on first visit
- GDPR Art. 7
- ePrivacy Art. 5(3)
- NIST PT-4: NIST SP 800-53 Rev. 5 PT-4: Consent
- High
SSL/TLS
TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.
- High
Weak SSL Key Length
SSL certificate uses 256-bit key, which is considered weak
What to do: Use at least 2048-bit RSA or 256-bit ECC key
- CWE-326
- OWASP A04:2025
- Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048
- NIS2 21(2)(h)
- IR 2024/2690 9.2(b): Implementing Regulation (EU) 2024/2690, Annex point 9.2(b): Cryptography
- NIST SC-13: NIST SP 800-53 Rev. 5 SC-13: Cryptographic Protection
- High
Need hands-on remediation? Email guard@offseq.com
Keep watching one.store
This scan found 21 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.
Daily monitoring
Recommended€25per month
- TLS certificates and expiry
- DNS records
- SPF, DKIM and DMARC
- Security headers
- GDPR and NIS2 posture
- Exposed services
- Third-party trackers
- Security score drift
Email alerts on material changes and an exportable JSON history of every change.
Billed monthly to your card. Cancel anytime. See sample alerts.
Full report
€39.90one-time
- The complete analysis as a PDF you can cite
- Email delivery with an unlock code
- Lifetime access to this report
Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.
Results by check
Each check with its score, findings and the evidence it collected.
How this score is calculated
The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.
Counted in this score
- SSL/TLS
- 75
- Security headers
- 30
- Email security
- 75
- DNS health
- 80
- Network security
- 100
- GDPR outside view
- 68
- Average
- 71
Not counted
- NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
- OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.
Findings that cap the score at 49
Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.
- The certificate is not trusted by browsers
- The website is not served over HTTPS
- A database, remote desktop, file-sharing or Telnet service is reachable from the internet
- The page loads a script from a compromised source
- The domain registration has expired
- SPF authorises every server to send mail as the domain
Partial scans
When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.
Risk levels
- Critical0–25
- High26–49
- Medium50–75
- Low76–100
Technical appendix
Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.
Business context
Business profile
Security posture
Recommendations
- Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
- Publish a comprehensive privacy policy and terms of service accessible from the main website.
- Add a security.txt file and provide clear incident response contact information.
- Implement additional HTTP security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
- Regularly audit and update third-party scripts to mitigate supply chain vulnerabilities.
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- Company
- Domains By Proxy, LLC (registrant proxy), business brand: OneStore
- Description
- OneStore is an AI-powered customer engagement and customer data platform that helps recover abandoned carts, drive sales, average order value, loyalty, and subscriber growth. It integrates with Shopify, TikTok Shop, eBay, Etsy, Amazon, and more, offering all-in-one AI marketing including a Shopify Sidekick AI assistant.
- Key services
- Social proof notifications, One-click checkout upsell, Gamification (Fortune Wheel), Email automation, SMS marketing, A/B testing, Integrations with major e-commerce platforms
- Content quality
- good
- Branding
- consistent
Technology
- Stack
- JavaScript, jQuery, Google Analytics, Google Tag Manager, LeadDyno, ProfitWell, Iubenda Cookie Solution, Crisp Chat, Flywheel analytics, Swiper.js, ConveyThis translation
- Platforms
- Shopify, WooCommerce, BigCommerce, Magento, Wix
- Performance
- fast
- Mobile
- good
- Accessibility
- basic
- SEO
- good
Security
- Observed score
- 85/100
- Good practices seen
- HTTPS enforced
- Domain locked with multiple EPP prohibitions
- Cookie consent mechanism implemented
- No exposed sensitive data in HTML
Analytics and tracking
- Services
- Google Analytics, Google Ads, ProfitWell, Flywheel, LeadDyno
- Tracking level
- extensive
- Privacy practices
- basic
Advertising
- Tracking pixels
- Google Ads, LeadDyno, ProfitWell, Flywheel
- Marketing tools
- OneStore AI Marketing Platform, Iubenda Cookie Consent, Crisp Chat, ConveyThis Translation
- Transparency
- good
Site quality
- Design
- good
- User experience
- good
- Content relevance
- good
- Navigation
- good
- Professionalism
- good
- Trustworthiness
- high
Key observations
- Website is a professional SaaS platform for e-commerce marketing automation.
- Content is rich with customer testimonials and case studies.
- Multiple integrations with major e-commerce platforms are highlighted.
- Privacy and terms pages are not directly found or linked in the provided content.
- Cookie consent is implemented via Iubenda.
- No direct contact emails or phone numbers are visible on the main page.
- Use of multiple third-party marketing and analytics tools is extensive.
- Domain uses Cloudflare DNS but no WAF blocking detected.
- No security.txt or vulnerability disclosure policy found.
Technical notes
Notes
Standards and sources
Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.
- MITRE CWE (opens in a new tab)4.20 (2026-04-30) · CWE Terms of Use (free use with attribution, © MITRE)
- OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
- MITRE CAPEC (opens in a new tab)3.9 (2023-01-24) · CAPEC Terms of Use (free use with attribution, © MITRE)
- OWASP ASVS (opens in a new tab)5.0.0 · CC BY-SA 4.0
- OWASP Web Security Testing Guide (opens in a new tab)latest (checklist.json, master) · CC BY-SA 4.0
- OWASP Secure Headers Project (opens in a new tab)2026-10-18 · Apache-2.0
- Mozilla Server Side TLS (intermediate) (opens in a new tab)6.0 · MPL-2.0
- NIST SP 800-53 Rev. 5 (OSCAL catalog) (opens in a new tab)5.2.0 · Public domain (US Government work)
- Directive (EU) 2022/2555 (NIS2) (opens in a new tab)OJ L 333, 27.12.2022 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Commission Implementing Regulation (EU) 2024/2690 (opens in a new tab)OJ L, 18.10.2024 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Regulation (EU) 2016/679 (GDPR) (opens in a new tab)OJ L 119, 4.5.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive 2002/58/EC (ePrivacy), consolidated (opens in a new tab)19.12.2009 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- RFC Editor metadata (opens in a new tab)per-RFC (obsolete RFCs rejected) · IETF Trust Legal Provisions (metadata only)
- NIST CSRC, W3C TR, IETF Datatracker, EDPB, EUR-Lex CELLAR and gesetze-bayern.de (opens in a new tab)per document · Titles and links only
- NIST NVD CVE API 2.0 (opens in a new tab)live records · Public domain (NVD); CVE® records © MITRE, free use
- W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
- ETSI EN 301 549 (opens in a new tab)V3.2.1 (2021-03), clause headings · Clause numbers and titles only (© ETSI)
- Directive (EU) 2019/882 (European Accessibility Act) (opens in a new tab)OJ L 151, 7.6.2019 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive (EU) 2016/2102 (Web Accessibility Directive) (opens in a new tab)OJ L 327, 2.12.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Retrieved 2026-10-25
Earlier scans of this domain
- 71/100Medium30 findingsView report
Feedback on this report
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with one.store. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review one.store.