The domain nodego.network is identified as a high-risk generic_phishing site and is currently offline. It does not impersonate a specific brand but poses a significant threat due to its phishing activities.
Analysis indicates that nodego.network has been flagged by 19 out of 95 security vendors on VirusTotal, highlighting its potential for malicious intent. The domain is registered through Cloudflare, Inc., and resolves to the IPv6 address 2606:4700:3032::6815:282c, which is located in the United States and is part of the AS13335 Cloudflare, Inc. network. The domain appears on five security blocklists, including PhishDestroy, Polkadot, Enkrypt, Codeesura, and PhishingDB, further underscoring its risk level. The lack of an SSL certificate and the generic page title 'Just a moment...' are additional indicators of its suspicious nature.
Currently, the domain nodego.network is offline. However, organizations and individuals are advised to remain vigilant and ensure that all systems are updated to block this domain. Network administrators should configure firewalls and security solutions to prevent access to the associated IP address. Users should be educated on the signs of phishing attempts and encouraged to report any suspicious activity immediately. Regular audits of network traffic and security logs are recommended to detect and respond to any attempts to revive or redirect the domain.
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='nodego.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.
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.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:10:38 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-04-22 04:24:33 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-22 04:24:33 UTC → 2026-09-30 16:14:55 UTC · 3,875.84hmidpoint estimate ≈ 2026-07-11 22:19:44 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.
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.
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.
(US)
