Skip to main content

Security report for toms.com

TOMS · Retail · United States

Medium risk. 5 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

68/100

Risk levelMedium

0–100, higher is better. How it is calculated

TOMS is a well-established footwear and accessories brand operating a professional e-commerce website targeting men, women, and children. The site offers a broad product catalog with a focus on stylish, comfortable shoes and accessories, supported by a social impact mission. The technical infrastructure leverages modern e-commerce platforms such as Shopify and Builder.io, ensuring good performance, mobile optimization, and SEO readiness. Security posture is strong with HTTPS enforcement and security headers, though explicit security policies and incident response information are absent. Privacy compliance is well addressed with clear privacy and cookie policies and consent mechanisms. The absence of WHOIS data limits domain legitimacy verification, but the website's professional presentation and trust signals support its credibility. Overall, the site is a reliable and user-friendly platform for TOMS customers.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (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

5 findings rated critical or high. Fix these first.

  1. 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"

    • 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';…

  2. 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

  3. 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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1
    • 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

Need hands-on remediation? Email guard@offseq.com

Keep watching toms.com

This scan found 23 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. The full timeline opens with your unlock code.

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
57
Security headers
50
Email security
55
DNS health
80
Network security
100
GDPR outside view
68
Average
68

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention toms.com, from OffSeq Breach.

Total records
3,613
Employees
4
Customers
3,536
Third parties
73
Weak passwords
12%

Latest record dated 2025-11-14 · 9 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for toms.com.

Select it in the checkout above.

Masked preview

  • –www.toms.com2025-11-14
  • –toms.com2025-07-19
  • –www.toms.com2025-07-09
  • –www.toms.com2025-04-15

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

TOMS operates in the retail and e-commerce sectors with a focus on footwear and accessories. The brand targets a broad demographic including men, women, and kids, emphasizing style and comfort. The business model is direct-to-consumer online sales, supported by impact initiatives that enhance brand value. The website integrates partner domains such as preloved product platforms, indicating a diversified sales approach. The company maintains a consistent brand image and provides comprehensive product collections and seasonal campaigns. Contact information and structured data enhance transparency and customer trust. The lack of WHOIS data suggests privacy protection or domain registration nuances, warranting further inspection for domain ownership verification.

Security posture

The website demonstrates a mature security posture with HTTPS enabled and multiple security headers in place, including HSTS, CSP, and X-Frame-Options. Forms and inputs appear secure with no exposed sensitive data detected. However, there is no publicly available security policy or incident response contact, which could be improved to enhance transparency and readiness. No vulnerable libraries or security flaws were identified in the analyzed content. Privacy compliance is strong with cookie consent and GDPR indicators. Overall, the site is secure but could benefit from explicit security governance documentation and vulnerability disclosure mechanisms.

Recommendations

  1. Publish a dedicated security policy and incident response page to improve transparency and customer trust.
  2. Implement a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  3. Enhance accessibility features to meet higher standards and improve user experience for all users.
  4. Regularly audit third-party scripts and dependencies to mitigate potential vulnerabilities.
  5. Maintain updated WHOIS information or provide domain ownership transparency to strengthen legitimacy.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
TOMS
Description
Shoes: Discover trendy, comfortable shoes for men, women, and kids. Step into style with sneakers, boots, and more — shop now from TOMS!
Key services
Footwear sales, Accessories sales, Impact initiatives
Content quality
good
Branding
consistent

Technology

Stack
Shopify, Builder.io, Typekit Fonts, JavaScript, CSS, Swiper.js
Frameworks
React (implied by JSX-like builder.io scripts), Tailwind CSS
Platforms
Shopify
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Secure cookies with SameSite=None; Secure
  • No exposed sensitive data in HTML
  • Use of CSP headers

Analytics and tracking

Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
builder.io pixel, OneTrust cookie consent
Marketing tools
OneTrust, Builder.io
Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is a professional e-commerce platform for TOMS footwear and accessories.
  2. Content is rich with product categories, collections, and impact information.
  3. Privacy and cookie policies are present with consent mechanisms.
  4. No explicit security policy or incident response information found.
  5. WHOIS data is missing or unavailable, reducing domain trust verification.
  6. No suspicious or malicious indicators detected in content or linked domains.
Technical notes

Notes

The website is built on a modern e-commerce stack primarily using Shopify and Builder.io CMS, with Tailwind CSS for styling and Typekit for fonts. The site is well-optimized for performance and mobile responsiveness, with fast loading times and good SEO practices including meta tags and structured data. Accessibility is basic but functional. The use of multiple external domains for content delivery and tracking is standard for e-commerce but should be monitored for privacy compliance. The technical implementation supports a robust and scalable online retail experience with room for improvement in accessibility and security governance.
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.

Retrieved 2026-10-25

Reviews of this site

Share your experience with toms.com. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review toms.com.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.