Skip to main content

Security report for luerzersarchive.com

Lürzer's Archive · Media · United Kingdom

High risk. 9 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

42/100

Risk levelHigh

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

Lürzer's Archive is a well-established media company specializing in providing a comprehensive archive and magazine platform for advertising professionals worldwide. With over 30 years of curated creative content, it serves as a leading resource for creatives, agencies, and industry stakeholders. The website offers subscription services, a searchable archive of print campaigns, TV commercials, and digital designs, as well as a profiles platform connecting creatives and agencies. Technically, the site is built on WordPress with WooCommerce and leverages Cloudflare CDN for performance and security. However, the absence of a valid SSL certificate and HTTPS significantly undermines its security posture. While the site includes privacy and terms policies, cookie consent mechanisms and explicit security policies are lacking, indicating room for compliance improvements. Overall, the site is professionally designed with rich content but requires urgent security enhancements to protect user data and maintain trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
0/ 100 · Critical
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

9 findings rated critical or high. Fix these first.

  1. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

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

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. 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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • 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';…

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

Keep watching luerzersarchive.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. 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
0
Security headers
15
Email security
50
DNS health
85
Network security
100
GDPR outside view
0
Average
42

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

The company holds a strong market position as a niche media provider in the advertising industry, targeting professionals seeking inspiration and industry insights. Its business model combines subscription revenue, magazine and book sales, and a platform for creative submissions and profiles. The presence of multiple international contact points and social media channels supports a global reach. The company benefits from a consistent brand identity and trust signals such as Google site verification and structured data. However, the lack of advanced privacy compliance and security policies may impact user confidence and regulatory adherence. The company appears to operate independently without visible parent or subsidiary relationships.

Security posture

The website's security posture is weak due to the lack of HTTPS and valid SSL/TLS certificates, exposing users to potential data interception risks. No modern TLS protocols or security headers like HSTS are enabled, and there is no OCSP stapling or session resumption configured. While Cloudflare CDN is used, no WAF challenge or blocking is detected, indicating basic protection but insufficient for comprehensive security. The absence of explicit incident response or vulnerability disclosure policies further limits the site's security maturity. These gaps pose risks to user data protection and compliance with regulations such as GDPR.

Recommendations

  1. Implement and maintain a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and configure security headers including HSTS with preload and includeSubDomains.
  3. Introduce a cookie consent mechanism to comply with privacy regulations and enhance user trust.
  4. Develop and publish clear security policies including incident response and vulnerability disclosure procedures.
  5. Regularly audit and update third-party libraries and plugins to mitigate vulnerabilities and improve overall security posture.
Technical notes

Notes

The website is powered by WordPress 6.7.1 with WooCommerce for e-commerce functionality. It uses jQuery and several custom JavaScript components for UI features. Hosting is provided via Cloudways with Cloudflare CDN for caching and performance. SEO is enhanced with Rank Math PRO plugin and structured data is implemented using JSON-LD for organization, website, and social profiles. Performance metrics are not provided but the site uses lazy loading for images and responsive design techniques. Accessibility is basic with some semantic HTML usage. The site lacks HTTPS which is a critical technical deficiency. Overall, the technical infrastructure is modern but requires security upgrades and performance monitoring.
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 luerzersarchive.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 luerzersarchive.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.