Skip to main content

Security report for alaska.edu

University of Alaska · Education · United States

Medium risk. 4 critical or high findings in Security headers and SSL/TLS.

Security score

75/100

Risk levelMedium

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

The University of Alaska operates the website www.alaska.edu as a subdomain under its main alaska.edu domain, serving as a digital portal for educational and research services. The institution is a large public university system focused on providing higher education and community outreach within the state of Alaska. The website targets students, faculty, researchers, and the general public interested in academic programs and university resources. The business model is that of a public educational institution, with a strong market position as the primary higher education provider in Alaska. Technically, the website employs modern frontend technologies such as Bootstrap 4.6.1 and FontAwesome 6.7.2, along with multiple analytics and marketing tools including Google Tag Manager, Google Analytics, Hotjar, and Facebook Pixel. The site appears to be mobile optimized and has a moderate performance profile. However, no CMS or hosting provider details were explicitly identified from the provided data. From a security perspective, the site uses HTTPS and standard third-party scripts but lacks visible security headers and explicit privacy or cookie policies in the analyzed content. No forms or contact information were detected, which limits the assessment of input security and user data handling. The absence of privacy and cookie policies suggests potential compliance gaps with GDPR and other privacy regulations. Overall, the website is legitimate and trustworthy as an educational institution's digital presence, but it would benefit from enhanced privacy compliance and security best practices to improve user trust and regulatory adherence.

Scanned

NIS2 and GDPR posture

GDPR outside view
95/ 100 · Low
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

4 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. 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 alaska.edu

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
67
Security headers
15
Email security
85
DNS health
85
Network security
100
GDPR outside view
95
Average
75

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

Total records
4,671
Employees
20
Customers
3,245
Third parties
1,406
Weak passwords
12%

Latest record dated 2026-06-12 · 93 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 alaska.edu.

Select it in the checkout above.

Masked preview

  • –jlc-web.uaa.alaska.edu2026-06-12
  • –classes.alaska.edu2026-06-09
  • –online.uas.alaska.edu2026-06-02
  • –www.alaska.edu2026-02-22
  • –me.uaa.alaska.edu2026-02-22

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 University of Alaska holds a strong position in the education sector within the United States, specifically serving the Alaskan region. Its business model revolves around public funding and tuition-based revenue streams, targeting students seeking undergraduate and graduate education, as well as research collaborators. The website supports this model by providing access to academic resources, program information, and community engagement. The presence of multiple analytics and marketing tools indicates an interest in understanding user behavior and improving outreach. The lack of explicit contact information or detailed business registration data on the site is typical for public universities, which often centralize such information elsewhere. The institution's branding is consistent and professional, reinforcing its credibility and market presence.

Security posture

The website demonstrates a basic to moderate security posture. HTTPS is used, which is mandatory for secure communications. However, the absence of key security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security reduces the overall security effectiveness. The use of multiple third-party scripts introduces potential risk vectors that require ongoing monitoring. No forms or user input fields were detected, which limits exposure to common web vulnerabilities like injection attacks. The lack of visible privacy and cookie policies indicates potential compliance and data protection gaps. Incident response and vulnerability disclosure mechanisms are not evident, which could delay mitigation of security incidents. Overall, the site is secure enough for informational purposes but should enhance security controls and compliance documentation to meet higher standards.

Recommendations

  1. Implement comprehensive privacy and cookie policies with clear user consent mechanisms to improve GDPR and privacy compliance.
  2. Add and configure security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to strengthen site security.
  3. Publish clear contact information including security incident response contacts to facilitate communication and trust.
  4. Conduct regular audits of third-party scripts and dependencies to identify and mitigate vulnerabilities.
  5. Develop and publicize a vulnerability disclosure policy or security.txt file to encourage responsible reporting of security issues.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
University of Alaska
Description
The University of Alaska is a public university system serving the state of Alaska, providing higher education and research opportunities.
Key services
Higher education, Research, Community outreach, Online learning
Content quality
good
Branding
consistent

Technology

Stack
Bootstrap 4.6.1, FontAwesome 6.7.2, Google Tag Manager, Google Analytics, Hotjar, Facebook Pixel, YouTube iframe API, Google Custom Search Engine
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • Use of HTTPS (implied by domain .edu and Google Tag Manager scripts)
  • No exposed sensitive data detected in HTML

Analytics and tracking

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

Advertising

Ad networks
Google Adsense, AppNexus
Tracking pixels
Facebook Pixel, Hotjar
Marketing tools
Google Custom Search Engine
Transparency
basic

Site quality

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

Key observations

  1. Website is a subdomain of alaska.edu, a legitimate educational institution domain.
  2. No WHOIS data for www.alaska.edu as it is a subdomain, not a registered domain.
  3. Website uses multiple third-party analytics and tracking tools.
  4. No visible privacy, cookie, or terms of service policies found in the provided HTML snippet.
  5. No contact emails or phone numbers explicitly found in the provided content.
  6. No forms detected in the provided HTML snippet.
  7. Website uses modern frontend technologies including Bootstrap and FontAwesome.
  8. No WAF or security challenge detected; content is accessible.
  9. Content is educational and safe for general audiences.
Technical notes

Notes

The website leverages a modern frontend stack with Bootstrap and FontAwesome for responsive design and iconography. It integrates multiple analytics and marketing tools, including Google Tag Manager, Google Analytics, Hotjar, and Facebook Pixel, indicating a mature approach to user behavior tracking and marketing. The site loads external resources from reputable CDNs, enhancing performance and reliability. However, no CMS or backend platform was identified, suggesting a custom or static site architecture. Performance is moderate, with good mobile optimization and basic accessibility features. SEO is supported by proper meta tags and structured data usage is not evident in the provided snippet. Technical debt appears low, but improvements in security headers and privacy compliance are recommended to modernize the infrastructure fully.
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 alaska.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 alaska.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.