ST

security.txt history

A historical index of security.txt files across the web.

security.txt

richmondmusictrust.org.uk

Collected on 2026-10-23 01:04 UTC.

# Our security address
Contact: disclosure@charanga.com
Preferred-Languages: en
Canonical: https://charanga.com/.well-known/security.txt

# Our acknowledgments page
Acknowledgments: https://charanga.com/hall_of_fame

# Our security policy. Please read this before undertaking research or reporting any issues
Policy: https://docs.google.com/document/d/1Nh3RnQ1WDByjz6QfGgt3Bl9l1c4lNisqUHwGbRa1OaE/

# For the avoidance of doubt, we do not consider these to be reportable issues,
# so please don't report them:
#
# 1. Volumetric vulnerabilities (i.e. denial-of-service or overwhelming our
#    service with a high volume of requests)
#
# 2. ssh and ssh username enumeration
#
# 3. TLS configuration weaknesses (i.e. weak ciphersuite support, TLS1.0
#    support, etc)
#
# 4. Email configuration (SPF, DKIM, DMARC, MTA-STS)
#
# 5. file: access in our CSP
#
# 6. Gaps in common best practice such as missing security headers 
#    (x-frame-options, x-prevent-xss etc)
#
# 7. Non-exploitable vulnerabilities
#
# 8. Older front-end libraries (jQuery, etc)

This file is shown exactly as published by the domain, as collected by the securitytxthistory crawler. 1,051 bytes · 33 lines.

Collection details

HTTP 200/.well-known/security.txttext/plain1 redirect
Collected URL

https://www.richmondmusictrust.org.uk/.well-known/security.txt

SHA-256

013f8593032f33876e097fd651e6a4cbf1de3d57a7f0cb1bff4708b0893b0d3a

Redirects

  1. 301https://richmondmusictrust.org.uk/.well-known/security.txt
  2. 200https://www.richmondmusictrust.org.uk/.well-known/security.txt