Security engines reporting a detection: 16. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
The domain s.team-um.com was observed on the OpenPhish blocklist as of 2026-10-09, providing a dated external listing for its security context. On that date, a PageSpeed performance score of 100 was also recorded for the domain, reflecting a technical measurement distinct from security findings.
Recorded Evidence
On 2026-10-09, s.team-um.com was listed by OpenPhish as an external blocklist entry. VirusTotal checked the domain on the same date, recording 16 detections out of 92 total scanners. An internal listing was also present in PhishDestroy, and a PageSpeed performance score of 100 was documented on 2026-10-09.
Interpretation
The VirusTotal record contains detection results from multiple security scanners, offering a quantitative view of how s.team-um.com was evaluated by that source. OpenPhish provides a dated external blocklist entry, while PhishDestroy adds an internal listing, each contributing a different type of observation. These records together describe the domain’s status in several security intelligence sources as of their respective check dates.
Recommended Actions
For s.team-um.com, preserve the VirusTotal, OpenPhish, and PhishDestroy records for ongoing reference and future comparison. Retain the PageSpeed performance measurement as part of the technical profile. Use these dated entries to inform future monitoring and to track any changes in blocklist or detection status.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Last analyzed Previous stored snapshot: 16 detections
BitDefender
Chong Lua Dao
CRDF
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Kaspersky
Lionic
MalwareURL
SOCRadar
Sophos
URLQuery
VIPRE
Webroot
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of s.team-um.com· checked Oct 9, 2026
100
Good
Performance
FCP
0.78s
First Contentful Paint
LCP
0.78s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.78s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-10-09 17:23:12 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 188.114.97.1.
Threat Response Pipeline
Discovery
Analysis
Monitoring
7 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
s.team-um.com detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
4 evidence signal groups linked0 reports recordedUnverified
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · s.team-um.com
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(US)
