Security report for redcross.org.uk
British Red Cross Society · Non-profit · United Kingdom
Medium risk. 3 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.
The British Red Cross is a well-established humanitarian charity operating primarily in the UK and internationally. The organization provides emergency response, health and social care services, refugee support, first aid training, and retail operations through charity shops. It holds a strong market position as part of the global Red Cross network and is incorporated by Royal Charter with multiple charity registrations across UK jurisdictions. The website reflects a professional and consistent brand image with comprehensive content targeting donors, volunteers, and people in crisis. Technically, the website employs modern web technologies including Google Tag Manager, YouTube iframe API, OneTrust for cookie consent, and Salesforce Marketing Cloud for personalization. It is hosted behind an Incapsula WAF, ensuring protection against common web threats. The site is mobile-optimized, accessible, and SEO-friendly, though no explicit CMS or framework is identified. Performance is moderate with good technical implementation. Security posture is strong with HTTPS enforced, no exposed sensitive data, and use of consent management for cookies. However, explicit security headers like CSP and X-Frame-Options are not evident, and no public security policy or incident response information is provided. No vulnerability disclosure or security.txt file is found, indicating room for improvement in transparency and security communication. Overall, the website is trustworthy, professionally maintained, and compliant with GDPR and privacy standards. The domain WHOIS data aligns well with the organization's identity, confirming legitimacy. Strategic recommendations include enhancing security header implementation, publishing security policies, and establishing a vulnerability disclosure program to further strengthen security posture and trust.
Scanned
NIS2 and GDPR posture
- GDPR outside view
- 63/ 100 · Medium
- Checks completed
- 7of 7
NIS2 Art. 21(2)
- (a) Risk analysis and security policies: Not visible from outside
- (b) Incident handling: One indicator
- (c) Business continuity, backups and crisis management: Not visible from outside
- (d) Supply chain security: Not visible from outside
- (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
- (f) Assessing the effectiveness of security measures: Not visible from outside
- (g) Cyber hygiene and security training: Not visible from outside
- (h) Cryptography and encryption: Partly checked
- (i) HR security, access control and asset management: One indicator
- (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.
GDPR outside view
These are the privacy signals visitors and data protection authorities look for under GDPR.
- Critical
No HTTPS encryption
GDPR requires appropriate security measures for personal data
What to do: Implement SSL/TLS certificate for HTTPS
- CWE-319
- OWASP A04:2025
- ASVS V12.2.1
- NIS2 21(2)(h)
- IR 2024/2690 9.2(a): Implementing Regulation (EU) 2024/2690, Annex point 9.2(a): Cryptography
- GDPR Art. 32(1)(a)
- NIST SC-8: NIST SP 800-53 Rev. 5 SC-8: Transmission Confidentiality and Integrity
- Critical
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.
- Critical
No HTTPS Encryption
Website does not use HTTPS encryption, making all data transmission vulnerable to interception
What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS
- CWE-319
- OWASP A04:2025
- ASVS V12.2.1
- NIS2 21(2)(h)
- IR 2024/2690 9.2(a): Implementing Regulation (EU) 2024/2690, Annex point 9.2(a): Cryptography
- GDPR Art. 32(1)(a)
- NIST SC-8: NIST SP 800-53 Rev. 5 SC-8: Transmission Confidentiality and Integrity
- Critical
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 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';…
- High
Need hands-on remediation? Email guard@offseq.com
Keep watching redcross.org.uk
This scan found 14 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
- 0
- Security headers
- 60
- Email security
- 93
- DNS health
- 70
- Network security
- 100
- GDPR outside view
- 63
- Average
- 64
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
Security posture
Recommendations
- Implement and enforce comprehensive security headers including CSP, X-Frame-Options, and X-Content-Type-Options.
- Publish a clear security policy and incident response information accessible from the website footer or dedicated page.
- Establish and publicize a vulnerability disclosure program or security.txt file to encourage responsible reporting.
- Provide direct security contact channels such as security@ or abuse@ email addresses.
- Regularly audit and update third-party scripts and marketing tools to mitigate supply chain risks.
Contact details published on the site
- Legal name
- The British Red Cross Society
- Registration number
- 220949 (England and Wales), SC037738 (Scotland), 0752 (Isle of Man), 430 (Jersey)
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- Company
- British Red Cross Society
- Description
- The British Red Cross helps people in crisis, whoever and wherever they are. We are part of a global voluntary network, responding to conflicts, natural disasters and individual emergencies.
- Key services
- Emergency response, Health and social care services in the UK, Support for refugees and asylum seekers, First aid training and courses, Charity shops and retail, Fundraising and donations
- Content quality
- excellent
- Branding
- consistent
Technology
- Stack
- YouTube iframe API, Google Tag Manager, OneTrust Cookie Consent, Salesforce Marketing Cloud Personalisation, WebTrends Optimize, Grunticon for SVG icons, Modernizr (conditional for IE), CSS3, JavaScript
- Performance
- moderate
- Mobile
- good
- Accessibility
- good
- SEO
- good
Security
- Observed score
- 85/100
- Good practices seen
- HTTPS enforced
- Cookie consent with OneTrust
- No exposed emails or phone numbers in HTML
- No visible vulnerable libraries
- Use of iframe with YouTube no-cookie domain
Analytics and tracking
- Services
- Google Tag Manager, WebTrends Optimize
- Tracking level
- moderate
- Privacy practices
- good
Advertising
- Tracking pixels
- WebTrends Optimize, Salesforce Marketing Cloud Personalisation
- Marketing tools
- WebTrends Optimize, Salesforce Marketing Cloud Personalisation
- Transparency
- good
Site quality
- Design
- excellent
- User experience
- excellent
- Content relevance
- excellent
- Navigation
- excellent
- Professionalism
- excellent
- Trustworthiness
- high
Key observations
- Website is fully accessible with rich content and navigation.
- Strong presence of privacy and cookie policies with consent mechanisms.
- No direct contact emails or phone numbers exposed in HTML; contact via contact page.
- Use of multiple third-party marketing and analytics tools with consent.
- Good branding consistency and professional design.
- No visible security policy or incident response information.
- No vulnerability disclosure or security.txt found.
- Incapsula WAF in place but no blocking detected.
Technical notes
Notes
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.
- MITRE CWE (opens in a new tab)4.20 (2026-04-30) · CWE Terms of Use (free use with attribution, © MITRE)
- OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
- MITRE CAPEC (opens in a new tab)3.9 (2023-01-24) · CAPEC Terms of Use (free use with attribution, © MITRE)
- OWASP ASVS (opens in a new tab)5.0.0 · CC BY-SA 4.0
- OWASP Web Security Testing Guide (opens in a new tab)latest (checklist.json, master) · CC BY-SA 4.0
- OWASP Secure Headers Project (opens in a new tab)2026-10-18 · Apache-2.0
- Mozilla Server Side TLS (intermediate) (opens in a new tab)6.0 · MPL-2.0
- NIST SP 800-53 Rev. 5 (OSCAL catalog) (opens in a new tab)5.2.0 · Public domain (US Government work)
- Directive (EU) 2022/2555 (NIS2) (opens in a new tab)OJ L 333, 27.12.2022 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Commission Implementing Regulation (EU) 2024/2690 (opens in a new tab)OJ L, 18.10.2024 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Regulation (EU) 2016/679 (GDPR) (opens in a new tab)OJ L 119, 4.5.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive 2002/58/EC (ePrivacy), consolidated (opens in a new tab)19.12.2009 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- RFC Editor metadata (opens in a new tab)per-RFC (obsolete RFCs rejected) · IETF Trust Legal Provisions (metadata only)
- NIST CSRC, W3C TR, IETF Datatracker, EDPB, EUR-Lex CELLAR and gesetze-bayern.de (opens in a new tab)per document · Titles and links only
- NIST NVD CVE API 2.0 (opens in a new tab)live records · Public domain (NVD); CVE® records © MITRE, free use
- W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
- ETSI EN 301 549 (opens in a new tab)V3.2.1 (2021-03), clause headings · Clause numbers and titles only (© ETSI)
- Directive (EU) 2019/882 (European Accessibility Act) (opens in a new tab)OJ L 151, 7.6.2019 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive (EU) 2016/2102 (Web Accessibility Directive) (opens in a new tab)OJ L 327, 2.12.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Retrieved 2026-10-25
Earlier scans of this domain
- 82/100Low23 findingsView report
Feedback on this report
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with redcross.org.uk. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review redcross.org.uk.