Skip to main content

Security report for libbey.com

Libbey · Retail · United States

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

Security score

74/100

Risk levelMedium

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

Libbey is a well-established company specializing in the manufacturing and retail of durable and aesthetically pleasing tableware products for both home and professional foodservice markets. With a history spanning over 200 years, Libbey positions itself as a trusted brand offering quality products designed to last a lifetime. The website reflects a mature digital presence with clear segmentation for home and foodservice customers, supported by regional domains for Latin America and China. Technically, the site leverages modern web technologies including React, Next.js, and Builder.io CMS, ensuring a fast, mobile-optimized, and accessible user experience. Security posture is solid with HTTPS enforced and no visible vulnerabilities, though improvements are recommended in security headers and published policies. Privacy compliance is addressed with a comprehensive privacy policy, but cookie consent mechanisms could be enhanced. Overall, the website demonstrates high professionalism and trustworthiness, though the lack of WHOIS data slightly reduces domain trust. Strategic recommendations include enhancing security transparency and cookie consent to further strengthen compliance and user trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
58/ 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 Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • 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

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

Keep watching libbey.com

This scan found 19 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
62
Security headers
55
Email security
85
DNS health
85
Network security
100
GDPR outside view
58
Average
74

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

Libbey operates in the retail and manufacturing sectors, focusing on tableware products for home consumers and foodservice professionals. The company benefits from a strong brand legacy and a diversified market presence including subsidiaries and regional domains. Its business model combines direct retail, B2B sales, and foodservice solutions, supported by an online shop and dedicated foodservice site. The company targets a broad audience from individual consumers to commercial clients, leveraging its heritage and product durability as competitive advantages. The website's integration with multiple external domains and social media channels indicates a well-established partnership and marketing ecosystem. Growth indicators include active career pages and product recall transparency, signaling operational maturity and regulatory compliance.

Security posture

The website demonstrates a good security baseline with HTTPS enabled and no exposed sensitive data or vulnerable libraries detected. However, the absence of explicit security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options is a gap that could be exploited. No published security policies or incident response contacts were found, which limits transparency and preparedness in case of security incidents. The lack of a vulnerability disclosure program or security.txt file further reduces the security maturity level. Privacy compliance is partially addressed with a privacy policy and cookie policy, but the absence of a cookie consent mechanism is a compliance risk under GDPR and similar regulations. Overall, the security posture is solid but could be improved by adopting best practices in headers, policies, and user consent.

Recommendations

  1. Implement and enforce security headers including CSP, HSTS, and X-Frame-Options to mitigate common web vulnerabilities.
  2. Add a cookie consent banner/mechanism to comply with GDPR and enhance user privacy transparency.
  3. Publish a clear security policy and incident response contact information to improve trust and readiness.
  4. Establish a vulnerability disclosure program or security.txt file to encourage responsible reporting of security issues.
  5. Regularly audit third-party scripts and tracking pixels to minimize privacy risks and improve compliance.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Libbey
Description
Libbey provides durable and beautiful tableware products for home and foodservice markets, with a history dating back over 200 years. They offer products for home entertaining and professional foodservice, emphasizing quality and durability.
Key services
Tableware products for home, Foodservice tabletop solutions, Online retail and B2B sales
Content quality
excellent
Branding
consistent

Technology

Stack
Next.js, React, Google Analytics, Google Tag Manager, Builder.io, Typekit Fonts
Frameworks
React, Next.js
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • No visible vulnerable libraries

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Builder.io pixel
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content and multimedia.
  2. No WAF or blocking mechanisms detected.
  3. WHOIS data is missing or unavailable, which reduces trust score.
  4. Strong branding and consistent messaging about company history and products.
  5. Multiple external domains linked for regional and business segments.
  6. Privacy policy and cookie policy present but no explicit cookie consent mechanism.
  7. No visible security or incident response policies published.
  8. Modern tech stack with React and Next.js and Builder.io CMS.
  9. Good mobile optimization and accessibility features.
  10. No forms collecting sensitive data visible except contact form link.
Technical notes

Notes

The website is built on a modern technology stack featuring React and Next.js frameworks, with Builder.io as the CMS platform. It uses Typekit for fonts and integrates Google Analytics and Google Tag Manager for tracking and marketing purposes. The site is well-optimized for performance and mobile responsiveness, with lazy loading of images and videos. The HTML structure is valid and semantic, supporting accessibility and SEO best practices. Hosting provider details are not explicitly identified, but the use of Next.js and Builder.io suggests a cloud-based hosting environment. No technical debt or legacy technologies were detected, indicating a well-maintained and modern infrastructure. Opportunities exist to enhance security headers and privacy mechanisms to align with industry standards.
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 libbey.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 libbey.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.