Skip to security report
Domain security and threat intelligence
jtx.network favicon

jtx.network

“Even geduld...”

Registrar
Dynadot
Resolved IP
188.114.96.3
Registered
Jun 29, 2026
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
VirusTotal detections: 6/89 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 Scam type: Crypto Drainer
Jul 11, 2026 2 Reports Sent CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 6. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
URLQuery
detections
Page captures
open gallery
Domain age
Reports sent
view timeline
Source evidenceVirusTotal 6 / 89 7 sources

VirusTotal

6 / 89 engine detections

Open report

URLQuery

2 det.

Spamhaus DBL

DBL_PHISH

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Critical
VirusTotal
6 / 89
Page captures
3

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.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-07-11T05:52:03Z

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"
}
Cloudflare Radar · 2026-07-11T05:50:46Z

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
Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 3 captures

Observed page title
Even geduld...
TLS Certificate
Issued by Google Trust Services · stored validity ends in 78 days

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar Dynadot US(US)
Abuse contactabuse@dynadot.com
RegistrationCreated Jun 29, 2026 (114d) — Expires Jun 29, 2027
Time to First Unavailability 26 days
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.
Minimum notice count 2 is the number of stored outgoing report records for this domain. It does not by itself prove acknowledgement or action by a recipient.
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.
ICANN RAA §3.18 The history below lists stored escalation records and timestamps. It does not by itself establish receipt, acknowledgement, compliance, or enforcement by any recipient.
Technical detailsProvenance & timestamps
First DetectedJul 11, 2026
DOM Analysisanalyzed Jul 11, 2026score 90/100
Submitted URLhttp://jtx.network/
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

Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • elle.ns.cloudflare.com
  • gerald.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services
Valid from
2026-06-29 15:46:45
Valid until
2026-09-27 16:44:14
Hostname coverage
Stored certificate dates valid
Validity
Stored certificate expired
Collection time
2026-07-12 13:00:22 UTC
Collection source
PhishDestroy collector
Certificate fingerprint44e84272b02ac6ec1ad87c4a13210d4dafb86a666f545a63847305ce25242792
Certificate names · 2 SANs
  • jtx.network
  • *.jtx.network

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

6 / 89 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 6 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
SOCRadar
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of jtx.network · checked Jul 11, 2026

97
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
2.42s
Largest Contentful Paint
CLS
0.003
Cumulative Layout Shift
TBT
135ms
Total Blocking Time
SI
1.09s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history2

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unavailable→Reachable

  2. Availability monitor · Recorded state

    Reachable→Unavailable

Recorded activity

6 entries
  1. VirusTotal

    6/89 engine detections

    View source
  2. Abuse report sent #2

    ⚠️ ESCALATION #2 (621h active): Phishing - jtx[.]network

    abuse@dynadot.comabuse@identitydigital.comcompliance@icann.org
  3. URLScan

    Page captured

    View source
  4. Google Safe Browsing

    No threat flag

    View source
  5. Abuse report sent #1

    ⚠️ ESCALATION #1 (0h active): Phishing - jtx[.]network

    abuse@dynadot.comabuse@identitydigital.comcompliance@icann.org
  6. Added to PhishDestroy

    jtx.network

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

jtx.network

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-1783749018-jtx.network Recipient: abuse@dynadot.com
Blocklist hits included with submission: MetaMask, SEAL
PDF notice generated
Deep Analysis
Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 2 stored notification records Content 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.

Official reporting routes

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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

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.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including jtx.network)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/jtx.network"
  title="PhishDestroy threat report for jtx.network"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>