Aller au rapport de sécurité
Sécurité des domaines et renseignements sur les menaces
gfo-ltd.com favicon

gfo-ltd.com

“Attention Required! | Cloudflare”

Bureau d’enregistrement
Name SRS AB
Resolved IP
188.114.97.3
Registered
15/04/2026
PhishDestroy assessment Critique
First observed Sep 30, 2026 12:27 UTC · PhishDestroy
Détections VirusTotal : 2/92
OTX: 2 refs 30/09/2026 1 Report Sent CDN
API
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 2. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@namesrs.com. The latest stored availability evidence still shows the domain reachable; 20 days has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
20 days
Reports sent
1
Latest case ID
PD-20260930-637175
Current status
Observed active at latest stored check
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Résumé du rapport

Domaine sur listes de blocage: gfo-ltd.com — Non vérifié. Résumé des preuves: VirusTotal 2/92 (alphaMountain.ai, SOCRadar); URLScan malicious verdict; CF…

L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.

Source evidenceVirusTotal 2 / 92 · OTX 2 references 6 sources

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Renseignements sur la sécurité réseau
CF Cloudflare Radar Verdict Malveillant
Phishing Phishing Security threats

Analysis

Critique
VirusTotal
2 / 92
OTX
2 community refs
Page captures
3

PhishDestroy threat report

Overview

gfo-ltd.com is an impersonation phishing page that greets visitors with a fake Cloudflare screen titled "Attention Required! | Cloudflare". Scanning also picked up OKX branding, which points at OKX exchange users as the likely targets. PhishDestroy first flagged the domain on 2026-09-30. As of 2026-10-19 the site still responds, but its DNS no longer serves the phishing content.

How the scam works

A Cloudflare-style "Attention Required!" page looks like a routine bot check, so visitors trust it and click through without much thought. Behind that familiar gate, the scheme leads to content built around a trusted brand, here OKX, where victims are asked to sign in or confirm account details. Anything typed there, such as logins, one-time codes or recovery information, goes straight to the operators, who can use it to take over the account and withdraw its funds. The page title presents a Cloudflare challenge, while urlscan.io detected OKX branding. We classify the site as impersonation phishing.

Evidence

urlscan.io rated the page malicious and identified OKX as the brand on display, which is the strongest independent signal here. VirusTotal coverage is thin: on 2026-10-13 only 2 of 92 engines flagged it, alphaMountain.ai and SOCRadar. That low count means most security tools would not have warned a visitor. The domain appears in two AlienVault OTX threat pulses and is listed on the PhishDestroy blocklist.

Infrastructure

The domain was registered on 2026-04-15 through Name SRS AB, about five and a half months before PhishDestroy detected it. A gap that long suggests the domain was held in reserve or used quietly before it surfaced as phishing. The site sits behind Cloudflare's network, resolving to 188.114.97.3, with a Canadian location. Because Cloudflare fronts the site, the real origin server is hidden and the fake "Attention Required!" screen blends in with genuine Cloudflare traffic pages.

What to do

If you entered OKX credentials or codes after passing this page, change your OKX password at once from the official app and reset two-factor authentication. Then review active sessions, API keys and withdrawal address whitelists, and remove anything you do not recognize. If you reused that password anywhere else, change it there too, and treat any follow-up messages about "account verification" as part of the same attack. Defenders should block gfo-ltd.com at DNS and proxy level and search logs for past visits. They should also teach users that a Cloudflare challenge page does not make a site legitimate.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Capture enregistrée · 3 captures

Domain details

Domaine
URLScan verdict Malveillant score 100 Phishing brand: Okx report ↗
IP Context Cloudflare shared edge origin IP hidden La réputation Edge-IP n’est pas attribuée à ce domaine.
OTX tags activeblocklistcontentcryptodrainerfraudphishdestroyphishingscam
Bureau d’enregistrement Name SRS AB SE(SE)
EnregistrementCréé 15/04/2026 (188d) — Expires 15/04/2027
Détails techniquesProvenance & timestamps
Première détection30/09/2026
DOM Analysisanalyzed 09/10/2026score 76/1001 brand signal
Submitted URLhttp://gfo-ltd.com/
Favicon Hash
ID du dossier
Observed page title
Attention Required! | Cloudflare
Automated brand references
OKX
Certificat TLS
Émis par WE1

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

La réputation Edge-IP n’est pas attribuée à ce domaine.

Serveurs de noms 2

  • gabriel.ns.cloudflare.com
  • kehlani.ns.cloudflare.com

Location describes the IP network.

Certificat TLS

Issuer
WE1
Collection time
2026-10-20 16:02:33 UTC
Collection source
PhishDestroy collector

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-20 08:21:37 UTC

Primary outcome DNS inactif reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Inconnu Probe Inconclusive 20% 2026-10-20 10:06:47 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-09-30 22:44:39 UTC current episode first observed: 2026-10-01 16:16:25 UTC observed RIP window: 2026-09-30 22:44:39 UTC → 2026-10-01 16:16:25 UTC · 17.53h midpoint estimate ≈ 2026-10-01 07:30:32 UTC · precision medium · 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.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

2 / Les fournisseurs de sécurité 92 ont signalé ce domaine
View on VT
Last analyzed First positive detection Previous stored snapshot: 2 detections
alphaMountain.ai
SOCRadar

Preuves archivées

Wayback Machine Snapshot
Un instantané historique est disponible pour l’examen des preuves
View Archive
Analyse des performances du site

Google PageSpeed Insights — mobile performance audit of gfo-ltd.com · checked Sep 30, 2026

100
Good
Performance
FCP
0.77s
First Contentful Paint
LCP
0.77s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.77s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
17.53
Estimate basis
Bounded by observations
Estimate precision
Moyen

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history23

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

Earlier observations 18
  1. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  7. VirusTotal · Detection count

    3→2

  8. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  9. VirusTotal · Detection count

    2→3

  10. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  11. VirusTotal · Detection count

    1→2

  12. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  13. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  14. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  15. VirusTotal · Detection count

    5→1

  16. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  17. VirusTotal · Detection count

    4→5

  18. Availability monitor · First collection record

    Accessible

Recorded activity

6 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. AlienVault OTX

    2 community references

    View source
  3. VirusTotal

    2/92 engine detections

    View source
  4. Abuse report sent

    PD-20260930-637175

    abuse@namesrs.com
  5. Added to PhishDestroy

    gfo-ltd.com

    View source
  6. URLScan

    Page captured

    View source

Domaines ressemblants

142 domaines ressemblants enregistrés

c.loudflare.com subdomain claudflare.com vowel-swap cloadflare.com vowel-swap cloduflare.com transposition cloodflare.com vowel-swap clou.dflare.com subdomain cloudf.lare.com subdomain cloudfalre.com transposition cloudfla.re.com subdomain cloudflaer.com transposition cloudflarecom.com various cloudflore.com vowel-swap
Tout afficher (88)
cloudflrae.com transposition cloudflure.com vowel-swap cloudflwre.com replacement cloudlfare.com transposition cloufdlare.com transposition cluodflare.com transposition coludflare.com transposition c1oudf1are.com homoglyph c1oudflare.com homoglyph ccloudflare.com repetition cioudfiare.com homoglyph cioudflare.com homoglyph ckoudflare.com replacement cl0udfiare.com homoglyph cliudflare.com replacement clludflare.com replacement clo-udflare.com hyphenation clodflare.com omission clohdflare.com replacement cloidflare.com replacement clooudflare.com insertion cloubflare.com homoglyph clouclflare.com homoglyph cloud-flare.com hyphenation cloudcflare.com insertion cloudclare.com replacement clouddflare.com insertion cloudfare.com omission cloudfflare.com insertion cloudfiare.com homoglyph cloudfla1re.com insertion cloudflaare.com repetition cloudflae.com omission cloudflaee.com replacement cloudflar.com omission cloudflarr.com replacement cloudflarre.com repetition cloudflarz.com replacement cloudflate.com replacement cloudfllare.com repetition cloudflre.com omission cloudflsre.com replacement cloudiflare.com homoglyph cloudlare.com omission cloudlflare.com homoglyph cloudsflare.com insertion cloudtflare.com insertion cloudtlare.com replacement cloudvflare.com insertion cloudxflare.com insertion cloufflare.com bitsquatting clouflare.com omission cloulflare.com bitsquatting clourflare.com replacement clousflare.com replacement cloutflare.com bitsquatting clouudflare.com repetition clowdflare.com bitsquatting cloydflare.com replacement clpudflare.com replacement cludflare.com omission cmoudflare.com bitsquatting cnoudflare.com bitsquatting coudflare.com omission dloudflare.com homoglyph doudflare.com homoglyph gloudflare.com bitsquatting kloudflare.com bitsquatting loudflare.com omission sloudflare.com bitsquatting xn--clodflare-is7d.com homoglyph xn--cloudflae-7fe.com homoglyph xn--cloudflae-7n6d.com homoglyph xn--cloudflar-3f7d.com homoglyph xn--cloudflar-j4a.com homoglyph xn--cloudflre-676d.com homoglyph xn--clouflare-t05d.com homoglyph xn--cludflare-6x3d.com homoglyph xn--cludflare-ml7d.com homoglyph xn--coudflare-0sb.com homoglyph aloudflare.com bitsquatting bloudflare.com bitsquatting cdoudflare.com bitsquatting choudflare.com bitsquatting clgudflare.com bitsquatting clkudflare.com bitsquatting clmudflare.com bitsquatting clnudflare.com bitsquatting

100 affichés sur 142

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

gfo-ltd.com

Données factuelles et rapports externes

Instantané des preuves transmises
Sent: Ledger records: 1 Case ID: PD-20260930-637175 Recipient: abuse@namesrs.com
Page title stored with report: OKX Trading Bot
PDF notice generated
Référencement naturel et nom de domaine
Analyse approfondie
Help & reporting

Ce site vous a-t-il affecté ?

6 evidence signal groups linked 1 stored notification records Non vérifié
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.

Official reporting routes

Méfiez-vous des escrocs qui prétendent vous aider à récupérer vos biens ! Les criminels peuvent recontacter leurs victimes tout en se faisant passer pour des enquêteurs, des avocats ou des agents de recouvrement. Ne payez pas de frais initiaux et ne partagez pas vos informations d'identification. En savoir plus sur la fraude liée aux aides à la reprise →

Signalez-le à vos autorités locales

Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.

Annuaire de 97 pays

Template-based draft · optional AI wording assistance requires separate consent

Brouillon assisté par l'IA : les détails de l'incident sont traités par le fournisseur d'IA · Examinez-le et soumettez-le vous-même
After a phishing incident

Recommandations et conseils à l'intention des victimes

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

Que dois-je faire tout de suite ?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Modifier tous les mots de passe — e-mail, comptes Exchange, tout ce qui utilise le même mot de passe
  • Activer l'authentification à deux facteurs (2FA) en utilisant une application d'authentification (et non par SMS). Désactivez la récupération par SMS
  • Cartes « Freeze » si vous avez saisi vos coordonnées bancaires sur le site de hameçonnage

Quelles informations dois-je rassembler pour mon rapport ?

Directives du FBI

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Dates et horaires exacts — de chaque transaction et du premier contact avec l'escroc
  • Captures d'écran — sites web frauduleux, messages de chat, e-mails, transactions via des portefeuilles numériques, réseaux sociaux
  • Toutes les URL et tous les noms de domaine utilisés par l'escroc (notamment gfo-ltd.com)
  • Communications — les e-mails, SMS, numéros de téléphone et noms d'utilisateur utilisés par l'escroc

Même si vous ne disposez pas de tous les détails — déposer quand même une plainte. Même des informations partielles peuvent aider les enquêtes.

À qui dois-je signaler cette arnaque ?

  • FBI IC3 — Centre de signalement des délits sur Internet (système fédéral américain de signalement)
  • Europol — Rapports sur la cybercriminalité en Europe (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Police locale — permet de consigner officiellement la situation, même s’ils ne peuvent pas agir immédiatement

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Faux sites web — des clones identiques au pixel près de sites légitimes, dont les noms de domaine ont été légèrement modifiés
  • Découpe du porc — une relation de confiance établie au fil des semaines via Telegram, WhatsApp ou des applications de rencontre, puis une escroquerie financière
  • Arnaques liées au recouvrement — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Escroqueries basées sur l'IA — les « deepfakes », le hameçonnage automatisé et les sites générés par l'IA, qui rendent la fraude plus difficile à détecter

Comment puis-je me protéger à l'avenir ?

  • Ajouter les sites officiels à vos favoris — Ne cliquez jamais sur les liens contenus dans les e-mails, les messages privés ou les publicités
  • Vérifier les noms de domaine — vérifier si PhishDestroy avant d'entrer en contact. Vérifiez le protocole HTTPS, l'orthographe et l'ancienneté du domaine
  • « Trop beau pour être vrai » = arnaque — des rendements garantis, des témoignages de célébrités, des délais serrés

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Restez informés, restez en sécurité

Surveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif

Flux d'alertes en temps réel Contester cette annonce
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Intégrer ce rapport

Partagez ces informations sur les menaces sur votre site web ou votre blog

embed.html
<iframe
  src="https://phishdestroy.io/fr/embed/domain/gfo-ltd.com"
  title="PhishDestroy threat report for gfo-ltd.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>