VirusTotal
6 / 89 engine detections
Open report“Even geduld...”
6 / 89 engine detections
Open report2 det.
DBL_PHISH
no community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This domain, jtx.network, is identified as an active crypto drainer phishing infrastructure targeting cryptocurrency wallet users. Analysis indicates the site employs deceptive wallet connection prompts and transaction signing requests to siphon digital assets from victims. No direct brand impersonation is observed, but the domain mimics legitimate decentralized application interfaces to facilitate unauthorized fund transfers. The presence of a drainer kit is inferred from behavioral patterns and historical associations with similar malicious domains. Infrastructure analysis reveals the following technical indicators: the domain is flagged by 4 out of 95 security vendors on VirusTotal, indicating moderate detection but persistent risk. The domain was registered through an undisclosed registrar, resolving to IP address 104.21.81.193, a Cloudflare proxy endpoint. Creation date metadata is obfuscated, but passive DNS records suggest recent deployment. Google Safe Browsing (GSB) currently does not list the domain, though it appears on two independent security blocklists. Additional enforcement actions include active blocking by wallet security extensions and decentralized threat intelligence feeds. The domain remains operational and poses an elevated risk to users engaging with cryptocurrency platforms. Immediate response actions include revocation of the SSL certificate issued by Google Trust Services, though this has not yet been executed. Users are advised to treat all interactions with jtx.network as hostile and to verify wallet addresses through trusted sources before executing transactions. Remaining risk includes potential exposure to users unaware of the domain's malicious status, particularly those redirected from compromised advertising networks or social engineering campaigns. Continued monitoring is recommended to track infrastructure changes or shifts in detection coverage.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 019f4fbb-74af-7508-af9b-29b13caca003 |
|---|---|
| Final url | https://jtx.network/ |
| Status | 403 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://jtx.network/",
"from": "http://jtx.network/",
"status": 307
},
{
"to": "https://jtx.network/",
"from": "https://jtx.network/",
"status": 307
}
] |
| Ip | 188.114.96.3 |
| Contacted domains | [
"challenges.cloudflare.com"
] |
| Contacted IP addresses | [
"104.18.94.41",
"104.18.95.41",
"188.114.96.3"
] |
| Asns | [
"13335"
] |
| Linked domains | [
"www.cloudflare.com"
] |
| Document hash | 5cb52d9568a946061452cd42717dbbd141c391639a4646497e802498544338d9 |
| Script hashes | [
"bd27088532448179fc97293279feae00a8af5a5efbf02887deca15ec8a50ee81"
] |
| Globals | [
"_cf_chl_opt",
"runProgram",
"czFZd5",
"apbV4",
"TSAKU6",
"wQKMU5",
"hUNx6",
"txpf0",
"ojUR0",
"VncEJ9",
"gkUE2",
"UEUx9",
"TUae0",
"XisUD9",
"abhiZ0",
"MEDWe9",
"keyVo9",
"hUgL3",
"sKSiM6",
"bpprn3",
"PBVv8",
"Jdvdh0",
"OqFnG7",
"uwBP8",
"XWzH5",
"xrCq3",
"FmBU0",
"RHlfd5",
"JoZi2",
"angular",
"IfhVE8",
"xeVw8",
"AFEhr3",
"turnstile",
"gUYw8",
"QUycY7",
"vioO3",
"yTEB5"
] |
| Tls | {
"san": [
"jtx.network",
"*.jtx.network"
],
"cipher": "AES_128_GCM",
"issuer": "WE1",
"subject": "jtx.network",
"protocol": "QUIC",
"valid_to": "2026-09-27T16:44:14Z",
"valid_from": "2026-06-29T15:46:45Z"
} |
| Domain age days | 11 |
| Apex age days | 11 |
| Tls age days | 11 |
| Tls valid days | 90 |
| Requests | 9 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 80,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "cloudflare",
"content-type": "text/html; charset=UTF-8",
"content-security-policy": "default-src 'none'; script-src 'nonce-pq2IHHVCReoaCi26ruzSid' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.clou",
"x-frame-options": "SAMEORIGIN",
"x-content-type-options": "nosniff",
"referrer-policy": "same-origin",
"permissions-policy": "accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),s",
"cross-origin-opener-policy": "same-origin",
"cross-origin-resource-policy": "same-origin",
"cross-origin-embedder-policy": "require-corp"
} |
Observed: · Retrieved:
| Uuid | 94cd0938-f53c-4c51-9617-47822902fcde |
|---|---|
| Final url | https://jtx.network/ |
| Status | 403 |
| History | [
{
"url": "https://jtx.network/",
"status": 403
}
] |
| DOM structure hash | bf4551addbc55ebc01453032e5d1edbf23101b5f6de1cf9a686b546d7fef9f49 |
| Document hash | f2a803585665f3224021a872d07261f2a811a58cd252e135da10949979e050d9 |
| Domain risks | [
"Newly Seen Domains",
"Security Risks"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "jtx.network",
"type": "A",
"value": "188.114.96.0"
},
{
"name": "jtx.network",
"type": "A",
"value": "188.114.97.0"
},
{
"name": "jtx.network",
"type": "AAAA",
"value": "2a06:98c1:3121::"
},
{
"name": "jtx.network",
"type": "AAAA",
"value": "2a06:98c1:3120::"
}
] |
| Dnssec valid | false |
| Ip | 188.114.96.0 |
Last checked
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.
Edge-IP reputation is not attributed to this domain.
elle.ns.cloudflare.comgerald.ns.cloudflare.comLocation describes the IP network.
44e84272b02ac6ec1ad87c4a13210d4dafb86a666f545a63847305ce25242792jtx.network*.jtx.networkSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of jtx.network · checked Jul 11, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unavailable→Reachable
Reachable→Unavailable
6/89 engine detections
View source⚠️ ESCALATION #2 (621h active): Phishing - jtx[.]network
Page captured
View sourceNo threat flag
View source⚠️ ESCALATION #1 (0h active): Phishing - jtx[.]network
jtx.network
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
jtx.network
PD-1783749018-jtx.network Recipient: abuse@dynadot.com 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
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
jtx.network)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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
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.