Skip to main content

Security report for keesafety.co.uk

Other

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

Security score

57/100

Risk levelMedium

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

The website www.keesafety.co.uk is currently inaccessible, returning an HTTP 403 Forbidden error page with minimal HTML content. This prevents any meaningful extraction of business, technical, or security information from the site itself. The WHOIS lookup for the domain also failed, indicating the domain name is invalid under Nominet UK rules, which raises concerns about the domain's registration status or query method. Due to these access and data limitations, the overall digital maturity and security posture of the entity behind this domain cannot be reliably assessed. From a business perspective, no information about the company, its services, or market positioning could be identified. Technically, no metadata, scripts, or technologies were detectable, and no security headers or SSL configuration details were available. The lack of privacy, cookie, or terms of service policies further limits compliance assessment. The content safety rating is safe by default due to the absence of content. Security posture evaluation is severely impacted by the lack of accessible content and WHOIS data. The domain's legitimacy is questionable given the WHOIS error and lack of registrant information. The site is likely protected or blocked by a security mechanism or misconfigured server permissions, resulting in the 403 error. Overall, the risk assessment is high due to the inability to verify the domain's legitimacy, absence of accessible content, and lack of security and compliance indicators. Strategic recommendations include resolving access issues, verifying domain registration status, implementing standard security headers and HTTPS, and publishing clear business and compliance information to improve trust and security posture.

Scanned

NIS2 and GDPR posture

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

8 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 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';…

  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

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

Keep watching keesafety.co.uk

This scan found 26 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
37
Security headers
15
Email security
70
DNS health
70
Network security
100
GDPR outside view
50
Average
57

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

No business intelligence could be extracted due to inaccessible website content and missing WHOIS data. The domain WHOIS query failure suggests potential issues with domain registration or query parameters. Without access to the website or registrant details, no insights into market positioning, competitive advantages, or business model are available. No partnership or subsidiary domains were identified.

Security posture

The current security posture cannot be fully assessed due to the website being inaccessible and no WHOIS data available. The HTTP 403 Forbidden response indicates server-side access restrictions or security controls blocking access. No security headers or SSL information were detected. The absence of privacy and cookie policies suggests compliance gaps. Incident response and vulnerability disclosure information are not present. The domain's legitimacy is questionable given the WHOIS lookup failure, which may indicate registration or configuration issues.

Recommendations

  1. Resolve the HTTP 403 Forbidden error to allow access to website content for proper analysis and user access.
  2. Verify and correct the domain registration status with Nominet UK to ensure the domain is valid and properly registered.
  3. Implement HTTPS with valid SSL certificates and configure security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Publish comprehensive privacy, cookie, and terms of service policies to enhance compliance and user trust.
  5. Provide clear contact information and business details on the website to improve credibility and support incident response.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. HTTP 403 Forbidden error page indicating access is blocked or rejected by server security or permissions. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Analytics and tracking

Site quality

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

Key observations

  1. Website content is inaccessible due to HTTP 403 Forbidden error.
  2. No metadata, structured data, or scripts detected due to minimal HTML content.
  3. No contact information, policies, or business details found on the page.
  4. WHOIS data unavailable due to domain query error; no registrar or registration dates extracted.
  5. No external links or social media links present in the HTML.
  6. No forms or input fields detected.
  7. No security headers or SSL configuration information available.
  8. Content safety rating is safe given no content is present.
  9. WAF or security blocking is likely causing access denial.
Technical notes

Notes

Due to the HTTP 403 Forbidden error and minimal HTML content, no technical stack, frameworks, CMS, or hosting provider information could be identified. No metadata, scripts, or analytics tools were detected. The website's performance, mobile optimization, accessibility, and SEO optimization cannot be evaluated. The domain WHOIS query failed, preventing analysis of domain age or registrar details. Overall, the technical infrastructure appears inaccessible or misconfigured.
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 keesafety.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 keesafety.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.