Skip to main content

Security report for asu.edu

Arizona State University · Education · United States

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

Security score

72/100

Risk levelMedium

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

Arizona State University (ASU) is a large, well-established public research university in the USA, offering a wide range of degree programs both in-person and online. The website reflects a mature digital presence with comprehensive academic, research, and community engagement content. ASU targets a broad audience including prospective students, current students, alumni, and researchers. The technical infrastructure is modern, leveraging Drupal 10 CMS, Font Awesome icons, and analytics tools such as Google Tag Manager and Optimizely. The site is mobile-optimized, accessible, and professionally designed, supporting a positive user experience. Security posture is good with HTTPS enforced and cookie consent implemented, though some security headers and explicit security policies are not publicly found. WHOIS data is unavailable from the raw output, likely due to .edu domain registry policies, but the website's legitimacy is supported by consistent branding and official content. Overall, ASU's website is a trustworthy and authoritative source for educational services and information.

Scanned

This is an earlier scan of asu.edu. View the latest report

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

  3. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

  4. 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 SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching asu.edu

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
65
Security headers
65
Email security
50
DNS health
85
Network security
100
GDPR outside view
68
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

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 asu.edu, from OffSeq Breach.

Total records
78,488
Employees
2,598
Customers
47,682
Third parties
28,208
Weak passwords
7%

Latest record dated 2026-06-18 · 503 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 asu.edu.

Select it in the checkout above.

Masked preview

  • –federation.asu.edu2026-06-18
  • –asu.edu2026-06-17
  • –federation.asu.edu2026-06-17
  • –federation.asu.edu2026-06-17
  • –federation.asu.edu2026-06-17

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

Technical appendix

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

Business context

Business profile

ASU holds a strong market position as a leading public university with multiple campuses and extensive online offerings. Its business model focuses on education, research, and public service, supported by a large enterprise-scale digital platform. The university's ecosystem includes various subsidiary domains for specialized campuses and initiatives, enhancing its reach and service delivery. The presence of official social media channels and comprehensive contact information supports engagement and transparency. ASU's strategic emphasis on innovation and accessibility is evident in its digital content and program offerings.

Security posture

The website demonstrates a solid security foundation with HTTPS enabled and cookie consent mechanisms in place. However, the absence of explicit security headers such as Content-Security-Policy and a publicly available security policy or incident response page indicates room for improvement. No vulnerabilities or exposed sensitive data were detected in the analysis. The lack of a vulnerability disclosure or security.txt file suggests that security communication could be enhanced to better support responsible disclosure and incident management.

Recommendations

  1. Implement and publish comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  2. Develop and make publicly accessible a security policy and incident response page to improve transparency and preparedness.
  3. Consider publishing a vulnerability disclosure policy or security.txt file to facilitate responsible vulnerability reporting.
  4. Regularly audit third-party scripts and libraries to ensure no vulnerable components are included.
  5. Enhance monitoring and logging capabilities to detect and respond to security incidents promptly.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Arizona State University
Description
Arizona State University is a comprehensive public research university committed to excellence in education, research, innovation, and serving learners at every stage of life.
Key services
Degree programs (in-person and online), Research and innovation, Community engagement, Virtual tours and admissions support
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 10, Font Awesome 6, Google Tag Manager, Optimizely, Glide.js
Frameworks
Drupal
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of Google Tag Manager for analytics
  • Cookie consent mechanism present

Analytics and tracking

Services
Google Tag Manager, Optimizely
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Optimizely
Marketing tools
Optimizely
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 mechanisms.
  2. Uses modern CMS (Drupal 10) and standard web technologies.
  3. Strong branding and consistent user experience.
  4. Comprehensive contact and legal information present.
  5. No security policy or incident response page publicly found.
  6. No WHOIS data available from provided raw output.
  7. Multiple official social media and partner domains linked.
  8. Cookie consent mechanism implemented.
  9. No adult or questionable content detected.
Technical notes

Notes

The website is built on Drupal 10, a modern and widely supported CMS, ensuring a robust content management framework. It uses Font Awesome 6 for icons and integrates Google Tag Manager and Optimizely for analytics and experimentation. The site is mobile-optimized and accessible, with good SEO practices evident in meta tags and structured data. Performance is moderate, likely influenced by rich media content and third-party scripts. There is an opportunity to improve technical security configurations and optimize loading times further. Overall, the technical infrastructure supports a scalable and user-friendly digital experience aligned with enterprise-level educational services.
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. 72/100Medium27 findingsView report
  2. 72/100Medium30 findingsView report
Reviews of this site

Share your experience with asu.edu. 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 asu.edu.

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.