Public blocklists
2 external matches
DetailsInterpretation & limits
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
“web3-trustwallet.cfd”
Assessment based on the stored source evidence below. Review sources →
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
2 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
DBL_PHISH
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
checked — no detections recorded
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
2 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: suspicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored report
A preserved page image documents what the collector received; a capture is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
web3-trustwallet.cfd was first observed on 2026-10-15, with a PhishDestroy internal listing recorded on that date. The domain's registration through NameSilo, LLC is also documented as occurring on 2026-10-15.
The PhishDestroy internal listing for web3-trustwallet.cfd is dated 2026-10-15. OTX referenced the domain in two pulses on 2026-10-15. VirusTotal checked the domain on 2026-10-15, reporting 0 detections out of 92 scanners. The registration date is recorded as 2026-10-15 with NameSilo, LLC as the registrar.
PhishDestroy contains an internal record for web3-trustwallet.cfd, documenting its inclusion in their catalogue. VirusTotal provides a measurement of detections based on analysis by multiple security engines. OTX records the domain's appearance in two pulses, which are community-driven intelligence entries. These sources each capture a different aspect of the domain's technical and intelligence profile.
Preserve the PhishDestroy listing, VirusTotal scan results, and OTX pulse references for web3-trustwallet.cfd as baseline evidence. Compare future security intelligence records to these sources to monitor for any changes. Use the documented observation and registration dates as reference points for subsequent reviews.
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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.
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.
mx1.beget.compriority 10mx2.beget.compriority 20Location describes the IP network.
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://web3-trustwallet.cfd/Server: nginx-reuseport/1.21.1Content-Type: text/htmlX-Powered-By: PHP/5.6.40Content-Encoding: gzipkeep-alivegziptext/htmlThu, 15 Oct 2026 14:52:54 GMTtimeout=30nginx-reuseport/1.21.1chunkedAccept-EncodingPHP/5.6.40Values retained by the collector; long values may be shortened during collection.
Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.
/robots.txt
The scanner received HTTP 404 or 410 for this file.
/sitemap.xml
The scanner received HTTP 404 or 410 for this file.
/.well-known/security.txt
The scanner received HTTP 404 or 410 for this file.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Local archived 2026-10-15 14:52:56 UTC87.236.19.212.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown
stale_current_evidence
Unknown
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
104 stored lookalike domains
Showing 100 of 104
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive