On 24 July 2026 the domain www.trc20support.buzz was observed hosting a page with the title “Trust Wallet”. The page title directly references the legitimate Trust Wallet brand, and the domain is flagged as a brand‑impersonation infrastructure. The domain was registered on 21 February 2026 through OwnRegistrar, Inc., and the authoritative nameservers are ns1.dvgroup.co.in and ns2.dvgroup.co.in. DNS resolution points to the IPv4 address 194.61.31.103, which belongs to AS141995 (Contabo Asia Private Limited) and is geolocated in India. An HTTPS service is presented using a Let’s Encrypt certificate issued to “YE2”, confirming that TLS is active and the server returns HTTP status code 200 for the root request.
Reputation checks show a Gridinsoft trust score of 0 / 100 and the domain appears on one security blocklist. PhishDestroy has already listed the host as blocked. VirusTotal analysis reports that three of ninety‑five scanners flagged the site, indicating partial detection by anti‑malware engines. The observed scam type is “Crypto Scam”, consistent with the Trust Wallet impersonation claim. From the available evidence, the infrastructure is actively serving content that is likely intended to lure Trust Wallet users into disclosing credentials or performing unauthorized cryptocurrency transactions.
No additional samples of the page content, JavaScript, or credential‑capture mechanisms have been publicly released, so the exact attack flow remains uncertain. Defenders should add www.trc20support.buzz to URL filtering and endpoint allow‑list exclusions, block the associated IP address 194.61.31.103, and monitor DNS queries for the dvgroup.co.in name servers. Further analysis of the TLS certificate and any network traffic to the host is recommended to capture potential payloads. Organizations using Trust Wallet should issue user awareness advisories warning against visiting URLs that contain “trust” or “wallet” without confirming the official domain.
Extracted from stored page analysis
Observed indicators
1 wallet · 0 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-52034.invalid', port=80): Max retries exceeded with url: / (Caused by N
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedJan 24, 2026
DOM Analysisanalyzed Mar 24, 2026score 71/1001 brand signal
IoC Extractionscanned Jul 29, 20261 wallet · 0 Telegram IoC
Submitted URLhttps://www.trc20support.buzz/
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
194.61.31.103
Network ASN
AS141995
Organization
Contabo Asia Private Limited
Observed location
Mumbai, IN
Server header
nginx
Nameservers 2
ns1.dvgroup.co.in
ns2.dvgroup.co.in
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YE2
Valid from
2026-07-03 02:01:21
Valid until
2026-10-01 02:01:20
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-07-09 01:01:11 UTC
Collection source
PhishDestroy collector
Certificate fingerprint3fa1b9ed89926957a871315878d31e9385fc8586fe23234871b891b52e8c6422Certificate names · 1 SANs
trc20support.buzz
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:12:28 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-08-11 22:44:10 UTC
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.
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
duplicate-disabled-52034.invalid detected and queued for full analysis
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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 7, 2026
Time to First Unavailability
699 hours elapsed from detection to the first unavailable observation.
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+
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.
4 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
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 →
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
(US)
