Skip to main content

Security report for sjog.org.au

St John of God Health Care · Healthcare · Australia

Medium risk. 6 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

52/100

Risk levelMedium

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

St John of God Health Care is a well-established, large not-for-profit Catholic healthcare provider operating across Australia and New Zealand. The organization offers a broad range of healthcare services including hospitals, home nursing, disability services, mental health, maternity, and community outreach programs. The website reflects a mature digital presence with comprehensive content targeting patients, visitors, healthcare professionals, and caregivers. Technically, the site uses modern analytics and tracking tools, a .NET SDK backend, and is optimized for mobile and accessibility. Security posture is good with HTTPS and anti-forgery tokens, but lacks explicit security headers and published security policies. Privacy compliance is basic, with a privacy policy present but no cookie consent mechanism. Overall, the site is professional, trustworthy, and well-branded, with minor improvements recommended in security and privacy transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
28/ 100 · High
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

6 findings rated critical or high. Fix these first.

  1. 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

    • 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

  2. 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

  3. 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';…

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

Keep watching sjog.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. 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
0
Security headers
30
Email security
80
DNS health
75
Network security
100
GDPR outside view
28
Average
52

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention sjog.org.au, from OffSeq Breach.

Total records
688
Employees
1
Customers
667
Third parties
20
Weak passwords
8%

Latest record dated 2026-01-10 · 38 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for sjog.org.au.

Select it in the checkout above.

Masked preview

  • –idpf5.sjog.org.au2026-01-10

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The organization holds a strong market position as one of the largest Catholic healthcare providers in the region, with a history dating back to 1895. Its business model focuses on not-for-profit healthcare delivery with multiple subsidiaries specializing in disability and community services. The website supports recruitment, patient information, and community engagement, indicating diversified revenue streams and stakeholder engagement. Partnerships with foundations and subsidiaries are clearly linked. The digital ecosystem includes extensive use of analytics and marketing tools, supporting growth and outreach strategies.

Security posture

The website demonstrates a solid security foundation with HTTPS and anti-forgery tokens in forms. However, it lacks several security best practices such as explicit security headers (CSP, HSTS), published incident response or security policies, and a vulnerability disclosure program. No vulnerabilities or exposed sensitive data were detected in the HTML content. The absence of cookie consent mechanisms may pose compliance risks in certain jurisdictions. Overall, the security posture is good but could be enhanced with additional transparency and technical controls.

Recommendations

  1. Implement and publish a comprehensive security policy and incident response plan on the website.
  2. Add explicit security headers including Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), X-Frame-Options, and X-XSS-Protection.
  3. Deploy a cookie consent banner/mechanism to comply with GDPR and other privacy regulations.
  4. Publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Enhance privacy compliance by clearly stating data retention policies and user rights.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
St John of God Health Care
Description
St John of God Health Care is a leading Catholic not-for-profit health care provider in Australia, established in Western Australia in 1895. It operates 26 facilities with more than 3,300 hospital beds across Australia and New Zealand, offering hospitals, home nursing, disability services, and social outreach programs.
Key services
Hospitals, Home nursing, Disability services, Community and youth services, Mental health and therapy, Maternity, Medical and surgical, Rehabilitation services
Content quality
excellent
Branding
consistent

Technology

Stack
Google Analytics, Google Tag Manager, Facebook Pixel, Hotjar, jQuery, Owl Carousel, Monsido, Spotify Pixel
Frameworks
.NET SDK 1.4.16
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enabled
  • No exposed sensitive data in HTML
  • Use of anti-forgery token in forms

Analytics and tracking

Services
Google Analytics, Hotjar, Facebook Pixel
Tracking level
extensive
Privacy practices
basic

Advertising

Ad networks
Google Ads
Tracking pixels
Facebook Pixel, Hotjar, Spotify Pixel, Monsido
Marketing tools
Qualtrics
Transparency
good

Site quality

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

Key observations

  1. Website is a professionally designed healthcare provider site with comprehensive service and location information.
  2. Strong presence of healthcare-related content and community engagement.
  3. No signs of phishing or malware.
  4. Use of multiple analytics and tracking tools indicates marketing and user behavior analysis focus.
  5. Lacks explicit cookie consent mechanism and published security policies.
  6. No visible contact emails or phone numbers in HTML; contact primarily via forms and social media.
Technical notes

Notes

The website is built on a .NET SDK platform with a modern frontend using jQuery and Owl Carousel for UI components. It integrates multiple third-party analytics and marketing tools such as Google Analytics, Facebook Pixel, Hotjar, Monsido, and Spotify Pixel. The site is mobile-optimized and accessible with good SEO practices including meta tags and Open Graph data. Performance is moderate, with asynchronous loading of scripts and responsive images. There is no clear CMS identified, suggesting a custom or proprietary solution. Hosting provider details are not explicit. The technical stack supports a professional and scalable healthcare website but could benefit from enhanced security headers and privacy features.
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 sjog.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 sjog.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.