Opening the security report for www.ombuds.upenn.edu
www.ombuds.upenn.edu
Loading the security report for www.ombuds.upenn.edu
www.ombuds.upenn.edu
Is www.ombuds.upenn.edu Safe? Security Score 59/100 | CyStack
www.ombuds.upenn.edu
Climate Investments | University of Pennsylvania
topics
Industry
Science and Education / Universities and Colleges
Origin
United States
Global rank
#5,053
Rank in United States
#1,264
Updated at
F59/100
Security level
Low
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.ombuds.upenn.edu” safe?
As of September 15, 2026 at 00:04, www.ombuds.upenn.edu has a security score of 59/100 (grade F: “Low”). CyStack’s automated assessment recorded 13 issues to review after completing 97.3% of applicable checks. The website owner should address “Certificate matches the website” first, then review the remaining items in order of impact.
Does www.ombuds.upenn.edu show known scam, phishing, or malware signals?
At assessment time, CyStack did not find www.ombuds.upenn.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 @upenn.edu, the registered domain of the assessed website www.ombuds.upenn.edu. A record is not counted merely because someone visited or signed in to the website.63 matching email exposure records
63Matching email exposure records
22Related 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.ombuds.upenn.edu?
A valid SSL certificate still does not prove that www.ombuds.upenn.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.ombuds.upenn.edu use HTTPS, and is its SSL certificate valid?
HTTPS on www.ombuds.upenn.edu presented a certificate that was invalid or failed verification. The operator should review its validity dates, domain names, and trust chain.
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.ombuds.upenn.edu.
Certificate matches the websiteThe certificate does not match the requested target.Critical
Why it matters
The certificate must list the exact hostname visitors requested in its Subject Alternative Names (SAN). A mismatch produces browser warnings because the certificate may belong to a different service.
What to do
Issue and deploy a certificate whose SAN list includes every public hostname served by this website address.
Diagnostic information
The available certificate evidence was not sufficient to conclude this certificate requirement.
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.
DMARC blocking policyThe effective DMARC policy is none and applies to 100% of messages.High
Why it matters
A policy of quarantine or reject tells receiving services to move suspicious mail to spam or refuse it. A monitoring-only policy (p=none) records the problem but does not ask receivers to stop spoofed mail.
What to do
After every legitimate sender passes DMARC, move gradually to quarantine and then reject, covering 100% of messages.
Leak evidenceMost recent observation:
Email addressRelated infected deviceInfection evidenceRecorded time
Email addressm*****@upenn.eduRelated infected deviceM*********************** (macOS 15.7.4 (24G517))United StatesIOC reference: IOC-F467A8CAFCInfection evidenceSHub StealerObserved application: Chrome_DefaultRecorded timeEmail addressm******@upenn.eduRelated infected deviceM*********************** (macOS 15.7.4 (24G517))United StatesIOC reference: IOC-F467A8CAFCInfection evidenceEmail addressm***@upenn.eduRelated infected deviceP* (Microsoft Windows 11 Pro 64-bit)United StatesIOC reference: IOC-4E39D3F946Infection evidenceEmail addressm*******@upenn.eduRelated infected deviceM*********** (Windows 11)United StatesIOC reference: IOC-EA4D441307Infection evidenceEmail addressn******@upenn.eduRelated infected deviceNo safely shareable device details are available for this record.FranceIOC reference: IOC-8C3E89DC78Infection evidenceEmail addressJ*****@upenn.eduRelated infected deviceNo safely shareable device details are available for this record.IOC reference: IOC-AC3FDC480EInfection evidenceStealCEmail addressG****************@upenn.eduRelated infected deviceNo safely shareable device details are available for this record.IOC reference: IOC-BC58A0657EInfection evidenceStealCEmail addressR**************@upenn.eduRelated infected deviceNo safely shareable device details are available for this record.IOC reference: IOC-BC58A0657EInfection evidenceStealCEmail addressm*****@upenn.eduRelated infected deviceNo safely shareable device details are available for this record.IOC reference: IOC-C4C808B96EInfection evidenceVidarEmail addressz***@upenn.eduRelated infected device(Windows 10 Home x64)IOC reference: IOC-D95460E9E4Infection evidenceAMOS Stealer
At most 10 recent redacted records are shown to protect sensitive information.
Data provided by
Discovered subdomains (808+)Subdomains of upenn.edu, the registered domain of the assessed website www.ombuds.upenn.edu. Sensitive-looking names are shown first; individual subdomains have not been separately security-tested.Partial
Public web contextThe website title, description, industry and popularity.Website rankings and industry category are based on data from Similarweb
Page title
Climate Investments | University of Pennsylvania
Website category
Science and Education / Universities and Colleges
Description
topics
Global rank
#5,053
Rank in United States
#1,264
Rank in industry
#26
Final URL
https://www.ombuds.upenn.edu/
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 @upenn.edu email addresses appeared in exposed data or information-stealer (infostealer) logs?
There are currently 63 exposed email records matching the upenn.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.ombuds.upenn.edu expose?
The assessment observed 3 public IPs and 2 open ports for www.ombuds.upenn.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 upenn.edu have been discovered?
The assessment observed 808+ public subdomains of upenn.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.