VirusTotal
3 / 91
“Experience Seamless DeFi on DeX1rp – Built on XRP Ledger”
The domain dexrp.network is a phishing site engaged in brand impersonation targeting Ledger, a cryptocurrency hardware wallet provider. It presents itself as a decentralized finance (DeFi) platform built on the XRP Ledger to deceive users into connecting wallets or entering sensitive information, posing an elevated risk of cryptocurrency theft. As of the latest verification, dexrp.network has been taken offline, though it previously operated as an active scam site.
Technical indicators confirm the malicious nature of dexrp.network. The domain was flagged by 2 of 95 security vendors on VirusTotal, including Fortinet and G-Data. It appears on two security blocklists, PhishDestroy and ScamSniffer, and was registered through OwnRegistrar, Inc. on February 21, 2026. The site resolved to the IP address 192.3.190.186, hosted by AS36352 (HostPapa) in the US, and used nameservers dns1.webproserver.com and dns2.webproserver.com. No SSL certificate was observed, and the page title read 'Experience Seamless DeFi on DeX1rp – Built on XRP Ledger'.
Users who interacted with dexrp.network should immediately revoke any token approvals granted to the site and transfer funds to a new, secure wallet. If credentials or recovery phrases were entered, users must change passwords, enable two-factor authentication (2FA) on all accounts, and monitor for unauthorized transactions. Report the phishing domain to platforms like Google Safe Browsing, PhishTank, or the impersonated brand’s security team (Ledger) to aid in takedown efforts and prevent further victimization.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='dexrp.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("
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.
dns2.webproserver.comLocation describes the IP network.
b330bacd7bf56a83366685d8d56dcdeec8917adaa6264e468d07289b69b0143d5759505117.cyou5gbet9.net644wrm.cc687859.cc837871.my9ero.probeqlean.comclaitor.comgaopingzxw.cngovacapitalassetalliance.biziukwvg.bidlatin.momleadsfoxcap.comlevans.commcglendinghub.bizmizalla.comnashville.onepatriots.inpressreleaseskool.inforunthiscitycancerfoundation.orgsayingprayers.orgsekabet-1396.onlinexyw868.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
12 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.
151 stored lookalike domains
Showing 100 of 151
Reported by 1 community member, first seen Aug 8, 2025
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