Opening the security report for www.eyecare.berkeley.edu
www.eyecare.berkeley.edu
Loading the security report for www.eyecare.berkeley.edu
www.eyecare.berkeley.edu
Is www.eyecare.berkeley.edu Safe? Security Assessment | CyStack
www.eyecare.berkeley.edu
Free Speech FAQ - University of California, Berkeley
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
U59/100
Security level
UnratedProvisional
Data confidence
Low
Scope checked
56.8%
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.eyecare.berkeley.edu” safe?
As of September 8, 2026 at 23:28, www.eyecare.berkeley.edu has a security score of 59/100 (grade U: “Unrated”), but this result is provisional because some required evidence is incomplete. CyStack’s automated assessment recorded 10 issues to review after completing 56.8% of applicable checks. The website owner should address “HTTPS/TLS endpoint reachability” first, then review the remaining items in order of impact.
Does www.eyecare.berkeley.edu show known scam, phishing, or malware signals?
At assessment time, CyStack did not find www.eyecare.berkeley.edu or related infrastructure on any scam, phishing, or malware warning list after checking 3 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.eyecare.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.eyecare.berkeley.edu?
A valid SSL certificate still does not prove that www.eyecare.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.eyecare.berkeley.edu use HTTPS, and is its SSL certificate valid?
HTTPS on www.eyecare.berkeley.edu could not be reached during this assessment, so its SSL certificate and transport encryption could not be evaluated.
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.eyecare.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.eyecare.berkeley.edu
Resolved IPs tested:
34.102.161.251
IPs with conclusive connection failure:
34.102.161.251
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.
Database or cache exposed to the InternetA confirmed public datastore service was found: 34.102.161.251:1433 (mssql), 34.102.161.251:1521 (oracle), 34.102.161.251:2181 (zookeeper), 34.102.161.251:3306 (mysql), 34.102.161.251:5432 (postgresql), 34.102.161.251:5984 (couchdb), 34.102.161.251:6379 (redis), 34.102.161.251:7687 (neo4j), 34.102.161.251:9042 (cassandra), 34.102.161.251:9200 (elasticsearch), 34.102.161.251:11211 (memcached), 34.102.161.251:27017 (mongodb).High
Why it matters
Databases and caches often contain sensitive information and are normally used only by internal applications. Direct Internet access makes password attacks and configuration mistakes much more likely to become a data breach.
Public management service exposureA likely public management service should be reviewed: 34.102.161.251:22 (ssh), 34.102.161.251:1080 (socks), 34.102.161.251:2375 (docker), 34.102.161.251:2376 (docker-tls), 34.102.161.251:3389 (rdp), 34.102.161.251:5601 (kibana), 34.102.161.251:5900 (vnc), 34.102.161.251:6443 (kubernetes-api), 34.102.161.251:7001 (weblogic), 34.102.161.251:8500 (consul), 34.102.161.251:8888 (http-alt), 34.102.161.251:9090 (prometheus), 34.102.161.251:10000 (webmin), 34.102.161.251:10250 (kubelet), 34.102.161.251:10255 (kubelet-readonly), 34.102.161.251:15672 (rabbitmq-management).High
Why it matters
Leak evidenceMost recent observation:
Email addressRelated infected deviceInfection evidenceRecorded time
At most 10 recent redacted records are shown to protect sensitive information.
Data provided by
Discovered subdomains (1,030+)Subdomains of berkeley.edu, the registered domain of the assessed website www.eyecare.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.Website rankings and industry category are based on data from Similarweb
Page title
Free Speech FAQ - University of California, Berkeley
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
–
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.
Have @berkeley.edu email addresses appeared in exposed data or information-stealer (infostealer) logs?
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.eyecare.berkeley.edu expose?
The assessment observed 1 public IPs and 58 open ports for www.eyecare.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,030+ 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.
Remote administration services such as RDP, VNC, Docker, Kubernetes, and management consoles are high-value targets. Public exposure allows anyone on the Internet to attempt passwords or exploit an unpatched service.
What to do
Remove direct Internet access and require a VPN, a hardened access gateway, or trusted source networks; also use MFA where supported.
Evidence and check scope
Complete:
Yes
Ports checked:
21, 22, 23, 25, 53, 80, 110, 111, 139, 143… and 48 more
Industry
Updated at 
United States
