VirusTotal
2 / 89 engine detections
रिपोर्ट खोलें“Go4Rex - the global leader in online trading”
Analysis performed on 27 July 2026 identifies www.go4rex.com as an active infrastructure supporting a generic phishing campaign.
मूल फॉरेंसिक रिकॉर्ड सुरक्षित रखने के लिए नीचे का विस्तृत PhishDestroy AI विश्लेषण अंग्रेज़ी में रखा गया है।
2 / 89 engine detections
रिपोर्ट खोलें35/100
checked — no detections recorded
रिपोर्ट खोलें1 community reference
रिपोर्ट खोलेंprovider verdict: clean
रिपोर्ट खोलेंNo threat flag
रिपोर्ट खोलेंNo malicious flag
रिपोर्ट खोलेंResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
Analysis performed on 27 July 2026 identifies www.go4rex.com as an active infrastructure supporting a generic phishing campaign. The domain resolves to the Cloudflare‑hosted address 172.67.143.42 and is delegated to the Cloudflare name servers ace.ns.cloudflare.com and jewel.ns.cloudflare.com, indicating use of a reputable CDN service to obscure the true hosting location. Registration data shows the domain was created on 29 November 2018 and is listed under the registrar MainReg Inc., a provider that does not inherently imply malicious intent but offers minimal transparency regarding registrant identity. VirusTotal records confirm that the domain was submitted to 91 scanning engines; none reported a detection at the time of analysis.
While the absence of detections does not constitute evidence of benign behavior, it demonstrates that automated malware scanners have not yet flagged the host as malicious. The domain appears on a single public blocklist, PhishDestroy, which has classified it as a phishing source and actively blocks traffic to the domain. This blocklist entry provides concrete evidence that security communities have observed abusive activity associated with the domain. Given the combination of Cloudflare front‑end services, a long‑standing registration period, and inclusion on a phishing‑specific blocklist, defenders should treat www.go4rex.com as a high‑confidence phishing indicator.
Recommended mitigations include adding the domain to network‑level deny lists, configuring web‑gateway filters to block HTTP(S) requests to the host, and monitoring DNS logs for queries to the domain. Continuous re‑evaluation is advised, as threat actors may modify the underlying payload or shift to new hosting while retaining the same domain. Until further forensic analysis of the website content is available, the domain should be considered malicious and blocked in enterprise environments.
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.
एज-आईपी प्रतिष्ठा इस डोमेन के लिए जिम्मेदार नहीं है।
ace.ns.cloudflare.comjewel.ns.cloudflare.comLocation describes the IP network.
2b38f1746a44958641f6bb853bffdc6e66fc106e6fb44b55854890ad26f1562fgo4rex.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of duplicate-disabled-342394.invalid · checked Jul 27, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
पहुँच योग्य→अनुपलब्ध
2/89 engine detections
View sourcePage captured
View source1 community references
View sourceNo threat flag
View sourceduplicate-disabled-342394.invalid
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
duplicate-disabled-342394.invalid
Listed domains receive at least one abuse report; this entry has no retained notification history.
यदि आपने खाता क्रेडेंशियल, व्यक्तिगत या भुगतान जानकारी दर्ज की है, या इस डोमेन से कोई फ़ाइल डाउनलोड की है, तो तुरंत कार्रवाई करें। घटना की रिपोर्ट करने और अपनी सुरक्षा करने में आपकी सहायता के लिए नीचे संसाधन दिए गए हैं।
आधिकारिक साइबर अपराध संपर्क, या एक शिकायत ड्राफ्ट बनाएं → प्राप्त करने के लिए अपना देश चुनें।
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
duplicate-disabled-342394.invalid)भले ही आपके पास सभी विवरण न हों — फिर भी रिपोर्ट दर्ज करें. आंशिक जानकारी अभी भी जांच में मदद करती है।
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
संग्रहीत ब्लॉकलिस्ट, WHOIS, DNS और सार्वजनिक स्कैन साक्ष्य का उपयोग करके खतरे का विश्लेषण
अभी स्कैन करेंसंदिग्ध डोमेन हमारे थ्रेट डेटाबेस में जमा करें — समुदाय की सुरक्षा करें
रिपोर्ट करेंहाल की फ़िशिंग रिपोर्टें और उपलब्धता में परिवर्तन देखे गए
निगरानी करेंलाइव खतरों की निगरानी करें या यदि आपको लगता है कि यह एक गलत सकारात्मक है तो इस लिस्टिंग को चुनौती दें।
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.