Skip to main content

Security report for timpson.co.uk

Other

Medium risk. 6 critical or high findings in SSL/TLS and GDPR outside view.

Security score

68/100

Risk levelMedium

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

The website www.timpson.co.uk is currently inaccessible due to an SSL handshake failure between Cloudflare and the origin server, resulting in a Cloudflare error 525 page. This prevents access to any meaningful website content, metadata, or business information. The domain WHOIS lookup failed with an error indicating the domain name contains too many parts, which is unusual and prevents extraction of registrar, creation, expiry, or registrant details. Technically, the site uses Cloudflare as a CDN and WAF, but the origin server's SSL configuration is misconfigured or incompatible, causing the failure. Security posture is weak due to lack of SSL connectivity and absence of security headers or policies. Overall, the site is currently non-functional and lacks publicly accessible information, severely limiting trust and business credibility assessments.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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

6 findings rated critical or high. Fix these first.

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

  2. GDPR outside view

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

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

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

Keep watching timpson.co.uk

This scan found 20 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
42
Security headers
75
Email security
70
DNS health
85
Network security
100
GDPR outside view
35
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

Technical appendix

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

Business context

Business profile

Due to the lack of accessible content and metadata, no business intelligence insights can be reliably derived. The domain WHOIS failure and SSL issues suggest possible misconfiguration or domain registration irregularities. No contact information, privacy policies, or business descriptions are available to analyze market positioning, target audience, or business model. The presence of Cloudflare indicates some level of infrastructure investment, but the critical SSL failure undermines operational reliability and customer trust.

Security posture

The security posture is currently poor. The SSL handshake failure indicates the origin server's SSL certificate or configuration is incompatible with Cloudflare, preventing secure HTTPS connections. No security headers or policies are present on the error page. The absence of privacy and cookie policies further indicates compliance gaps. Incident response and vulnerability disclosure mechanisms are not detectable. The WHOIS lookup failure adds to concerns about domain legitimacy and transparency. Immediate remediation of SSL configuration and WHOIS registration issues is recommended to restore secure access and trust.

Recommendations

  1. Correct the SSL certificate and configuration on the origin server to ensure compatibility with Cloudflare and enable HTTPS connections.
  2. Investigate and resolve the domain WHOIS registration issue causing the naming rules violation error.
  3. Implement standard security headers (e.g., HSTS, Content-Security-Policy) to improve security posture once the site is accessible.
  4. Publish privacy, cookie, and terms of service policies to enhance compliance and user trust.
  5. Establish clear contact and incident response information on the website to support security and customer service.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. Detected Cloudflare error 525 SSL handshake failure page indicating origin server SSL issues and blocked content. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor

Technology

Stack
Cloudflare

Security

Observed score
10/100

Analytics and tracking

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website is currently inaccessible due to SSL handshake failure (Cloudflare error 525).
  2. No actual website content is available for analysis.
  3. No metadata, structured data, forms, or contact information found.
  4. No privacy, cookie, or terms of service policies detected.
  5. No security policies or incident response information available.
  6. No business or company information extractable from the page.
  7. Cloudflare is used as a CDN/WAF but origin server SSL is misconfigured.
  8. WHOIS lookup failed with an error indicating domain naming rules violation.
  9. Analysis incomplete due to WAF/security mechanisms. For accurate analysis, please contact guard@offseq.com.
Technical notes

Notes

The website is served behind Cloudflare, which acts as a CDN and WAF. However, the origin server SSL configuration is broken, causing Cloudflare error 525 (SSL handshake failure). No CMS or frameworks are detectable due to lack of content. The HTML is minimal and only serves an error page. No analytics, tracking, or marketing technologies are present. Performance and accessibility cannot be assessed due to inaccessible content. The domain WHOIS lookup failed, indicating potential domain registration or configuration issues. Overall, the technical infrastructure requires urgent remediation to restore normal website operations.
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 timpson.co.uk. 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 timpson.co.uk.

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.