Security engines reporting a detection: 5. Public blocklists reporting a match: 3. Exercise extreme caution — do not enter credentials or personal information.
According to Tranco this site has a low rank We tried to analyze the content of the site but failed This website seems to offer financial services but does not have a valid SSL certificate
This website is safe according to DNSFilter
Evidence Summary
Critical
VirusTotal
5/95
URLScan
Stored capture
Analysis of cloudnetwork.digital, observed on July 25, 2026, shows the site is currently offline but retains a set of indicators consistent with a brand‑impersonation operation targeting Ethereum users. The domain resolves to the Cloudflare edge address 172.67.207.174, located in the United States under ASN 13335, confirming hosting through Cloudflare, Inc. The registration was also performed via Cloudflare, Inc., and the authoritative name servers are khloe.ns.cloudflare.com and sam.ns.cloudflare.com. No SSL certificate is presented, meaning HTTPS connections would be untrusted or unavailable. The page title returned when the site was reachable was "CloudNetwork Mining - Professional Cloud Mining," suggesting a claim of cloud‑based cryptocurrency mining services, a common lure for Ethereum‑related scams.
VirusTotal scans show that five of ninety‑five security vendors flagged the domain, indicating that at least a minority of scanners detected malicious characteristics. Independent reputation services assign extremely low trust scores: Gridinsoft rates the domain 0 out of 100, and Scamadviser rates it 1 out of 100, both reflecting a near‑certain malicious reputation. The domain appears on four security blocklists and has been explicitly blocked by the PhishDestroy, Polkadot, Enkrypt, and Codeesura blocklists, reinforcing the consensus that it is being used for malicious purposes.
While the site is offline, the combination of low trust scores, blocklist presence, a brand‑impersonation tag, and the Ethereum‑focused page title provides sufficient evidence for security teams to treat the domain as hostile. Defenders should continue to block cloudnetwork.digital at the DNS and proxy layers, monitor for any re‑activation or changes in hosting, and consider adding the domain to internal threat‑intel feeds.
Extracted from stored page analysis
Observed indicators
4 wallet · 0 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
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 DetectedNov 3, 2025
DOM Analysisanalyzed Apr 23, 2026score 45/1004 brand signals
IoC Extractionscanned Aug 2, 20264 wallet · 0 Telegram IoCs
Submitted URLhttp://cloudnetwork.digital/
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.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:09:12 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-06-14 22:43:46 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-14 22:43:46 UTC → 2026-09-30 16:14:55 UTC · 2,585.52hmidpoint estimate ≈ 2026-08-07 19:29:20 UTC · precision very low · basis bounded
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.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
cloudnetwork.digital 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.
May 8, 2026
Time to First Unavailability
4456 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.
5 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 →
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
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · cloudnetwork.digital
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.
(US)
