On 2026-10-01, s.team-s.my returned an HTTP status 200 according to a recorded check, indicating a successful server response at that time. Additionally, the domain appears in the PhishDestroy internal listing, which is a publisher-managed catalogue entry.
Recorded Evidence
A check on 2026-10-01 recorded s.team-s.my responding with HTTP status 200. VirusTotal, as of 2026-09-29, reported 13 detections out of 91 scanners for this domain. The domain was first observed on 2026-09-29, and an SSL scan on the same date identified Let's Encrypt / YR2 as the certificate issuer. The PhishDestroy internal listing was also noted for this domain.
Interpretation
The HTTP status 200 describes a single response recorded on 2026-10-01 and does not indicate ongoing availability. VirusTotal's detection and scanner results reflect only the scanner set and results as of 2026-09-29. The PhishDestroy internal listing records the domain in a publisher-managed catalogue, separate from external blocklists. The SSL scan and first observation provide additional context for the domain's technical setup and timeline.
Recommended Actions
Review the recorded evidence for s.team-s.my, including the HTTP check, VirusTotal result, and PhishDestroy listing, as separate records. Preserve the VirusTotal scanner results and HTTP response for future comparison. Retain the SSL scan and first observation as part of the domain's historical record. Conduct new checks for updated HTTP responses and scanner results before making further decisions.
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
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='s.team-s.my', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Registration (base domain)team-s.my · Created Sep 18, 2026 (25d · Very New!)—Expires Sep 18, 2027
Time to First Unavailability15 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 29, 2026
DOM Analysisanalyzed Oct 9, 2026score 93/1002 brand signals
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 22:08:50 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-29 04:58:31 UTC
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.
Threat Intel Cross-Reference · source references
ScamAdviserPublic lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
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.
Domain Status Transition2026-10-13 22:29:42 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-29 19:09:58 UTC
VirusTotal scanner detections updated from 12 to 13. Added scanner alerts: Criminal IP.
VirusTotal Detections Update2026-09-29 12:06:25 UTC
VirusTotal scanner detections updated from 11 to 12. Added scanner alerts: G-Data.
VirusTotal Detections Update2026-09-29 09:55:33 UTC
VirusTotal scanner detections updated from 5 to 11. Added scanner alerts: BitDefender, CRDF, ESET, Forcepoint ThreatSeeker, Gridinsoft, Sophos.
VirusTotal Detections Update2026-09-29 09:25:08 UTC
VirusTotal scanner detections updated from 3 to 5. Added scanner alerts: Fortinet, Webroot, Yandex Safebrowsing, alphaMountain.ai. Resolved alerts: CRDF, Gridinsoft.
VirusTotal Detections Update2026-09-29 06:49:42 UTC
VirusTotal scanner detections updated from 2 to 3. Added scanner alerts: Gridinsoft.
Threat First Observed2026-09-29 04:45:44 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 45.155.69.188.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
20 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Oct 14, 2026
Time to First Unavailability
353 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
5 evidence signal groups linked1 reports recordedContent unavailable
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-s.my
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.
Content matches4
Same favicon hash or the same page title as this host.
(US)
