en
Give to Berkeley
Support UC Berkeley. Start here.
IndustryOriginGlobal rankRank in United States
Updated at 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.
As of September 9, 2026 at 12:12, www.give.berkeley.edu has a security score of 93.6/100 (grade A – “Excellent”). CyStack’s automated assessment recorded 7 issues to review after completing 89.3% of applicable checks. The website owner should address “Allowed browser content (CSP)” first, then review the remaining items in order of impact.
At assessment time, CyStack did not find www.give.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.
Check whether the website uses a secure connection and whether its HTTPS certificate remains valid.
Frequently asked questions
A valid SSL certificate still does not prove that www.give.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.
www.give.berkeley.edu used a valid SSL certificate at assessment time, valid until February 24, 2027. This status may change when the certificate expires or the server configuration changes.
Review HTTPS and certificateData sources
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.
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the enterprise.
These 3 failed checks or warnings have the greatest impact on the result for www.give.berkeley.edu.
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.
Evidence and check scope
References
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.
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
Identify website protection and check whether public IPs appear on warning lists.
Cloudflare| Hosting or network provider | DroneBL | Mailspike | PSBL | SpamCop | blocklist.de | Spamhaus |
|---|---|---|---|---|---|---|
| 104.20.38.90 | Not listed | Not listed | Not listed | Not listed | Not listed | Unavailable |
| 172.66.145.184 | Not listed |
Check domain and email settings that help prevent brand impersonation.
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.
Review exposed email recordsThe assessment identified 46 technologies on www.give.berkeley.edu, including 1 with a version, but CVE matching did not complete for every version. An empty result should not be treated as proof that no vulnerability exists.
Review technologies and CVEsThe assessment observed 4 public IPs and 8 open ports for www.give.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.
Review IPs and open portsThe assessment observed 1,203+ 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.
Review discovered subdomainsDiagnostic information
Subdomain discovery did not complete, so the current list may be incomplete.
Evidence and check scope
References
| Not listed |
| Not listed |
| Not listed |
| Not listed |
| Unavailable |
Recently completed assessments, prioritizing websites with a similar sector, country or security grade for easier comparison.
United States
