VirusTotal
2 / 89
ergonext.pro returned HTTP status 502 in a check dated 2026-10-01, indicating the server did not return a normal response at that moment. The domain's registration date is recorded as 2026-09-11, placing it shortly before the earliest observation in this evidence set.
The PhishDestroy internal catalogue listed ergonext.pro as of this evidence set, and OTX recorded 3 pulses on 2026-09-23. VirusTotal reported 2 detections across 89 scanners on 2026-09-23, with no known observation time. The domain was first observed on 2026-09-16, and the registrar is recorded as Porkbun LLC.
The OTX and VirusTotal checks share the 2026-09-23 date, so those two sources describe the same day, while the HTTP check on 2026-10-01 and the first observation on 2026-09-16 sit at different points. Because the dates differ, a reader cannot treat the records as a single snapshot; the PhishDestroy listing and the 502 response were captured on separate occasions.
Reviewers should retain the ergonext.pro records with their exact dates, including the 2026-10-01 HTTP result and the 2026-09-23 OTX and VirusTotal entries. Any later check of ergonext.pro should be compared against these dated observations rather than assumed to match them. Until the review is complete, avoid submitting credentials or other sensitive information to ergonext.pro.
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='ergonext.pro', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S
ian.ns.cloudflare.comLocation describes the IP network.
9 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
CategoryPHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-09-16T10:26:19.413Z.
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