Opening the security report for www.disasterrisklab.berkeley.edu
www.disasterrisklab.berkeley.edu
Loading the security report for www.disasterrisklab.berkeley.edu
www.disasterrisklab.berkeley.edu
Is www.disasterrisklab.berkeley.edu Safe? Security Score 59/100 | CyStack
www.disasterrisklab.berkeley.edu
Origin DNS error | www.disasterrisklab.berkeley.edu | Cloudflare
UC Berkeley pushes the boundaries of knowledge, challenges convention and expands opportunity to create the leaders of tomorrow.
Industry
Science and Education / Universities and Colleges
Origin
United States
Global rank
#3,455
Rank in United States
#846
Updated at
F59/100
Security level
Low
Data confidence
High
Scope checked
96.4%
The higher the score, the more externally observable protections the system has recorded. This page does not certify that the website is reputable, legitimate, or completely free of vulnerabilities.
Is the website “www.disasterrisklab.berkeley.edu” safe?
As of September 9, 2026 at 16:12, www.disasterrisklab.berkeley.edu has a security score of 59/100 (grade F – “Low”). CyStack’s automated assessment recorded 9 issues to review after completing 96.4% of applicable checks. The website owner should address “HTTPS/TLS endpoint reachability” first, then review the remaining items in order of impact.
Does www.disasterrisklab.berkeley.edu show known scam, phishing, or malware signals?
At assessment time, CyStack did not find www.disasterrisklab.berkeley.edu or related infrastructure on any scam, phishing, or malware warning list after checking 5 online reputation sources. This result reflects external observations; it does not guarantee absolute safety or verify the organization’s legal status or reputation.
Potentially exposed domain email addressesChecks infostealer data for email addresses ending in @berkeley.edu, the registered domain of the assessed website www.disasterrisklab.berkeley.edu. A record is not counted merely because someone visited or signed in to the website.1,743 Matching email exposure records
1,743Matching email exposure records
153Related infected devices (estimated)
These matching email records were observed previously, but they may already have been addressed or may no longer be valid. The device count estimates infected devices associated with these email records; it is not the number of devices owned by the organization.
Frequently asked questions
What affects the security of www.disasterrisklab.berkeley.edu?
A valid SSL certificate still does not prove that www.disasterrisklab.berkeley.edu is safe, legitimate, or free of scam signals. For a more complete assessment, this report also checks phishing and malware, exposed email records, IPs and open ports, subdomains, technologies, and CVEs that may apply to observed versions.
Does www.disasterrisklab.berkeley.edu use HTTPS, and is its SSL certificate valid?
HTTPS on www.disasterrisklab.berkeley.edu could not be reached during this assessment, so its SSL certificate and transport encryption could not be evaluated.
Have @berkeley.edu email addresses appeared in exposed data or information-stealer (infostealer) logs?
Data sources
Data compiled from CyStack cybersecurity monitoring systems
CyStack compiles scan results from its internal cybersecurity monitoring systems, including CyStack VulnScan and CyStack Threat Intelligence, together with publicly available Internet data. The assessment only observes and analyzes information already available; it does not attempt unauthorized access, test passwords, send exploit code, or change or disrupt the assessed system.
These 3 failed checks or warnings have the greatest impact on the result for www.disasterrisklab.berkeley.edu.
HTTPS/TLS endpoint reachabilityA TLS connection could not be established on the tested HTTPS endpoint (port 443).Critical
Why it matters
This check only confirms whether a TLS handshake can be established with at least one tested resolved endpoint on the HTTPS port. Certificate trust, hostname identity, validity, chain, protocol, and cryptographic strength are evaluated separately.
What to do
Provide the entire website over HTTPS using a certificate trusted by common browsers.
Diagnostic information
The scanner could not complete a TLS handshake with the HTTPS endpoint during this assessment.
Evidence and check scope
HTTPS port tested:
443
Connection established:
No
Host requested:
www.disasterrisklab.berkeley.edu
Resolved IPs tested:
141.193.213.10, 141.193.213.11
IPs with conclusive connection failure:
141.193.213.10, 141.193.213.11
This is the port on which the scanner attempted a TLS connection. The port number alone does not prove that the port is open or that HTTPS works.
Allowed browser content (CSP)The inspected root HTML response does not include a Content-Security-Policy header.High
Why it matters
Content Security Policy (CSP) limits where scripts, styles, frames, and other browser content may come from. A strong policy reduces the impact if an attacker manages to inject content into a page.
What to do
Define only the sources the application needs, test the policy before activating it, and avoid broad wildcard (*) rules, unsafe-inline, and unsafe-eval where possible.
Correct file-type handling (nosniff)The inspected root response does not set X-Content-Type-Options to nosniff.Medium
Why it matters
Without the nosniff setting, a browser may guess a file's type and treat harmless-looking content as executable code. This can turn an incorrect Content-Type into a security issue.
What to do
Send X-Content-Type-Options: nosniff on every response and return an accurate Content-Type.
Scope of this check
Leak evidenceMost recent observation:
Email addressRelated infected deviceInfection evidenceRecorded time
Discovered subdomains (1,209+)Subdomains of berkeley.edu, the registered domain of the assessed website www.disasterrisklab.berkeley.edu. Sensitive-looking names are shown first; individual subdomains have not been separately security-tested.Partial
Results were bounded and may be truncated.
admin.millennium.berkeley.eduSensitive-lookingAdmin system
Public web contextThe website title, description, industry and popularity.
Page title
Origin DNS error | www.disasterrisklab.berkeley.edu | Cloudflare
Website category
Science and Education / Universities and Colleges
Description
UC Berkeley pushes the boundaries of knowledge, challenges convention and expands opportunity to create the leaders of tomorrow.
Global rank
#3,455
Rank in United States
#846
Rank in industry
#12
Final URL
http://www.disasterrisklab.berkeley.edu/
Website rankings and industry category are based on data from Similarweb
This is a quick, point-in-time check from outside the organization. It can surface visible risks, but it does not replace penetration testing or an authenticated assessment.
There are currently 1,743 exposed email records matching the berkeley.edu domain. These records may be old or already resolved. The website owner should verify them before resetting passwords or locking related accounts.
Which public IPs, services, and ports does www.disasterrisklab.berkeley.edu expose?
The assessment observed 2 public IPs and 8 open ports for www.disasterrisklab.berkeley.edu. An open port is not the same as a vulnerability, but the website owner should keep every public service updated and appropriately restrict access.
How many subdomains of berkeley.edu have been discovered?
The assessment observed 1,209+ public subdomains of berkeley.edu. This list can reveal additional entry points such as APIs, administration systems, or test environments, but it does not mean that every subdomain is risky.