Skip to main content

Security report for uwaterloo.ca

University of Waterloo · Education · Canada

Low risk. 3 critical or high findings in GDPR outside view and SSL/TLS.

Security score

76/100

Risk levelLow

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

The University of Waterloo is a leading Canadian educational institution known for its innovation, entrepreneurship, and comprehensive research programs. The website serves a broad audience including prospective and current students, faculty, and the general public. It provides extensive information about academic programs, events, news, and community engagement. The university holds a strong market position as a top-ranked institution in Canada with a large operational scale and a well-established digital presence. Technically, the website is built on Drupal 9 CMS and integrates multiple modern analytics and marketing tools such as Google Analytics, Microsoft Clarity, LinkedIn Insight Tag, and Twitter Universal Website Tag. The site is well-optimized for performance, mobile responsiveness, and accessibility, reflecting a mature digital infrastructure. From a security perspective, the site enforces HTTPS, uses domain transfer protection, and employs various security best practices. However, DNSSEC is not enabled, and explicit Content-Security-Policy headers were not detected in the HTML source, which are areas for improvement. Privacy compliance is robust with clear cookie consent mechanisms and a comprehensive privacy policy. Overall, the University of Waterloo website demonstrates a high level of professionalism, security, and compliance, supporting its reputation as a trusted educational institution. Strategic recommendations include enabling DNSSEC, enhancing security headers, and formalizing vulnerability disclosure policies to further strengthen security posture.

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

  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.

    • High

      SSL Certificate Expires Soon

      SSL certificate expires in 11 days

      What to do: Renew SSL certificate before expiration

      • NIS2 21(2)(h)
      • IR 2024/2690 9.2(c): Implementing Regulation (EU) 2024/2690, Annex point 9.2(c): Cryptography
      • NIST SC-17: NIST SP 800-53 Rev. 5 SC-17: Public Key Infrastructure Certificates

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

Keep watching uwaterloo.ca

This scan found 20 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
85
Security headers
70
Email security
75
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 University of Waterloo operates as a public university in the education sector, targeting students at various levels and the research community. It leverages its strong reputation for innovation and entrepreneurship to attract students and partners. The business model focuses on education delivery, research funding, and community engagement. The university maintains a large-scale operation with extensive digital outreach and partnerships. Its competitive advantages include top national rankings, comprehensive program offerings, and a strong brand presence. The website supports these objectives by providing detailed program information, news updates, and event promotion, facilitating engagement with its diverse audience.

Security posture

The website exhibits a mature security posture with HTTPS enforcement and domain transfer protection. The absence of DNSSEC is a notable gap that could expose the domain to DNS spoofing attacks. The use of multiple third-party analytics and marketing scripts introduces a moderate risk surface that requires ongoing monitoring. No critical vulnerabilities or exposed sensitive data were detected in the HTML content. Privacy and cookie compliance mechanisms are well implemented, supporting regulatory adherence. The lack of a published security policy or incident response contact limits transparency in security governance. Overall, the site is secure but could benefit from enhanced DNS security and formalized vulnerability disclosure processes.

Recommendations

  1. Enable DNSSEC to protect against DNS spoofing and improve domain security.
  2. Implement and enforce Content-Security-Policy headers to mitigate cross-site scripting risks.
  3. Establish and publish a vulnerability disclosure policy and security.txt file to facilitate responsible reporting.
  4. Regularly audit and update third-party scripts to minimize security risks from external dependencies.
  5. Enhance transparency by publishing a security policy and incident response contact information.

Contact details published on the site

Addresses
Legal name
University of Waterloo
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
University of Waterloo
Description
University of Waterloo is a comprehensive research university in Canada, highly ranked for innovation, entrepreneurship, and research excellence. It offers programs for high school, transfer, and graduate students, and hosts events and news related to academic and community life.
Key services
Undergraduate and graduate education, Research programs, Community engagement, Events and news dissemination
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 9 CMS, Google Tag Manager, Google Analytics, Microsoft Clarity, LinkedIn Insight Tag, Twitter Universal Website Tag, Mailchimp, StackAdapt, Acuity Platform pixel, YouTube Player API, MathJax
Frameworks
Drupal
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited domain status
  • No DNSSEC enabled (recommend enabling)
  • Use of security and analytics scripts with async loading

Analytics and tracking

Services
Google Analytics, Microsoft Clarity, LinkedIn Insight Tag, Twitter Analytics, Yahoo Analytics
Tracking level
extensive
Privacy practices
good

Advertising

Ad networks
StackAdapt, Twitter Ads, Acuity Platform, Yahoo Analytics
Tracking pixels
Facebook Pixel, LinkedIn Insight Tag, Microsoft Clarity, Twitter Universal Website Tag, Yahoo Analytics
Marketing tools
Mailchimp
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 maintained university site with comprehensive content.
  2. Strong branding and consistent design throughout.
  3. Multiple social media channels actively linked.
  4. Use of modern web technologies and analytics tools.
  5. Good privacy and cookie compliance mechanisms in place.
  6. No signs of malicious or suspicious activity.
  7. Domain registration data supports legitimacy and trust.
Technical notes

Notes

The University of Waterloo website is powered by Drupal 9 CMS, leveraging a modern tech stack including Google Tag Manager, Google Analytics, Microsoft Clarity, and various social media tracking pixels. The site is well-structured with valid HTML and CSS, optimized for fast loading and mobile responsiveness. Accessibility features are implemented to support diverse users. The hosting and domain registration are consistent with the university's Canadian location and institutional identity. Performance is fast with asynchronous loading of scripts. The site uses canonical URLs and Open Graph metadata for SEO and social sharing. Technical risks include reliance on multiple third-party scripts and lack of DNSSEC, which should be addressed to maintain security and performance.
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 uwaterloo.ca. 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 uwaterloo.ca.

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.