Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 10. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
s.team-zm.com favicon

s.team-zm.com

In short

PhishDestroy records the s.team-zm.com capture showing a TBELink admin dashboard login form with username and password fields.

“TBELink — Admin Dashboard”

Review the evidence
Registrar
Hong Kong SAR ChinaDominet (HK)
Resolved IP
United Kingdom188.114.97.3CloudFLARENET-EU · CDN
Registered
Oct 27, 2026
First observed
Oct 31, 2026
PhishDestroy assessment Critical
90/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 10/92 Young domain: 4 days old
VirusTotal
10 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 3
Cloudflare Radar
Phishing
Page captures
9
open gallery
Domain age
4 days
registered 2026-10-27 according to WHOIS · source data differ
Oct 31, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy records the s.team-zm.com capture showing a TBELink admin dashboard login form with username and password fields.

Critical
Status
Last known active
VirusTotal
10 / 92
Hosting
United Kingdom188.114.97.3CloudFLARENET-EU · CDN
Registrar
Hong Kong SAR ChinaDominet (HK)
Registered
Oct 27, 2026
Page captures
9
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page at s.team-zm.com presents a centered login card branded "TBELink" with the Russian subtitle "Панель управления инвайт-системой" (invite-system management panel). Two input fields are labeled "Логин (admin)" and "Пароль", followed by a red "Войти в аккаунт" button, so the main interaction is submitting credentials to access an admin panel. The surrounding page is dark with faint blurred content behind the card.

The stored VirusTotal domain result reports 10 detections out of 92 engines. DNS8 reported "suspicious"; G-Data reported "phishing".

Source evidenceVirusTotal 10 / 92 8 sources

VirusTotal

10 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
51
Malicious
9
Suspicious
1
Undetected
31

Vendor labels

DNS8
suspicious
G-Data
phishing
Sophos
phishing
Webroot
malicious
SOCRadar
phishing
Gridinsoft
phishing
BitDefender
phishing
Criminal IP
phishing
Yandex Safebrowsing
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Registrar

Dominet (HK) Limited

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    104.21.46.218
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3036::ac43:8edf
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3034::6815:2eda
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.142.223

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.team-zm.com
  • team-zm.com
Issuer
Let's Encrypt / YE1
Serial
6550472ad9f2cc852554234588fe21a12de
SHA-256
92c12fe9c1cd7f98838014da6b62f647ee980e7f48713917ac7870f762adcf0a
Subject
team-zm.com
Valid until
Valid from

Registration record

Registrar
Dominet (HK) Limited
Registrar IANA ID
3775
Registrar URL
http://www.alibabacloud.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • marjory.ns.cloudflare.com
  • sullivan.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 51,
    "malicious": 9,
    "suspicious": 1,
    "undetected": 31
}
Vendor labels
{
    "DNS8": "suspicious",
    "G-Data": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "SOCRadar": "phishing",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "Criminal IP": "phishing",
    "Yandex Safebrowsing": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
Dominet (HK) Limited
Created
2026-10-27T22:50:53Z
Expires
2027-10-27T22:50:53Z
Updated
2026-10-27T22:50:54Z
First seen
2025-03-03T10:53:55Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.46.218"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3036::ac43:8edf"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3034::6815:2eda"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.142.223"
    }
]
Dns at
2026-10-31T16:51:02Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.team-zm.com",
        "team-zm.com"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "6550472ad9f2cc852554234588fe21a12de",
    "sha256": "92c12fe9c1cd7f98838014da6b62f647ee980e7f48713917ac7870f762adcf0a",
    "subject": "team-zm.com",
    "valid_to": "2027-01-25T21:54:23Z",
    "valid_from": "2026-10-27T21:54:24Z"
}
Registration record
{
    "registrar": "Dominet (HK) Limited",
    "registrar_iana_id": "3775",
    "registrar_url": "http://www.alibabacloud.com",
    "created": "2026-10-27T22:50:53Z",
    "updated": "2026-10-27T22:50:54Z",
    "expires": "2027-10-27T22:50:53Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "marjory.ns.cloudflare.com",
        "sullivan.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 9 malicious + 1 suspicious / 92 · 2026-10-31 16:50:47 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-31T16:50:47Z
fetched_at
2026-10-31T23:10:41Z
stats
{"timeout":0,"harmless":51,"malicious":9,"suspicious":1,"undetected":31}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Report ID

47245b16-3d16-42e1-b124-654cb3b030e8

Final URL

https://s.team-zm.com/admin

HTTP response

200

Redirect type

same-domain

Navigation history

  • URL
    https://s.team-zm.com/
    Status
    302
  • URL
    https://s.team-zm.com/admin
    Status
    200

DOM structure hash

7f281909df3a8b057ac79bff49165d67d884e010b28582f76989e127d6af551a

Document hash

b88cfdcfcd9f16d0597461d58276fe00f6576e5c46d06d5b84de0983a341fe25

Phishing classifier result

  • phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    s.team-zm.com
    Type
    A
    Value
    188.114.97.0
  • Name
    s.team-zm.com
    Type
    A
    Value
    188.114.96.0
  • Name
    s.team-zm.com
    Type
    AAAA
    Value
    2a06:98c1:3120::
  • Name
    s.team-zm.com
    Type
    AAAA
    Value
    2a06:98c1:3121::

DNSSEC valid

No

IP address

127.0.1.13

127.0.1.13 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
Dominet (HK) Limited
Registered
Updated
Expires
Nameservers
  • marjory.ns.cloudflare.com
  • sullivan.ns.cloudflare.com
Original source fields · JSON
Uuid
47245b16-3d16-42e1-b124-654cb3b030e8
Final url
https://s.team-zm.com/admin
Status
200
Redirected
same-domain
History
[
    {
        "url": "https://s.team-zm.com/",
        "status": 302
    },
    {
        "url": "https://s.team-zm.com/admin",
        "status": 200
    }
]
DOM structure hash
7f281909df3a8b057ac79bff49165d67d884e010b28582f76989e127d6af551a
Document hash
b88cfdcfcd9f16d0597461d58276fe00f6576e5c46d06d5b84de0983a341fe25
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "s.team-zm.com",
        "type": "A",
        "value": "188.114.97.0"
    },
    {
        "name": "s.team-zm.com",
        "type": "A",
        "value": "188.114.96.0"
    },
    {
        "name": "s.team-zm.com",
        "type": "AAAA",
        "value": "2a06:98c1:3120::"
    },
    {
        "name": "s.team-zm.com",
        "type": "AAAA",
        "value": "2a06:98c1:3121::"
    }
]
Dnssec valid
false
Ip
127.0.1.13

127.0.1.13 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "Dominet (HK) Limited",
    "created": "2026-10-27T22:50:53Z",
    "updated": "2026-10-27T22:50:54Z",
    "expires": "2027-10-27T22:50:53Z",
    "nameservers": [
        "marjory.ns.cloudflare.com",
        "sullivan.ns.cloudflare.com"
    ]
}

URLScan

Malicious · engine verdict · score 3

SHA-256 daa5c18e3ae2b84af63af26e76e7192bfa8d6bb21b73db3a30849f2e83c41905

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a1941a-6296-715a-8aed-2bd982ad9343

Final URL

https://s.team-zm.com/lp/kma-mhc/foofvybf/

HTTP response

200

Redirect type

same-domain

Redirects

  • To
    https://s.team-zm.com/lp/kma-mhc/foofvybf
    From
    http://s.team-zm.com/lp/kma-mhc/foofvybf
    Status
    307
  • To
    https://s.team-zm.com/lp/kma-mhc/foofvybf/
    From
    https://s.team-zm.com/lp/kma-mhc/foofvybf
    Status
    301

IP address

104.21.46.218

Contacted domains

  • community.steamstatic.com
  • community.cloudflare.steamstatic.com
  • static.cloudflareinsights.com

Contacted IP addresses

  • 104.16.80.73
  • 199.232.215.52
  • 23.62.230.132
  • 104.21.46.218

Autonomous systems (ASN)

  • 13335
  • 54113
  • 20940

Server countries

  • US

Linked domains

  • steamcommunity.com
  • www.geonames.org

Document hash

daa5c18e3ae2b84af63af26e76e7192bfa8d6bb21b73db3a30849f2e83c41905

JavaScript globals

  • __cfBeacon

TLS session and certificate

Subject alternative names
  • *.team-zm.com
  • team-zm.com
Cipher
AES_128_GCM
Issuer
YE1
Subject
team-zm.com
Protocol
QUIC
Valid until
Valid from

Domain age, days

607

Differs from the registration date in WHOIS (2026-10-27), which gives 3 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Registered domain age, days

607

Differs from the registration date in WHOIS (2026-10-27), which gives 3 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Certificate age, days

4

Certificate validity, days

89

Page requests

6

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
3
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
cloudflare
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
01a1941a-6296-715a-8aed-2bd982ad9343
Final url
https://s.team-zm.com/lp/kma-mhc/foofvybf/
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://s.team-zm.com/lp/kma-mhc/foofvybf",
        "from": "http://s.team-zm.com/lp/kma-mhc/foofvybf",
        "status": 307
    },
    {
        "to": "https://s.team-zm.com/lp/kma-mhc/foofvybf/",
        "from": "https://s.team-zm.com/lp/kma-mhc/foofvybf",
        "status": 301
    }
]
Ip
104.21.46.218
Contacted domains
[
    "community.steamstatic.com",
    "community.cloudflare.steamstatic.com",
    "static.cloudflareinsights.com"
]
Contacted IP addresses
[
    "104.16.80.73",
    "199.232.215.52",
    "23.62.230.132",
    "104.21.46.218"
]
Asns
[
    "13335",
    "54113",
    "20940"
]
Countries
[
    "US"
]
Linked domains
[
    "steamcommunity.com",
    "www.geonames.org"
]
Document hash
daa5c18e3ae2b84af63af26e76e7192bfa8d6bb21b73db3a30849f2e83c41905
Globals
[
    "__cfBeacon"
]
Tls
{
    "san": [
        "*.team-zm.com",
        "team-zm.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "team-zm.com",
    "protocol": "QUIC",
    "valid_to": "2027-01-25T21:54:23Z",
    "valid_from": "2026-10-27T21:54:24Z"
}
Domain age days
607

Differs from the registration date in WHOIS (2026-10-27), which gives 3 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Apex age days
607

Differs from the registration date in WHOIS (2026-10-27), which gives 3 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Tls age days
4
Tls valid days
89
Requests
6
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 3,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8"
}
Separate monitor record · date not recorded

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a1941a-6296-715a-8aed-2bd982ad9343
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

10 / 100 · heuristic score · 1 brand reference · 0 classifications

Open report
Separate monitor score · 10 / 100 · 2026-10-31T23:18:08Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
10
analyzed_at
2026-10-31T23:18:08Z
source_timestamp
2026-11-01 00:18:08
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
s.team-zm.com — TBELink Admin Dashboard Login
ai_description
PhishDestroy records the s.team-zm.com capture showing a TBELink admin dashboard login form with username and password fields.
ai_summary
The captured page at s.team-zm.com presents a centered login card branded "TBELink" with the Russian subtitle "Панель управления инвайт-системой" (invite-system management panel). Two input fields are labeled "Логин (admin)" and "Пароль", followed by a red "Войти в аккаунт" button, so the main interaction is submitting credentials to access an admin panel. The surrounding page is dark with faint blurred content behind the card. The stored VirusTotal domain result reports 10 detections out of 92 engines. DNS8 reported "suspicious"; G-Data reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 00:14:32
revision
cfef5ab4c00354c4f0abf3ed2eb557c12b7776f222aed48697576bdda3f3882e
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 24 fields

CAA records

Domain
s.team-zm.com

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
18038

Page title and metadata

Page title
TBELink — Admin Dashboard

Trackers

Requests
119
Observed services
  • Name
    Pinterest
    Company
    Pinterest
    Country
    US
    Category
    Social Media
    Requests
    1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
302
Request timings, ms
DNS
39
TLS
148
Waiting
70
Connection
33
Download
0
Response time, ms
290

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
78205
CO₂, grams
0.0029
Cleaner than, %
27

DNS servers

Nameservers
  • IP address
    108.162.195.161
    Host
    sullivan.ns.cloudflare.com
  • IP address
    108.162.192.193
    Host
    marjory.ns.cloudflare.com
DNS zone
team-zm.com

Cookies

Cookies
  • Name
    timezoneOffset

Location

IP address
2a06:98c1:3120::3
ASN
13335
Organization
CloudFLARENET-EU
City
London
Country
GB

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
team-zm.com

DNS records

A
  • 188.114.96.3
  • 188.114.97.3
AAAA
  • 2a06:98c1:3120::3
  • 2a06:98c1:3121::3

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2a06:98c1:3120::3
IP version
6

Redirects

Redirect chain
  • https://s.team-zm.com
  • /admin
Count
1

Page links

External link addresses
  • https://t.me/BPdomains_bot
  • https://discord.gg/tbeteam
  • https://api.bp.domains/docs
External links
3
Internal links
4

Registration record

Registrar
Dominet (HK) Limited
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • marjory.ns.cloudflare.com
  • sullivan.ns.cloudflare.com

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=utf-8
Original source fields · JSON
Caa records
{
    "domain": "s.team-zm.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2025-03-03T17:25:34Z",
    "first": "2025-03-03T17:25:34Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 18038
}
Page title and metadata
{
    "title": "TBELink — Admin Dashboard"
}
Trackers
{
    "requests": 119,
    "trackers": [
        {
            "name": "Pinterest",
            "company": "Pinterest",
            "country": "US",
            "category": "Social Media",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 302,
    "timings": {
        "dns": 39,
        "tls": 148,
        "wait": 70,
        "connect": 33,
        "download": 0
    },
    "response_ms": 290
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 78205,
    "co2_grams": 0.0029,
    "cleaner_than": 27
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.195.161",
            "host": "sullivan.ns.cloudflare.com"
        },
        {
            "ip": "108.162.192.193",
            "host": "marjory.ns.cloudflare.com"
        }
    ],
    "zone": "team-zm.com"
}
Cookies
{
    "cookies": [
        {
            "name": "timezoneOffset"
        }
    ]
}
Location
{
    "ip": "2a06:98c1:3120::3",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "team-zm.com"
}
DNS records
{
    "A": [
        "188.114.96.3",
        "188.114.97.3"
    ],
    "AAAA": [
        "2a06:98c1:3120::3",
        "2a06:98c1:3121::3"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2a06:98c1:3120::3",
    "family": 6
}
Redirects
{
    "chain": [
        "https://s.team-zm.com",
        "/admin"
    ],
    "count": 1
}
Page links
{
    "external": [
        "https://t.me/BPdomains_bot",
        "https://discord.gg/tbeteam",
        "https://api.bp.domains/docs"
    ],
    "external_count": 3,
    "internal_count": 4
}
Registration record
{
    "registrar": "Dominet (HK) Limited",
    "created": "2026-10-27T22:50:53Z",
    "updated": "2026-10-27T22:50:54Z",
    "expires": "2027-10-27T22:50:53Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "marjory.ns.cloudflare.com",
        "sullivan.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=utf-8"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Security threats Phishing
View full Cloudflare Radar report

Questions about s.team-zm.com

Is s.team-zm.com legit?

PhishDestroy records the s.team-zm.com capture showing a TBELink admin dashboard login form with username and password fields.

Is s.team-zm.com safe to connect a wallet?

This report does not record which wallet requests s.team-zm.com makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used s.team-zm.com?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 9 captures

Cloudflare Radar 1 / 9 Used in the analysis Source file SHA-256: be40351fa60cd71a6d58c8495607f0e53cc34797b00168f17841fb055c43bb23 SHA-256 of the prepared copy given to the model: 999dd22455d483e7cc9cd8a5f797b4feb9b4103b3e0cc935feba136e35f5a979
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://s.team-zm.com/admin
Position1 / 9
Open capture Source Report Wayback Download
All capture links and hashes (9)

Domain details

Domain
IP Context United Kingdom188.114.97.3 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Dominet (HK) HK(HK)
Abuse contactdomainabuse@service.aliyun.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for team-zm.com →
Registration (base domain)team-zm.com · Created Oct 27, 2026 (4d · Brand New!) — Expires Oct 27, 2027
WHOIS statusclientTransferProhibited
HTTP Status302 Found (Temporary)
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Nov 1, 2026score 10/1001 brand signal
Submitted URLhttp://s.team-zm.com/lp/kma-mhc/foofvybf
Favicon Hash
Observed page title
TBELink — Admin Dashboard
Automated brand references
Valve
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 85 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United Kingdom188.114.97.3
Network ASN
AS13335
Organization
CloudFLARENET-EU
Observed location
United KingdomLondon, GB
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • marjory.ns.cloudflare.com
  • sullivan.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-27 21:54:24
Valid until
2027-01-25 21:54:23
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-31 23:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint92c12fe9c1cd7f98838014da6b62f647ee980e7f48713917ac7870f762adcf0a
Certificate names · 1 SAN
  • team-zm.com

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 188.114.97.3rapiddns.io
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.s.team-zm.comDomain record
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

10 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
Criminal IP
BitDefender
DNS8
Forcepoint ThreatSeeker
G-Data
Gridinsoft
SOCRadar
Sophos
Webroot
Yandex Safebrowsing

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of s.team-zm.com · checked Nov 1, 2026

99
Good
Performance
FCP
0.96 s
First Contentful Paint
LCP
0.96 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
3.48 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://s.team-zm.com/lp/kma-mhc/foofvybf
Final URL: https://s.team-zm.com/lp/kma-mhc/foofvybf/
Sign In
Response
HTTP 200
HTML body
83.2 KB
Compressed
19.1 KB
Links
0 internal · 0 external
Detected technologies
jquerycloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Server: cloudflare
Cache-Control: no-cache, no-store, must-revalidate
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Open Graph title: Sign In
Twitter card: summary
Saved response-header values · 14
alt-svc
h3=":443"; ma=86400
Cache-Control
no-cache, no-store, must-revalidate
cf-cache-status
DYNAMIC
CF-RAY
a53624a9e9dc97b9-YYZ
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sat, 31 Oct 2026 22:37:15 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=6D2dslyNhj9R1sqUgIv343uHVBVvbxuUHa0ZUpfeTi9CHiJWKpHlukBoyC6MobgTVxlIPcS8w9RCzMO1tQrNFayJBEsF80F6mI09D4OqmOElI1lVoVH%2FPfMFkT92TfzC"}]}
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
Vary
accept-encoding

Values retained by the collector; long values may be shortened during collection.

Archived
Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Captured network requests

Network requests: 6 SHA-256 hashes: 5 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-31 22:39 UTC.

Open this scan on URLScan 01a1941a-6296-715a-8aed-2bd982ad9343 ↗

Stored observation history1

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Domain monitor · First collection record

    Reachable

All retained availability observations2

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. http_observationunknown
    Observation source
    http_observation
    Cause
    legacy_alive_unverified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    15
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 23:36:40.000000
    Evidence SHA-256
    a2fad08ab6ce2730b636a107e973519f483f742a4e8f1834be59330a1f9d665e
    Evidence timestamp as recorded
    2026-10-31 23:36:40
  2. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 23:36:40.000000
    Evidence SHA-256
    cfe84f36f41b35c592df8e8838e94b90e8c46c5cf40f247a83234b19ed689b3e
    Evidence timestamp as recorded
    2026-10-31 23:36:40
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    false

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    s.team-zm.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Cloudflare Radar: Malicious · Automated brand label: Steam · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 3
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 10/92
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as Phishing, Security threats
  • Automated brand label: Steam
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

5 entries
  1. Cloudflare Radar

    Phishing

    View source
  2. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    s.team-zm.com

    View source
  4. URLScan

    Page captured

    View source
  5. VirusTotal

    10/92 engine detections

    View source
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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

s.team-zm.com

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 10 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch CF Radar Malicious WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including s.team-zm.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?
  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

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 →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/s.team-zm.com"
  title="PhishDestroy threat report for s.team-zm.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>