Skip to main content

Security report for arme-project.co.uk

Augmented Reality Music Ensemble · Education · United Kingdom

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

Security score

66/100

Risk levelMedium

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

The Augmented Reality Music Ensemble (ARME) project is an academic research initiative funded by EPSRC and hosted in the UK, focused on understanding musician synchronization and developing computational models to simulate virtual musicians for training purposes. The website serves as a platform to share research outcomes, publications, demos, and news related to the project. The target audience includes musicians, researchers, and the academic community interested in augmented reality and music technology. The project operates primarily as a research entity with public funding and academic partnerships. Technically, the website is built using modern web technologies including the Wowchemy Hugo static site generator, Bootstrap framework, and various JavaScript libraries such as MathJax, Leaflet, and jQuery. Hosting appears to be via Netlify, indicated by the presence of Netlify Identity widgets. The site is mobile optimized with good SEO practices and structured data for enhanced search engine visibility. From a security perspective, the site enforces HTTPS and uses no vulnerable libraries. However, it lacks several security headers and does not publish security policies or incident response information. Privacy compliance is partial, with a privacy policy present but no cookie consent mechanism or GDPR explicit indicators. No contact emails or phone numbers are provided, limiting direct communication channels. Overall, the security posture is moderate with room for improvement in policy transparency and user privacy controls. The overall risk assessment is low given the academic nature and lack of sensitive data collection. Strategic recommendations include implementing security headers, adding cookie consent for GDPR compliance, publishing security and incident response policies, and providing clear contact information to enhance trust and compliance.

Scanned

NIS2 and GDPR posture

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

5 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 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 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

  3. 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 arme-project.co.uk

This scan found 24 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
42
Security headers
70
Email security
70
DNS health
60
Network security
100
GDPR outside view
53
Average
66

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

ARME is positioned as a niche academic research project with a focus on augmented reality applications in music synchronization. Its competitive advantage lies in its EPSRC funding and affiliation with the University of Birmingham, providing credibility and access to research resources. The business model is grant-funded research with outputs including publications, demos, and datasets. Target customers are academic researchers, musicians, and potentially educational institutions. Growth indicators include recent press releases, impact acceleration awards, and collaborations with creative industry initiatives. The partnership ecosystem includes university departments and UKRI programs. Operationally, the project maintains a professional web presence with consistent branding and active content updates, supporting its research dissemination goals.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and no visible exposed sensitive data or vulnerable libraries. However, it lacks important security headers such as Content-Security-Policy and X-Frame-Options, which could mitigate certain attack vectors. There is no published security policy or incident response plan, which limits transparency and preparedness. GDPR compliance is partial, with a privacy policy present but no cookie consent or explicit data protection officer contact. The absence of contact emails and phone numbers reduces user trust and incident reporting capabilities. Overall, the security culture appears basic and could benefit from formalizing policies and improving user privacy controls.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  2. Add a cookie consent banner/mechanism to comply with GDPR and inform users about tracking.
  3. Publish a clear security policy and incident response plan accessible from the website.
  4. Provide verified contact emails and phone numbers for user support and security incident reporting.
  5. Enhance accessibility features to improve inclusivity and compliance with standards.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Augmented Reality Music Ensemble
Description
The A.R.M.E. project is funded by EPSRC aiming to understand how musicians synchronize and to build computational models to reproduce musician behavior, enabling music training tools with virtual musicians.
Key services
Research publications, Music synchronization computational models, Music training tools, Demos and annotated music datasets
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, jQuery, Bootstrap, Wowchemy Hugo theme, MathJax, Font Awesome, Academicons, Fancybox, Highlight.js, Leaflet, Mermaid, Fuse.js, Mark.js, Netlify Identity
Frameworks
Bootstrap, Wowchemy (Hugo-based)
Platforms
Netlify (implied by Netlify Identity widget)
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • No visible exposed sensitive data
  • No vulnerable libraries detected in scripts

Analytics and tracking

Services
Google Analytics
Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is a research project site with academic focus.
  2. No contact emails or phone numbers explicitly listed on the site.
  3. Physical address is provided in structured data only.
  4. No privacy or cookie consent banners detected.
  5. No terms of service or security policies published.
  6. Uses modern web technologies and frameworks.
  7. No signs of malicious or suspicious content.
  8. Good SEO and metadata usage including Open Graph and JSON-LD.
  9. No forms collecting personal data detected on the homepage.
  10. Google Analytics is used for visitor tracking.
Technical notes

Notes

The website is built on a modern static site generator (Wowchemy for Hugo) with a robust tech stack including Bootstrap, jQuery, MathJax, and other libraries supporting rich content and interactivity. Hosting is likely via Netlify, providing scalability and performance benefits. The site loads moderately fast with good mobile optimization and SEO metadata. There is no evidence of technical debt or outdated technologies. Opportunities exist to improve accessibility and implement security best practices. The technical infrastructure supports the academic and research goals effectively with minimal risks to operational continuity.
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 arme-project.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 arme-project.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.