PhishDestroy identifies web3-trust.digital as an active crypto wallet phishing domain currently under investigation. The threat type is generic_phishing, targeting users with deceptive Web3-related lures to steal cryptocurrency wallet credentials or funds. The domain resolves to IP address 5.149.248.229 using a Let's Encrypt SSL certificate, which may be used to lend false legitimacy to phishing pages. At this time, VirusTotal shows 0 detections out of 95 scanners, indicating low detection coverage despite active phishing behavior.
This domain was flagged with seed 9dd205 and is currently active. Intelligence indicates it has no confirmed presence on major blocklists or domain reputation engines as of the latest scan. The domain uses a free Let's Encrypt certificate, commonly leveraged in phishing campaigns to avoid immediate browser warnings. The associated IP 5.149.248.229 has not been widely flagged, increasing the risk of delayed detection by automated systems. No registrar data or creation date was provided in the seed intelligence, limiting historical context for reputation analysis.
To mitigate risk, users should avoid interacting with web3-trust.digital or any site prompting for crypto wallet access, seed phrase entry, or private key disclosure. Always verify URLs manually and use hardware wallets or trusted interfaces for transactions. Security teams should monitor IP 5.149.248.229 and associated domains for newly emerging phishing infrastructure. Report this domain to your security provider or via PhishDestroy’s submission portal using seed 9dd205 to aid in ongoing threat intelligence gathering.
DOM Analysisanalyzed 2026年7月29日score 56/1004 brand signals
Submitted URLhttp://web3-trust.digital/
ケース ID
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:10:32 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-04-22 04:25:15 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-22 04:25:15 UTC → 2026-09-30 16:14:55 UTC · 3,875.83hmidpoint estimate ≈ 2026-07-11 22:20:05 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.
使用技術 · 1 identified
N
Nginx
Web serversReverse proxies
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Google PageSpeed Insights — mobile performance audit of web3-trust.digital· checked Apr 21, 2026
93
Good
Performance
FCP
2.59s
First Contentful Paint
LCP
2.59s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.59s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
3875.83
Estimate basis
Bounded by observations
Estimate precision
very_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='web3-trust.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
web3-trust.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.
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.
詐欺による金銭の返還を装った詐欺 — 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.
