Analysis of trustalabs-ai.tokenlive.website indicates a confirmed crypto scam domain with elevated risk, now offline as of July 25, 2026. The domain was registered on July 17, 2025, through NameCheap, Inc., and resolved to IP 209.74.67.109, hosted on AS22612 (Namecheap, Inc.) in Singapore. No SSL certificate was present, increasing susceptibility to interception.
The page title, 'Default Web Site Page,' suggests either misconfigured hosting or an attempt to evade detection by displaying minimal content. Six of 95 security vendors on VirusTotal flagged the domain, while PhishDestroy and one additional security blocklist have already blocked it. Gridinsoft assigned a trust score of 0/100, reinforcing its malicious classification.
The domain's infrastructure—Namecheap hosting and Namecheap nameservers (dns1.namecheaphosting.com, dns2.namecheaphosting.com)—aligns with patterns observed in low-effort scam operations. Defenders should treat this domain as compromised and prioritize blocking resolutions to 209.74.67.109, as well as monitoring for related subdomains or newly registered lookalike domains under the same registrar. Further investigation into associated wallet addresses or redirect chains is recommended, though no specific brand impersonation or phishing kit details are currently available in the observable evidence.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='trustalabs-ai.tokenlive.website', port=80): Max retries exceeded with url: / (Caused by Ne
For the registrable domain tokenlive.website behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:11:36 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-13 16:28:31 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-13 16:28:31 UTC → 2026-09-30 16:14:55 UTC · 2,615.77hmidpoint estimate ≈ 2026-08-07 04:21:43 UTC · precision very low · basis bounded
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: 4 detections
G-Data
Seclookup
SOCRadar
Sophos
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.
10 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.
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.
(US)
