गूगल सुरक्षित ब्राउज़िंग
ध्वजांकित
Social engineering
“GFO-X”
ध्वजांकित
Social engineering
0
threat pulses mention the domain
Online · HTTP 200
Cloudflare · 172.67.210.173 · TLS: Let's Encrypt
Each check shows its own collection time. Zero detections do not guarantee safety.
फ़िशिंग: gfo-eth.com — सामग्री अनुपलब्ध. साक्ष्य सारांश: VirusTotal 11/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data); Spamhaus…
मूल फॉरेंसिक रिकॉर्ड सुरक्षित रखने के लिए नीचे का विस्तृत PhishDestroy AI विश्लेषण अंग्रेज़ी में रखा गया है।
11 / 89 engine detections
रिपोर्ट खोलेंDBL_PHISH
4 community references
रिपोर्ट खोलें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
gfo-eth.com is an impersonation phishing page that presented itself under the GFO-X name. It targeted crypto traders who might believe they were dealing with that brand, and the "eth" in the domain points toward Ethereum users. PhishDestroy flagged it on 2026-09-15, the same day the domain was registered. The site has been offline since 2026-09-22 and was still unreachable when last checked on 2026-10-19.
The page carried the title "GFO-X" so that visitors arriving from ads, direct messages or search results would take it for the real brand. Impersonation pages like this usually ask visitors to sign in, connect a wallet or make a deposit. Login details typed into the form go straight to the operators. A wallet connection or signature request can give them permission to move tokens, and any deposit sent to an address shown on the page is lost.
Eleven of 89 VirusTotal engines marked the domain malicious on 2026-09-17, two days after registration. The vendors included Google Safe Browsing, Fortinet, Forcepoint ThreatSeeker, G-Data, CRDF, alphaMountain.ai, Gridinsoft and LevelBlue. Spamhaus lists it in its DBL under the phishing category. MetaMask and SEAL block it alongside PhishDestroy, so many wallet users would have seen a warning before the page loaded. It also appears in four AlienVault OTX threat pulses.
The domain was registered through Cloudflare, Inc. on 2026-09-15 and was caught within hours. That pattern fits a domain set up for a short campaign. Traffic was served through Cloudflare's network, geolocated to Canada, which hides the actual origin server. The page lasted about a week before it went dark on 2026-09-22.
If you entered a password or recovery details on this page, change that password everywhere you reused it and turn on app-based 2FA. Never reuse a seed phrase that has been typed into a website. Move any remaining funds to a new wallet. If you connected a wallet or signed anything, revoke token approvals with a trusted approval checker and watch the wallet for unexpected transfers. Defenders should block the domain at DNS and proxy level and search mail and chat logs for links to it from 2026-09-15 onward.
Last checked
एज-आईपी प्रतिष्ठा इस डोमेन के लिए जिम्मेदार नहीं है।
betty.ns.cloudflare.comrazvan.ns.cloudflare.comLocation describes the IP network.
52e5741e0b4ce8b836d0c2909cfc5549b2199dcd6a11e7e0772bc939530f15caSaved 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 gfo-eth.com · checked Sep 15, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
gfo-eth.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
पहुँच योग्य→अनुपलब्ध
0→4
No flag recorded→Flag recorded
पहुँच योग्य
No threat flag
View source11/89 engine detections
View source4 community references
View sourcegfo-eth.com
View sourcePage captured
View sourceListed 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 ↗
gfo-eth.com)भले ही आपके पास सभी विवरण न हों — फिर भी रिपोर्ट दर्ज करें. आंशिक जानकारी अभी भी जांच में मदद करती है।
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.