Skip to main content

Security report for mshc.org.au

Melbourne Sexual Health Centre · Healthcare · Australia

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

Security score

72/100

Risk levelMedium

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

Melbourne Sexual Health Centre (MSHC) is a reputable healthcare provider specializing in sexual health services, education, and research based in Melbourne, Australia. The website clearly communicates its mission to improve sexual health through innovative healthcare, clinical education, and research leadership. It serves both the general public and health professionals with a broad range of services including STI testing, treatment, digital services, and vaccination programs. The centre operates under the umbrella of Alfred Health, enhancing its credibility and market position. Technically, the website employs modern web technologies such as Google Analytics, Google Tag Manager, Mapbox GL JS, and uses ExpressionEngine CMS. The site is well-optimized for mobile devices, features good SEO practices, and provides a professional user experience with clear navigation and comprehensive content. Performance is fast, and accessibility is good, although some improvements in security headers and cookie consent mechanisms are recommended. From a security perspective, the site uses HTTPS with no visible exposed sensitive data and includes CSRF tokens in forms, indicating good baseline security practices. However, the absence of explicit security headers and a cookie consent mechanism are areas for enhancement. The WHOIS data is privacy protected, which is justified for a healthcare entity, and no suspicious patterns were detected. Overall, the site demonstrates a strong security posture with room for incremental improvements. Overall, MSHC's website is a trustworthy, professional, and well-maintained digital presence that effectively supports its healthcare mission. Strategic recommendations include enhancing security headers, implementing cookie consent, and publishing security policies to further strengthen 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 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 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

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

Keep watching mshc.org.au

This scan found 21 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
82
Security headers
40
Email security
85
DNS health
70
Network security
100
GDPR outside view
53
Average
72

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

MSHC holds a strong market position as a leading sexual health centre in Melbourne, supported by its affiliation with Alfred Health. Its business model integrates direct healthcare services, education for health professionals, and research activities, creating multiple revenue and impact streams. The target audience includes both the general public seeking sexual health services and healthcare professionals requiring clinical education and resources. The website's partnership ecosystem includes Alfred Health and related donation and STI resource platforms, indicating a collaborative approach. Growth indicators include expanded digital services and vaccination programs. The organization demonstrates a commitment to inclusivity and community engagement, enhancing its reputation and reach within the healthcare sector.

Security posture

The website exhibits a mature security posture with HTTPS enforced, secure form handling, and no visible sensitive data exposure. However, the lack of explicit security headers such as Content-Security-Policy and X-Frame-Options represents a moderate gap. The absence of a published security policy or incident response information limits transparency. No vulnerability disclosure program or security.txt file was found, which could improve security culture and incident management. Compliance with privacy regulations is partially demonstrated through a comprehensive privacy policy, but cookie consent mechanisms are missing despite tracking technologies. Overall, the security posture is solid but could benefit from enhanced transparency and technical controls.

Recommendations

  1. Implement and configure security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  2. Add a cookie consent banner/mechanism to comply with privacy regulations and inform users about tracking.
  3. Publish a dedicated security policy and incident response plan on the website to improve transparency and preparedness.
  4. Consider establishing a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  5. Regularly review and update privacy compliance measures, including GDPR and local Australian privacy laws.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Melbourne Sexual Health Centre
Description
We improve people's sexual health. We provide innovation and excellence in healthcare, education and research. We lead the way in preventing and managing STIs.
Key services
STI testing and treatment, Sexual health education, Clinical guidelines for health professionals, Research studies, Digital sexual health services, Mpox vaccination
Content quality
excellent
Branding
consistent

Technology

Stack
Google Analytics, Google Tag Manager, Mapbox GL JS, Tippy.js, Popper.js, Polyfill.io, Instant.page
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Secure forms with CSRF tokens

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content and clear navigation.
  2. No WAF or blocking mechanisms detected.
  3. WHOIS data is privacy protected with minimal information.
  4. Strong affiliation with Alfred Health, a reputable healthcare provider.
  5. No suspicious or malicious content detected.
  6. No explicit security headers found; opportunity for improvement.
  7. No cookie consent mechanism detected despite tracking scripts.
  8. Comprehensive privacy policy and terms of service present.
  9. Multiple external trusted domains linked for resources and donations.
Technical notes

Notes

The website is built on a modern technology stack with ExpressionEngine CMS, enhanced by popular JavaScript libraries and services such as Google Analytics, Google Tag Manager, Mapbox GL JS, and Tippy.js. The site demonstrates fast loading times and excellent mobile responsiveness. SEO is well addressed through meta tags and structured navigation. Accessibility features such as skip links and ARIA labels are present, contributing to a good user experience. The use of CSRF tokens in forms indicates attention to security in data handling. Hosting details are not explicitly identified, but the domain and content delivery appear stable and reliable. Opportunities exist to improve security headers and cookie consent to reduce technical debt and enhance compliance.
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 mshc.org.au. 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 mshc.org.au.

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.