Analysis of trustalabs.digital, registered on February 21 2026 through Web Commerce Communications Limited (WebNic.cc), shows that the domain resolves to 104.21.48.1, an address owned by Cloudflare, Inc. (AS13335) located in the United States. The site presented the page title 'Trusta.AI' and was classified as a wallet/seed phishing operation that impersonates the brand 'across'. VirusTotal recorded a single positive detection out of 93 scanning engines, indicating at least one vendor identified malicious behavior. The domain appears on two public blocklists, PhishDestroy and ScamSniffer, both of which have marked it as malicious and subsequently forced the site offline.
The SSL certificate is identified as 'WE1', but no further certificate details are available. Gridinsoft assigned a trust score of 0 out of 100, reflecting an extremely low confidence in legitimacy. No additional content analysis is available; the page content has not been captured, and the exact phishing payload or lure was not disclosed. The limited evidence suggests the infrastructure is typical of cloud‑based phishing campaigns that leverage reputable CDNs to hide origin.
Defenders should block DNS resolution to 104.21.48.1 for this host name, add trustalabs.digital to internal URL filtering and email security policies, and monitor for any future re‑registration attempts. Threat intel feeds should be updated to include the domain and its association with wallet/seed phishing targeting the 'across' brand. Because the site is currently offline, continuous observation is recommended to detect possible revival or migration to new domains.
DOM Analysisanalyzed 2026年3月24日score 20/10018 brand signals
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
For this gTLD, 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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-19 01:11:56 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-03 22:16:01 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-03 22:16:01 UTC → 2026-09-30 16:14:55 UTC · 641.98hmidpoint estimate ≈ 2026-09-17 07:15:28 UTC · precision 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: 2 detections
alphaMountain.ai
Gridinsoft
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
641.98
Estimate basis
Bounded by observations
Estimate precision
Low
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='trustalabs.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
trustalabs.digital
已保存的结果
无法访问
Stored observation history10
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
我应该立即采取什么措施？
紧急
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
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?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(MY)
