Skip to main content

Security report for rba.gov.au

Reserve Bank of Australia · Government · Australia

Low risk. 3 critical or high findings in Security headers and GDPR outside view.

Security score

76/100

Risk levelLow

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

The Reserve Bank of Australia (RBA) is the nation's central bank responsible for conducting monetary policy, maintaining financial system stability, issuing currency, and providing banking services to the government. The website serves a broad audience including the Australian public, financial institutions, government entities, researchers, and educators. It provides authoritative content on economic conditions, policy decisions, and financial infrastructure. The RBA holds a dominant market position as the sole central bank in Australia, with a large organizational size and a history dating back to 1959. Technically, the website employs modern JavaScript libraries and trusted analytics tools such as Microsoft Clarity, Google Tag Manager, and LinkedIn Insight Tag. The site is well-optimized for performance, mobile responsiveness, and accessibility, with a professional and consistent design. However, it uses a custom or undisclosed CMS and does not explicitly declare some security headers, which could be improved. From a security perspective, the site enforces HTTPS and avoids exposing sensitive data. It uses secure forms and trusted third-party scripts but lacks explicit security policies and incident response contacts. The WHOIS data is limited due to Australian domain registry policies but aligns with the official government entity status, supporting legitimacy. No WAF or blocking mechanisms were detected, and no vulnerabilities were found in the content. Overall, the RBA website demonstrates a high level of professionalism, security, and compliance with minor gaps in privacy consent mechanisms and explicit security headers. It is a trustworthy and authoritative source of information for its stakeholders.

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

3 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

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

Keep watching rba.gov.au

This scan found 19 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
90
Security headers
50
Email security
85
DNS health
75
Network security
100
GDPR outside view
53
Average
76

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 RBA operates as a government central bank with a clear mandate under the Reserve Bank Act 1959. Its business model focuses on monetary policy implementation, financial system oversight, and currency issuance, serving the Australian economy and government. The website reflects a strong market position with comprehensive content and multiple communication channels including social media and RSS feeds. Revenue streams are government-funded, with no commercial sales. The target customers include policymakers, financial institutions, educators, and the general public. The RBA maintains partnerships with related government bodies and financial regulators, enhancing its ecosystem. Growth indicators include ongoing publications, research, and educational resources. The website's strategic observations highlight a focus on transparency, public engagement, and digital modernization.

Security posture

The RBA website exhibits a mature security posture with enforced HTTPS, secure form handling, and use of reputable analytics services. However, the absence of explicit security headers such as Content-Security-Policy and X-Frame-Options represents an area for improvement. No exposed sensitive information or vulnerable libraries were detected. The site lacks a publicly visible security policy or incident response contact, which could enhance transparency and preparedness. DNSSEC is not indicated, which could be considered to strengthen domain security. Overall, the security posture is strong but could benefit from formalized policies and enhanced header configurations.

Recommendations

  1. Implement explicit security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  2. Introduce a cookie consent mechanism to comply with privacy regulations and improve user transparency regarding tracking.
  3. Publish a formal security policy and incident response contact information to increase trust and preparedness.
  4. Evaluate and implement DNSSEC to improve domain name system security.
  5. Regularly audit third-party scripts and tracking tools to mitigate potential vulnerabilities and privacy risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Reserve Bank of Australia
Description
Australia's central bank conducting monetary policy, maintaining financial system stability, issuing currency, and providing banking services to the government.
Key services
Monetary policy, Payments system operation, Financial stability oversight, Banknote issuance, Banking services to government
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, Google Tag Manager, Microsoft Clarity, YouTube API, LinkedIn Insight Tag
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 proper labels and autocomplete off
  • Use of external trusted analytics and tracking scripts

Analytics and tracking

Services
Microsoft Clarity, Google Analytics, LinkedIn Insight Tag
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Microsoft Clarity, Google Analytics (via GTM), LinkedIn Insight Tag
Marketing tools
LinkedIn Insight Tag
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 rich content and no blocking detected.
  2. Strong government branding and authoritative content.
  3. No explicit privacy or cookie consent banner found, which may be a compliance gap.
  4. Use of multiple trusted analytics and tracking services.
  5. WHOIS data limited due to registry policy but consistent with official entity.
  6. No security policy or incident response contact publicly visible.
  7. No phone numbers explicitly labeled as contact found in HTML content.
  8. Multiple social media channels actively linked.
  9. No suspicious or malicious content detected.
Technical notes

Notes

The website uses a modern JavaScript-based front end with asynchronous loading of analytics and tracking scripts from Microsoft Clarity, Google Tag Manager, YouTube, and LinkedIn. The site is well-structured with semantic HTML and meta tags supporting SEO and accessibility. Performance is optimized with minified CSS and JavaScript assets. The site is mobile responsive and includes accessibility features such as skip links and ARIA labels. The CMS is not explicitly identified, suggesting a custom or proprietary solution. Hosting details are not disclosed but the site uses HTTPS with a valid certificate. There is no evidence of technical debt or deprecated technologies. Opportunities exist to enhance security headers and privacy compliance mechanisms.
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 rba.gov.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 rba.gov.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.