VirusTotal
6 / 91
“NetRich - Home”
netrich.network returned HTTP status 200 on 2026-10-01, according to the recorded HTTP check for that date. The same evidence set records a first observation of the domain on 2026-08-19, with an SSL certificate scanned that day.
The HTTP check dated 2026-10-01 recorded status 200 for netrich.network. The first observation of netrich.network is dated 2026-08-19, and the SSL scan on 2026-08-19 identified the issuer as Sectigo Limited / Sectigo Public Server Authentication CA DV R36. VirusTotal, checked on 2026-09-28, reported 6 detections across 91 scanners. OTX, checked on 2026-08-21, recorded 4 pulses. The registrar is listed as NameCheap, Inc., and the PhishDestroy internal listing is recorded as true.
The HTTP, SSL, VirusTotal, and OTX records carry different observation dates, so a reader comparing them is comparing separate snapshots rather than one synchronized view. The VirusTotal and OTX counts come from named sources with their own collection methods, and the PhishDestroy internal listing reflects that catalogue's own record. Because the dates differ, later observations may not reflect the conditions seen at earlier checks.
Reviewers should retain the dated records for netrich.network so that any later observation can be compared against the 2026-08-19 first observation and the 2026-10-01 HTTP check. When new checks are run, record the source name and exact date alongside each result to keep comparisons meaningful. Avoid submitting sensitive information while reviewing netrich.network, since the recorded HTTP response alone does not establish present availability or safety.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='netrich.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.
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.
dns1.namecheaphosting.commx1-hosting.jellyfish.systemspriority 5mx2-hosting.jellyfish.systemspriority 10mx3-hosting.jellyfish.systemspriority 20Location describes the IP network.
a53c8d32ddde5055715212d89187b5962c1b5fda6357ac6e974b06ccbb821916www.netrich.networkSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
1 community report
CategoryOTHER_INVESTMENT_SCAM
Data submited by Intelligence for good
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
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