Skip to main content

Security report for london.ac.uk

University of London · Education · United Kingdom

Low risk. 1 critical or high finding in Security headers.

Security score

86/100

Risk levelLow

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

The University of London is a prestigious federation of 17 higher education institutions, recognized as the UK's leading provider of digital and blended distance education internationally. The website reflects a mature digital presence with a focus on accessibility and user experience, targeting students worldwide seeking flexible higher education options. The institution's market position is strong within the education sector, leveraging its federation model to offer diverse academic programs. Technically, the website is built on Drupal 10, incorporating modern web technologies such as Google Tag Manager and OneTrust for consent management, indicating a high level of digital maturity. The site is well-optimized for mobile devices and demonstrates good SEO and accessibility practices, contributing to a positive user experience. From a security perspective, the site enforces HTTPS, employs robust security headers, and integrates cookie consent mechanisms compliant with GDPR. No critical vulnerabilities or exposed sensitive data were detected. However, the absence of publicly available WHOIS data and explicit security policies suggests areas for improvement in transparency and incident response readiness. Overall, the University of London's website presents a secure, professional, and user-friendly platform aligned with its educational mission. Strategic enhancements in security policy disclosure and vulnerability management could further strengthen its security posture and stakeholder trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
88/ 100 · Low
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

1 finding 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 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';…

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

Keep watching london.ac.uk

This scan found 13 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
90
Security headers
65
Email security
85
DNS health
85
Network security
100
GDPR outside view
88
Average
86

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 University of London operates as a large educational entity with a federated business model, offering digital and blended learning programs globally. Its competitive advantage lies in its international reach and the prestige of its constituent institutions. Revenue streams likely include tuition fees from distance learners and partnerships with educational providers. The target customer segments are international students seeking flexible higher education. The website's integration with major analytics and consent tools indicates a data-driven approach to user engagement and compliance. The institution maintains a strong partnership ecosystem, evident from its social media presence and federated structure, supporting growth and market penetration.

Security posture

The website demonstrates a mature security posture with enforced HTTPS, comprehensive security headers, and GDPR-compliant cookie consent. The use of OneTrust and Google Tag Manager is well-managed, minimizing privacy risks. No immediate vulnerabilities or security misconfigurations were identified. However, the lack of a published security policy, incident response plan, or vulnerability disclosure program limits transparency and may impact incident handling efficiency. The absence of WHOIS data is likely due to privacy protection, which is justified for this type of institution. Overall, the security maturity is high but could benefit from enhanced policy disclosures and proactive vulnerability management.

Recommendations

  1. Publish a detailed security policy and incident response plan on the website to improve transparency and stakeholder confidence.
  2. Implement and publicize a vulnerability disclosure program or security.txt file to encourage responsible reporting of security issues.
  3. Regularly audit and update third-party scripts and libraries to mitigate potential vulnerabilities.
  4. Enhance data retention policy disclosures to align with GDPR and improve user trust.
  5. Maintain and monitor security headers and SSL configurations to ensure ongoing protection against emerging threats.

Contact details published on the site

Addresses
Legal name
University of London
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
University of London
Description
University of London is the UK’s leading provider of digital and blended distance education internationally and a federation of 17 esteemed higher education institutions.
Key services
Digital distance education, Blended learning, Higher education courses, Federated university services
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 10, Google Tag Manager, OneTrust Consent Management, Typekit Fonts
Frameworks
Drupal
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of CSP
  • Cookie consent mechanism
  • No exposed sensitive data detected

Analytics and tracking

Services
Google Analytics (via Google Tag Manager)
Tracking level
moderate
Privacy practices
good

Advertising

Marketing tools
OneTrust Consent Management
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenge.
  2. Content is rich, professional, and targeted at international students.
  3. Strong privacy and cookie compliance with OneTrust integration.
  4. Use of modern technologies and CMS (Drupal 10).
  5. No suspicious or malicious content detected.
  6. WHOIS data is unavailable, likely due to privacy protection or query restrictions.
Technical notes

Notes

The website is powered by Drupal 10, a modern and secure CMS platform, supported by Google Tag Manager for analytics and OneTrust for consent management. The use of Typekit fonts and preloading techniques indicates attention to performance optimization. Mobile responsiveness and accessibility features are well-implemented, contributing to a high-quality user experience. Hosting details are not explicitly identified but appear stable and performant. The site benefits from strong SEO practices and structured metadata, including Open Graph tags, enhancing social media integration and search visibility. Technical risks are minimal, with opportunities for modernization focused on enhanced security transparency and continuous performance monitoring.
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 london.ac.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 london.ac.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.