Skip to main content

Security report for whitehallgardencentre.co.uk

Other · N/a

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

Security score

63/100

Risk levelMedium

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

The website www.whitehallgardencentre.co.uk is currently inaccessible, presenting only a minimal placeholder message indicating local rate limiting or blocking, likely due to a Web Application Firewall or security mechanism. No meaningful content, metadata, or business information is available for analysis. The WHOIS lookup failed with an error indicating the domain name violates Nominet UK's naming rules, suggesting the domain may not be properly registered or is invalid. This severely limits the ability to assess the business or technical posture of the site. From a technical perspective, the site lacks HTTPS, security headers, and any detectable technologies or frameworks. No privacy, cookie, or terms of service policies are present, and no contact information or social media links are found. The site appears non-functional or placeholder only, with no content to evaluate for SEO, accessibility, or user experience. Security posture is weak due to the absence of HTTPS and security headers, combined with the domain registration issues. The lack of WHOIS data and domain legitimacy raises significant trust concerns. Overall, the site is not currently suitable for business or customer engagement and requires substantial remediation. Strategic recommendations include establishing a valid domain registration, implementing HTTPS and security best practices, publishing privacy and cookie policies, and providing clear business contact information to improve trust and compliance.

Scanned

NIS2 and GDPR posture

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

  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 whitehallgardencentre.co.uk

This scan found 25 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
37
Security headers
75
Email security
75
DNS health
50
Network security
100
GDPR outside view
40
Average
63

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 WHOIS data, no reliable business intelligence can be derived. The domain appears invalid or improperly registered, and no business details, market positioning, or operational insights are available. The absence of contact information and social media presence further limits understanding of the company's market presence or partnerships.

Security posture

The security posture is currently poor. The site lacks HTTPS, security headers, and any visible security policies or incident response contacts. The domain registration is invalid or missing, which is a critical trust and security concern. No vulnerability disclosures or data protection officer information is available. The site is likely protected by a generic WAF or rate limiting mechanism, but this does not compensate for the lack of fundamental security controls.

Recommendations

  1. Register a valid domain name compliant with Nominet UK naming rules to establish legitimacy.
  2. Implement HTTPS with a valid SSL/TLS certificate to secure communications.
  3. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Publish comprehensive privacy and cookie policies to comply with GDPR and build user trust.
  5. Provide clear business contact information including emails, phone numbers, and physical address.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Website content is blocked or rate limited, showing minimal placeholder text 'local_rate_limited' indicating access restrictions or WAF protection. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Performance
slow
Mobile
poor
Accessibility
poor
SEO
poor

Security

Observed score
10/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website content is inaccessible or blocked due to rate limiting or WAF protection
  2. No meaningful HTML content or metadata available for analysis
  3. No contact or business information found on the site
  4. WHOIS data is unavailable and indicates domain registration issues
  5. No security headers or HTTPS detected
  6. No privacy, cookie, or terms of service policies found
  7. No external links, forms, or scripts detected
  8. Website appears non-functional or placeholder only
Technical notes

Notes

The website currently serves only a minimal placeholder message indicating local rate limiting, with no detectable HTML metadata, scripts, or technologies. No CMS or frameworks are identifiable. The absence of HTTPS and security headers indicates a basic or incomplete technical setup. The site likely suffers from performance and accessibility issues due to lack of content and optimization. Hosting provider and platform details are not discernible from the available data.
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 whitehallgardencentre.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 whitehallgardencentre.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.