Skip to main content

Security report for rwjoinery.co.uk

Other · N/a

Medium risk. 7 critical or high findings in SSL/TLS, Security headers and 1 other check.

Security score

60/100

Risk levelMedium

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

The website www.rwjoinery.co.uk currently serves a security verification page employing Google reCAPTCHA v3 to prevent automated access. This indicates the site is protected by a bot mitigation mechanism or WAF, limiting content accessibility. No substantive business information, contact details, or policies are present on the page, preventing a full assessment of the company's digital presence or operations. The WHOIS lookup failed due to domain naming rules violations, suggesting the domain may be misconfigured or invalid, which raises concerns about legitimacy. Technically, the site uses Bootstrap 5.3.3 and Google reCAPTCHA v3, but lacks visible HTTPS confirmation or security headers in the provided data. The minimal content and blocking mechanisms result in poor user experience, low trustworthiness, and limited SEO or accessibility features. Privacy and cookie policies are absent, indicating non-compliance with common data protection standards. From a security perspective, the use of reCAPTCHA is a positive control against bots, but the absence of other security headers and lack of visible HTTPS configuration are weaknesses. The domain registration issues further reduce trust in the website's legitimacy. Overall, the site’s security posture is weak, and the business credibility is low due to lack of accessible information. Strategically, the site requires urgent remediation to resolve domain registration issues, implement HTTPS, add security headers, and provide clear business and privacy information to improve trust and compliance. Until then, the site remains inaccessible to normal users and vulnerable to trust and security concerns.

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

7 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

  2. 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';…

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

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

Keep watching rwjoinery.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
62
Security headers
15
Email security
70
DNS health
65
Network security
100
GDPR outside view
50
Average
60

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 business information, no meaningful business intelligence can be derived. The domain appears to be related to a joinery business by name, but no details on market positioning, services, or partnerships are available. The absence of contact details and policies suggests the website is either under maintenance, misconfigured, or not actively managed. No revenue streams, customer segments, or growth indicators can be identified from the current data.

Security posture

The website employs Google reCAPTCHA v3 as a bot mitigation measure, which is a positive security control. However, the absence of HTTPS confirmation, security headers, and visible privacy or cookie policies indicates a low maturity level in security and compliance. The domain registration failure and WHOIS data unavailability further undermine trust. There is no evidence of incident response readiness or vulnerability disclosure mechanisms. Overall, the security posture is weak and requires significant improvements to meet standard compliance and security best practices.

Recommendations

  1. Resolve domain registration issues to ensure the domain is valid and properly registered.
  2. Implement HTTPS with a valid SSL/TLS certificate and verify secure configuration.
  3. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Publish clear privacy and cookie policies to comply with GDPR and other regulations.
  5. Provide accessible business contact information including emails, phone numbers, and physical addresses.
  6. Improve website content beyond security verification to enhance user experience and trust.
  7. Implement vulnerability disclosure and incident response contact channels.
  8. Conduct a full security audit to identify and remediate potential vulnerabilities.
  9. Enhance SEO and accessibility features to improve site visibility and usability.
  10. Establish a long-term security strategy including regular updates and monitoring.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Website content is a security verification page with Google reCAPTCHA v3 and minimal content, indicating bot protection or WAF challenge. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
Bootstrap 5.3.3, Google reCAPTCHA v3
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
30/100
Good practices seen
  • Use of Google reCAPTCHA v3 for bot protection

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Google reCAPTCHA
Transparency
poor

Site quality

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

Key observations

  1. Website is currently serving a security verification page with Google reCAPTCHA v3.
  2. No substantive business or contact information is available on the page.
  3. WHOIS data is unavailable due to domain naming rules violation, indicating possible domain registration issues.
  4. No privacy, cookie, or terms of service policies found.
  5. No contact emails, phone numbers, or addresses found.
  6. No social media or external business-related links found.
  7. Technical stack is minimal and focused on bot protection.
  8. Website is likely inaccessible for normal users without passing bot verification.
  9. Security posture is weak due to lack of visible HTTPS and security headers.
  10. Content quality and business credibility are very low due to lack of content.
Technical notes

Notes

The website uses Bootstrap 5.3.3 for styling and Google reCAPTCHA v3 for bot protection. The HTML content is minimal and focused solely on security verification, with no visible CMS or backend technology identified. External resources are loaded from trusted CDNs such as jsdelivr.net and google.com. There is no evidence of performance optimization or advanced technical frameworks. The site lacks visible HTTPS confirmation and security headers in the provided data. Mobile optimization and accessibility are basic due to minimal content. The current technical setup is insufficient for a fully functional business website and requires modernization and enhancement.
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 rwjoinery.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 rwjoinery.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.