Skip to main content

Security report for rbcroyalbank.com

Royal Bank of Canada · Finance · Canada

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

Security score

68/100

Risk levelMedium

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

Royal Bank of Canada (RBC) operates a comprehensive personal banking website offering a wide range of financial products and services including bank accounts, credit cards, loans, mortgages, investments, and insurance. The website is professionally designed with consistent branding and clear navigation, targeting personal banking customers primarily in Canada. The business model focuses on providing essential financial services with a strong market position as one of Canada's largest banks. Technically, the site employs modern web technologies such as Google Tag Manager, Conductrics for A/B testing, and Bing Ads for advertising, with good mobile optimization and accessibility features. Security posture is strong with HTTPS enforced and secure sign-in mechanisms, though explicit security headers could be confirmed. Privacy and cookie policies are present with consent mechanisms, indicating good compliance with GDPR and related regulations. The absence of WHOIS data in the raw output is unusual but likely due to query failure or privacy protection; however, the website content and branding strongly indicate legitimacy. Overall, the site scores highly on content quality, technical implementation, security, privacy compliance, and business credibility.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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 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 rbcroyalbank.com

This scan found 22 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
72
Security headers
15
Email security
70
DNS health
85
Network security
100
GDPR outside view
68
Average
68

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

RBC's personal banking website reflects a mature financial institution with a diversified product portfolio and a large enterprise scale. The site integrates multiple partner domains related to wealth management, asset management, capital markets, and investor services, indicating a broad ecosystem. The business targets Canadian personal banking customers with tailored products and services, including cross-border banking options. The website's detailed navigation and resources suggest a customer-centric approach with emphasis on education and support. Advertising and analytics tools are used responsibly with transparency and consent. The absence of direct registrant WHOIS data is a minor concern but does not detract from the overall business credibility given RBC's established brand.

Security posture

The website demonstrates a strong security posture with mandatory HTTPS, secure login links, and privacy policies. Use of third-party analytics and advertising scripts is evident but appears managed with consent mechanisms. No exposed sensitive data or vulnerabilities were detected in the HTML content. Security headers are implied but not explicitly confirmed in the provided data. Incident response contacts or vulnerability disclosure pages were not found, which could be improved. Overall, the site aligns with best practices for a financial institution's online presence, though explicit security header confirmation and incident response information would enhance trust.

Recommendations

  1. Confirm and explicitly implement security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  2. Publish a dedicated vulnerability disclosure policy or security.txt file to improve transparency and incident response readiness.
  3. Ensure all third-party scripts are regularly audited for security and privacy compliance.
  4. Maintain and regularly update privacy and cookie consent mechanisms to align with evolving regulations.
  5. Consider publishing data protection officer contact information to enhance GDPR compliance and user trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Royal Bank of Canada
Description
RBC Royal Bank offers personal banking services and products to help customers manage finances, buy homes, invest, and more.
Key services
Bank Accounts, Credit Cards, Loans, Mortgages, Investments, Rewards, Insurance, Customer Service
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, Google Tag Manager, Web Vitals, Bing Ads, Conductrics (A/B testing), CSS3, HTML5
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Secure sign-in links
  • No exposed sensitive data in HTML
  • Use of secure cookies (implied)
  • Consent mechanism for cookies

Analytics and tracking

Services
Google Analytics (via GTM), Bing Ads, Conductrics
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Bing Ads
Tracking pixels
Bing Ads, Conductrics
Marketing tools
Conductrics
Transparency
good

Site quality

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

Key observations

  1. Website is professionally designed with comprehensive personal banking product offerings.
  2. Strong branding consistent with Royal Bank of Canada.
  3. Multiple navigation menus with detailed product and service categories.
  4. Presence of privacy and cookie policies with consent mechanisms.
  5. Use of modern web technologies and analytics tools.
  6. No signs of adult or inappropriate content.
  7. WHOIS data unavailable, possibly due to query failure or privacy protection.
  8. No WAF or blocking detected; site content fully accessible.
Technical notes

Notes

The website uses a modern tech stack including JavaScript, Google Tag Manager, and Conductrics for analytics and A/B testing. The site is mobile-optimized with responsive design and accessibility features. Performance is moderate, likely due to rich media content such as videos. No CMS or hosting provider details were explicitly detected. The site structure is clear with comprehensive meta tags and SEO optimization. Technical risks are minimal with no visible outdated or vulnerable libraries. Opportunities exist to enhance security header implementation and incident response transparency.
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

Earlier scans of this domain

  1. 68/100Medium29 findingsView report
Reviews of this site

Share your experience with rbcroyalbank.com. 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 rbcroyalbank.com.

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.