Opening the security report for www.crisisresponse.berkeley.edu
www.crisisresponse.berkeley.edu
Loading the security report for www.crisisresponse.berkeley.edu
www.crisisresponse.berkeley.edu
Is www.crisisresponse.berkeley.edu Safe? Security Score 94.1/100 | CyStack
www.crisisresponse.berkeley.edu
Home | Campus Mobile Crisis Response
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
A94.1/100
Security level
Excellent
Data confidence
High
Scope checked
97.3%
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.crisisresponse.berkeley.edu” safe?
As of September 9, 2026 at 20:02, www.crisisresponse.berkeley.edu has a security score of 94.1/100 (grade A – “Excellent”). CyStack’s automated assessment recorded 6 issues to review after completing 97.3% of applicable checks. The website owner should address “Allowed browser content (CSP)” first, then review the remaining items in order of impact.
Does www.crisisresponse.berkeley.edu show known scam, phishing, or malware signals?
At assessment time, CyStack did not find www.crisisresponse.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.crisisresponse.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.crisisresponse.berkeley.edu?
A valid SSL certificate still does not prove that www.crisisresponse.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.crisisresponse.berkeley.edu use HTTPS, and is its SSL certificate valid?
www.crisisresponse.berkeley.edu used a valid SSL certificate at assessment time, valid until November 14, 2026. This status may change when the certificate expires or the server configuration changes.
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.crisisresponse.berkeley.edu.
Allowed browser content (CSP)The CSP on the inspected root HTML response contains a broad, unsafe, or missing script-source control recognized by this bounded check.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.
Scope of this check
This check only evaluates the homepage response and content that the scanner could reach. Other pages and sign-in flows may use different settings.
Potentially sensitive subdomainsCyStack confirmed at least 1202 active DNS subdomains of berkeley.edu. 12 names may expose sensitive services; discovery was partial, so more may exist.Medium
Why it matters
Names containing admin, development, staging, VPN, database, or monitoring terms may point attackers toward valuable systems. A name alone does not prove exposure, but it identifies a surface that should be reviewed.
What to do
Remove obsolete DNS names and protect non-public systems with strong authentication, MFA, network allowlists, or a VPN.
SPF protection levelThe terminal SPF policy is ~all.Medium
Why it matters
The final SPF rule tells receiving services how confidently they should reject unlisted senders. A permissive result allows more spoofed mail to appear legitimate than a hard fail (-all).
What to do
Confirm that every legitimate sender is included, then end the SPF record with -all.
Evidence and check scope
Leak evidenceMost recent observation:
Email addressRelated infected deviceInfection evidenceRecorded time
Discovered subdomains (1,202+)Subdomains of berkeley.edu, the registered domain of the assessed website www.crisisresponse.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
Home | Campus Mobile Crisis Response
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
https://crisisresponse.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.crisisresponse.berkeley.edu expose?
The assessment observed 3 public IPs and 2 open ports for www.crisisresponse.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,202+ 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.