Skip to main content

Security report for bighams.com

Charlie Bigham's · Retail · United Kingdom

Low risk. 3 critical or high findings in GDPR outside view and SSL/TLS.

Security score

79/100

Risk levelLow

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

Charlie Bigham's is a UK-based premium prepared meals brand offering lovingly made dishes freshly prepared in their kitchen and sold directly to consumers and retail. The website reflects a well-established business with a clear brand identity, targeting consumers seeking quality ready meals and related products such as cookbooks and a brasserie dining experience. The technical infrastructure leverages modern web technologies including Webflow CMS, Google Tag Manager, and multiple marketing pixels, indicating a mature digital presence. Security posture is strong with HTTPS enforced, security headers present, and use of reCAPTCHA, though explicit security policies and incident response contacts are absent. Privacy compliance is well addressed with comprehensive cookie and privacy policies and consent mechanisms. However, the absence of WHOIS data for the domain raises concerns about domain registration legitimacy, which impacts overall business credibility. Strategic recommendations include verifying domain registration, enhancing contact transparency, and adding security policy disclosures.

Scanned

NIS2 and GDPR posture

GDPR outside view
73/ 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

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

    • 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

  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.

    • 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 bighams.com

This scan found 16 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
54
Security headers
60
Email security
98
DNS health
90
Network security
100
GDPR outside view
73
Average
79

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 positions itself as a premium player in the prepared meals retail sector in the UK, founded in 1994. Its business model focuses on direct-to-consumer sales, retail partnerships, and brand extensions such as cookbooks and brasserie offerings. The website's content and design support a strong brand narrative and customer engagement. The use of multiple tracking and marketing tools suggests active digital marketing efforts. Lack of direct contact details and WHOIS data may affect customer trust and regulatory compliance. No evident partnerships or subsidiaries were identified from the website content.

Security posture

The website demonstrates good security hygiene with HTTPS, security headers, and anti-bot measures like Google reCAPTCHA. Cookie consent is granular and GDPR compliant. However, the absence of a dedicated security policy, incident response information, and vulnerability disclosure mechanisms limits transparency and preparedness perception. No vulnerabilities or exposed sensitive data were detected in the content. The domain registration opacity is a notable risk factor. Overall, the security posture is solid but could be improved with enhanced transparency and formal security documentation.

Recommendations

  1. Verify and update domain WHOIS registration to ensure transparency and legitimacy.
  2. Publish a dedicated security policy and incident response contact information on the website.
  3. Implement a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  4. Enhance accessibility features to improve compliance and user experience.
  5. Provide direct company contact emails and phone numbers to improve trust and customer support.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Charlie Bigham's
Description
Lovingly made dishes, freshly prepared in the Charlie Bigham's kitchen.
Key services
Prepared meals, Cookbook sales, Brasserie dining experience
Content quality
good
Branding
consistent

Technology

Stack
Webflow, Google Tag Manager, Google reCAPTCHA, TikTok Pixel, Pinterest CT, Iubenda Cookie Solution, Jetboost, Elf Sight
Platforms
Webflow CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of reCAPTCHA for forms
  • Cookie consent with granular controls

Analytics and tracking

Services
Google Analytics, TikTok Analytics, Facebook Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
TikTok Pixel, Facebook Pixel, Pinterest CT, Spotify Pixel
Marketing tools
Elf Sight
Transparency
good

Site quality

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

Key observations

  1. Website is professionally designed with clear branding and navigation.
  2. No WHOIS data available, indicating possible domain registration issues.
  3. Privacy and cookie policies are present and GDPR compliant.
  4. No direct contact emails or phone numbers found; contact via form only.
  5. Multiple third-party tracking and marketing scripts used.
  6. No explicit security policy or incident response information found.
  7. No vulnerability disclosure or security.txt present.
  8. Content is safe and appropriate for general audiences.
  9. No WAF or blocking detected; full content accessible.
Technical notes

Notes

The website is built on Webflow CMS, utilizing modern front-end technologies and third-party integrations for analytics, marketing, and user engagement. Performance is moderate with good mobile optimization and SEO practices. The use of multiple external scripts and pixels requires ongoing security review to mitigate supply chain risks. Hosting is via Webflow's CDN, providing reliable uptime and SSL termination. Technical debt appears low, but opportunities exist to improve accessibility and formalize security documentation. Overall, the technical infrastructure supports the business needs effectively.
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 bighams.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 bighams.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.