Analysis of www.netxworld.online as of July 24 2026 indicates a high‑risk generic phishing campaign. The domain was registered through NameCheap, Inc. on February 21 2026 and is hosted behind Cloudflare’s network (AS13335, United States). DNS resolution points to IP 188.114.96.3, and the authoritative nameservers are hazel.ns.cloudflare.com and javier.ns.cloudflare.com. HTTP requests receive a 301 redirect response, and the site presents an SSL certificate issued by Let’s Encrypt (certificate identifier E7), confirming encrypted transport. Automated scanning on VirusTotal recorded a single positive detection out of 95 security vendors, and the domain appears on one external blocklist, where it is also listed by PhishDestroy.
The page title returned from the live endpoint is “Home | NetX”, but no further content analysis is available. Detected server technologies include Cloudflare’s edge services and HTTP/3 support. The presence of a valid TLS certificate and Cloudflare’s CDN does not mitigate the phishing risk; instead, they can be leveraged to increase credibility. The single vendor flag and blocklist entry suggest that at least one security product has identified malicious behavior, but the low detection count leaves uncertainty about the breadth of the payload or victim targeting. No additional intelligence such as malware hashes, command‑and‑control infrastructure, or phishing page screenshots is currently available.
Defenders should block outbound connections to 188.114.96.3 at the network perimeter, add www.netxworld.online to URL filtering and email phishing protection lists, and monitor DNS queries for the domain and its nameservers. Continuous re‑scanning on multi‑engine services is recommended to capture any escalation in detection counts. Organizations using Let’s Encrypt certificates should not assume safety based on issuance alone, and any credential‑capture attempts that reference “NetX” should be treated as suspicious.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-19 22:16:24 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-19 22:16:24 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.
使用技術 · 2 identified
Cloudflare
CDN
Web infrastructure and security company providing CDN, DDoS mitigation, and DNS services.
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(US)
