Opening the security report for www.future.ucdavis.edu
www.future.ucdavis.edu
Loading the security report for www.future.ucdavis.edu
www.future.ucdavis.edu
Is www.future.ucdavis.edu Safe? Security Assessment | CyStack
www.future.ucdavis.edu
What to Know About Processed and Ultra-Processed Food
Scientists explain the difference between whole, processed and ultra-processed foods. Learn how they could affect our health and how the food industry can improve.
Industry
Science and Education / Universities and Colleges
Origin
United States
Global rank
#6,042
Rank in United States
#1,372
Updated at
U59/100
Security level
UnratedProvisional
Data confidence
Low
Scope checked
64%
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.future.ucdavis.edu” safe?
As of September 21, 2026 at 19:02, www.future.ucdavis.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 6 issues to review after completing 64% of applicable checks. The website owner should address “Certificate matches the website” first, then review the remaining items in order of impact.
Does www.future.ucdavis.edu show known scam, phishing, or malware signals?
At assessment time, CyStack did not find www.future.ucdavis.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 @ucdavis.edu, the registered domain of the assessed website www.future.ucdavis.edu. A record is not counted merely because someone visited or signed in to the website.1,352 matching email exposure records
1,352Matching email exposure records
151Related 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.future.ucdavis.edu?
A valid SSL certificate still does not prove that www.future.ucdavis.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.future.ucdavis.edu use HTTPS, and is its SSL certificate valid?
HTTPS on www.future.ucdavis.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.future.ucdavis.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.
Evidence and check scope
Assessed domain:
www.future.ucdavis.edu
Certificate domain names:
health.ucdavis.edu, believe.ucdavis.edu, caare.ucdavis.edu, cancer.ucdavis.edu, cancerinformatics.ucdavis.edu, children.ucdavis.edu, choosehealth.ucdavis.edu, elijasalud.ucdavis.edu, fetalcare.ucdavis.edu, health2.ucdavis.edu… and 20 more
Host requested:
www.future.ucdavis.edu
Resolved IPs tested:
152.79.121.82
IP that returned the observed result:
152.79.121.82
DMARC blocking policyThe effective DMARC policy is quarantine 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.
Potentially sensitive subdomainsCyStack confirmed at least 625 active DNS subdomains of ucdavis.edu. 46 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
Leak evidenceMost recent observation:
Email addressRelated infected deviceInfection evidenceRecorded time
Email addressa********@ucdavis.eduRelated infected deviceNo safely shareable device details are available for this record.IOC reference: IOC-6E372F70F1Infection evidenceMalware family not identifiedObserved application: Chrome, Profile: 0Recorded timeEmail addressb*****@ucdavis.eduRelated infected deviceNo safely shareable device details are available for this record.IOC reference: IOC-548EB5F332Infection evidenceMalware family not identifiedEmail addressj**********@ucdavis.eduRelated infected deviceD************** (Windows 11 Home (10.0.26200) x64)United StatesIOC reference: IOC-7945B9EC7FInfection evidenceEmail addresse*********@ucdavis.eduRelated infected deviceD************** (Windows 11 Home (10.0.26200) x64)United StatesIOC reference: IOC-7945B9EC7FInfection evidenceEmail addressj***************@ucdavis.eduRelated infected deviceD************** (Windows 11 Home (10.0.26200) x64)United StatesIOC reference: IOC-7945B9EC7FInfection evidence
At most 10 recent redacted records are shown to protect sensitive information.
Data provided by
Discovered subdomains (625+)Subdomains of ucdavis.edu, the registered domain of the assessed website www.future.ucdavis.edu. Sensitive-looking names are shown first; individual subdomains have not been separately security-tested.Partial
Results were bounded and may be truncated.
admin.amdhome-test5.ucdavis.eduSensitive-lookingAdmin system
admin.are.ucdavis.eduSensitive-lookingAdmin system
admin.lecturecapture.ucdavis.eduSensitive-lookingAdmin system
admin.physics.ucdavis.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
What to Know About Processed and Ultra-Processed Food
Website category
Science and Education / Universities and Colleges
Description
Scientists explain the difference between whole, processed and ultra-processed foods. Learn how they could affect our health and how the food industry can improve.
Global rank
#6,042
Rank in United States
#1,372
Rank in industry
#33
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 @ucdavis.edu email addresses appeared in exposed data or information-stealer (infostealer) logs?
There are currently 1,352 exposed email records matching the ucdavis.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.future.ucdavis.edu expose?
The assessment observed 1 public IPs and 2 open ports for www.future.ucdavis.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 ucdavis.edu have been discovered?
The assessment observed 625+ public subdomains of ucdavis.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.
Industry
Updated at 
United States
