Aller au rapport de sécurité
Tableau de bord analytique
Domain security report
quicknode.fhlac.com favicon

quicknode.fhlac.com

“Home”

Verdict de menace
CritiqueRecours en matière de nom de domaine
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Disponibilité Dernier actif connu Dernière observation d'accessibilité stockée Observé · HTTP probe
Signaux de risque
Correspondances de la liste de blocage stockée : 2 Automated brand label: Google Google Safe Browsing: threat flag recorded
16/10/2026 Google 1 Report Sent
API
Bureau d’enregistrement
Gname
Resolved IP
95.40.116.4
Registered
11/01/2015
2 sources
The capture source is temporarily unavailable.
1 / 2
Source
Primary capture
Collected · UTC
Open capture
Stored TLS certificateHostname mismatchReview certificate names and collection time
In this reportGet help
Ce domaine a été signalé comme malveillant
Listes de blocage publiques signalant une correspondance : 2. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
ABUSE NOTICE · 24H+ 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 complaint@gname.com. The latest stored availability evidence still shows the domain reachable; 29 hours 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
29 hours
Reports sent
1
Latest case ID
PD-20261016-EFC34E
Current status
HTTP 200 at latest stored check
Résumé du rapport

quicknode.fhlac.com — Dernier actif connu (HTTP 200). Usurpation de l'identité de la marque : Google; Type d'arnaque : Impersonation. Résumé des preuves: VirusTotal 0/92; URLScan malicious verdict; Google Safe Browsing flagged; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 80/100. Bureau d’enregistrement: Gname.

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

Additional indicators at a glance

URLScan
URLScan
Signaler ↗
Certificat TLS
Hostname mismatch
Let's Encrypt / YR2 · Certificate hostname mismatch
Âge
11.8 yr
Statut observé
Dernier actif connu 200
PhishDestroy
DestroyList
Répertorié
Reports Sent
1

Source evidence

8 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

URLScan verdict

malicious

Signaler
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Threat flag recorded

Signaler
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

2 external matches

Détails
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

VirusTotal

checked — no detections recorded

Signaler
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

Report stored; detailed verdict not recorded

Observation time not recorded
Signaler
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

OTX

no community references

Signaler
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Signaler
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

rapport stocké

View stored capture ↗
Signaler
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

Résumé des preuves

Critique
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

The domain quicknode.fhlac.com was observed on 2026-10-16 with a Google Safe Browsing record documenting a social engineering threat. Additionally, a PageSpeed performance score was measured for the domain on the same date, providing insight into its technical infrastructure.

Recorded Evidence

VirusTotal checked quicknode.fhlac.com on 2026-10-11 and recorded 0 detections out of 92 scanners. Google Safe Browsing flagged the domain for social engineering threats on 2026-10-16. The domain appeared on two external blocklists, MetaMask and SEAL, as of 2026-10-16. PhishDestroy internally listed the domain, and a PageSpeed performance score of 43 was recorded on 2026-10-16.

Interpretation

PhishDestroy contains an internal listing for quicknode.fhlac.com, which is a type of measurement documenting its presence in a curated database. VirusTotal provides a scan-based record, showing how many detection engines flagged the domain at a specific time. The evidence from Google Safe Browsing and external blocklists adds context from other security sources, offering a broader view of how the domain is referenced in multiple intelligence systems.

Recommended Actions

For quicknode.fhlac.com, it is practical to retain the Google Safe Browsing and VirusTotal records for future comparison. The MetaMask and SEAL blocklist entries should be preserved as reference points for ongoing monitoring. Maintaining the PhishDestroy internal listing and PageSpeed performance score will support technical and security reviews over time.

Data coverage & collection

22 · datasets with records / 9 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
0 / 92 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
Stored source recordCollection time not recorded
Google Safe Browsing
Threat flag recorded
OTX publications
0 · community references
External blocklists
2 · external matches
Cloudflare Radar
sainCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
Gname.com Pte. Ltd.Collection time not recorded
Network & DNS
95.40.116.4 · 2 · nameserversCollection time not recorded
Certificat TLS
Let's Encrypt / YR2
Page captures
2 · retained captures
HTML archives
1 · retained responses
Page analysis
0 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Site configuration files
robots.txt · sitemap.xml · security.txt
PageSpeed performance
43/100 · mobile performance
Response records
1 · outgoing report records
Availability history
2 · stored state changes
Source observation history
2 · stored source events
IP reputation
Network-level observations
Not recorded in this report 9

These checks have no retained result. This does not mean they passed or that a scan is running.

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Recorded subdomains
  • Lookalike relationships
  • Signalements communautaires
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

2 · external source matches

Statut de la liste de blocage publique

Domain, network & archive

Gname.com Pte. Ltd. · 95.40.116.4 · DNS, TLS and retained responses

Domain details

Domaine
URLScan verdict Malveillant score 100 Phishing report ↗
Google Safe Browsing Marqué Social engineering checked 17/10/2026
Réputation de l’IP abuse score 2/100 2 reports PhishingBad Web Bot checked 16/10/2026
Registrar (base domain) Gname CN(CN)
Contact anti-abuscomplaint@gname.com
Registre de l'ICANNICANN Lookup (RDAP) →
Recherche WHOISICANN RDAP pour fhlac.com →
Registration (base domain)fhlac.com · Créé 11/01/2015 — Expires 11/01/2027
Statut HTTP200
Détails techniquesProvenance & timestamps
Première détection16/10/2026
DOM Analysisanalyzed 16/10/2026score 80/100
Submitted URLhttp://quicknode.fhlac.com/
Favicon Hash
ID du dossier

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
95.40.116.4
Network ASN
AS16509
Organization
Amazon.com, Inc.
Observed location
Hong Kong, HK
Server header
nginx
Serveurs de noms 2
  • a10.share-dns.com
  • b10.share-dns.net

Location describes the IP network.

Certificat TLS

Issuer
Let's Encrypt / YR2
Valid from
2026-10-05 10:43:34
Valid until
2027-01-03 10:43:33
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-16 16:02:08 UTC
Collection source
PhishDestroy collector
Certificate fingerprintf7b640e137a81204c2a47f4165b06dfe29661838d049d9cfbae731523dcd9ec9
Certificate names · 4 SANs
  • quicknode.miutone.com
  • quicknode.vhuatu.com
  • quicknode.yiguk.com
  • quicknode.zikaoe.com

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

viewdns.info · 95.40.116.4rapiddns.io

Latest Classified Outcome 2026-10-17 10:00:14 UTC

Primary outcome Contenu actif reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Contenu actif Ordinary HTTP content served 90% 2026-10-17 10:00:14 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-17 10:00:14 UTC last content: 2026-10-17 10:00:14 UTC
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.
Recoupement des renseignements sur les menaces · source references
ScamAdviser Public lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
View on ScamAdviser
Live-fetched via CF worker proxy pool · cached 24h
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres
Analyse des performances du site

Google PageSpeed Insights — mobile performance audit of quicknode.fhlac.com · checked Oct 16, 2026

43
Poor
Performance
FCP
5.61s
First Contentful Paint
LCP
8.95s
Largest Contentful Paint
CLS
0.245
Cumulative Layout Shift
TBT
70ms
Total Blocking Time
SI
21.31s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://quicknode.fhlac.com/
QuickNode
Réponse
HTTP 200
HTML body
1.8 KB
Compressed
903 B
Links
0 internal · 2 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html
Content-Encoding: gzip
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: b4ba1c96f64b44c6f9438051d441f3fa3b19ffc742f4e90b465c66324c6b7ae2
Saved response-header values · 10
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Fri, 16 Oct 2026 14:39:24 GMT
Etag
W/"6a9c54fa-726"
Last-Modified
Sat, 05 Sep 2026 17:44:26 GMT
Server
nginx
Strict-Transport-Security
max-age=31536000
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

Archived
Crawler & disclosure files

Site configuration evidence

3 · file checks

Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.

robots.txt

Reachable (legacy)
/robots.txt
HTTP response
200
Observed at
2026-10-16 14:39:27 UTC
Source
legacy scan archive

A legacy scan recorded a successful response. The file contents were not retained.

Sitemap

Reachable (legacy)
/sitemap.xml
HTTP response
200
Observed at
2026-10-16 14:39:27 UTC
Source
legacy scan archive

A legacy scan recorded a successful response. The file contents were not retained.

security.txt

Introuvable
/.well-known/security.txt
HTTP response
404
Observed at
2026-10-16 14:39:27 UTC
Source
legacy scan archive

The scanner received HTTP 404 or 410 for this file.

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Detection & evasion checks

Stored browser and crawler observations

Analyse de la détection et de l'évasion

Suspicion de cloaking : les titres du scanner et ceux des visiteurs diffèrent

Pas encore numérisé Aucune différence entre les robots d'indexation et les navigateurs n'a encore été constatée

Enregistrement des observations « crawler contre navigateur » pour cet hôte, ainsi qu'une vérification en temps réel des empreintes numériques pour les systèmes de répartition du trafic de type Keitaro.

Indicateur de camouflage enregistré
Pas encore numérisé
Dernier scan de camouflage
En-tête du serveur détecté par le scanner
nginx
Routage de la capture
Local archivé le 2026-10-16 14:39:27 UTC

Note relative à la numérisation: alive_content: raw=ok; http=200; via=https_proxy; server=nginx

Titre affiché sur le scanner de sécuritéQuickNode
Titre affiché pour un visiteur du navigateurAccueil
Vérification en direct des empreintes digitales d'TDS
Sept empreintes Keitaro et une comparaison entre navigateur et robot. Une nouvelle analyse démarre uniquement en cliquant sur le bouton.
À la demande

Aucun résultat de vérification enregistré.

Timeline & response

1 · outbound report records

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Status Check 2026-10-16 15:09:17 UTC
    Source: PhishDestroy monitoring
    Event details
    Telemetry event observed.
  2. Threat First Observed 2026-10-16 14:39:01 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 95.40.116.4.
Stored observation history4

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→live_content

    content_served

  2. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  3. Availability monitor · Recorded state

    Inconnu

    probe_inconclusive

  4. Availability monitor · First collection record

    Accessible

Processus de réponse aux menaces Pipeline

Découverte
Analysis
Notifications
Monitoring

11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Menace détectée
quicknode.fhlac.com détectés et mis en file d'attente en vue d'une analyse complète
16/10/2026
URLScan.io Capture
Enregistré URLScan report with capture artifacts
16/10/2026
URLScan Verdict
URLScan returned a malicious verdict · score 100
17/10/2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Google Safe Browsing
Flagged via Rapport de transparence de Google
17/10/2026
Détection des listes noires
Trouvé dans 2 blocklists: MetaMask, SEAL
17/10/2026
Brand Impersonation
Impersonation of Google
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
16/10/2026
Technical Analysis Recorded
Le rapport contient des résultats de technologie ou d’analyse médico-légale stockés.
17/10/2026
Sent Report Recorded
Stored outgoing record associated with registrar Gname.com Pte. Ltd., 1 abuse contact
complaint@gname.com
16/10/2026
DestroyList publié
Listed in the public PhishDestroy/DestroyList repository
16/10/2026
Monitoring Continues
Le domaine reste accessible ou restreint en accès ; des contrôles futurs pourraient mettre à jour cette observation.
How we investigate & report

Public scans, evidence and abuse channels

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.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecÉvaluation du site AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Related infrastructure

Shared hosting, registrar records and related domains

Evidence & investigation tools

Original reports, independent checks and evidence links

Données factuelles et rapports externes

Analyse de sécurité
URLScan Malveillant VirusTotal ChainPatrol URLQuery Report stored Google SB Marqué SSL Laboratoires Certificate hostname mismatch CF Radar Ouvrir le rapport WOT ScamAdviser Vérificateur de liste noire URL nulle Sucuri SiteCheck Observatoire MDN
Instantané des preuves transmises
Sent: Ledger records: 1 Case ID: PD-20261016-EFC34E Recipient: complaint@gname.com
PDF notice generated Notice text archived (317 chars)
Abuse notice text as sent to the provider 
Registrar: Gname.com Pte. Ltd. (Singapore)
Policy Violations: Illegal Activities section forbids phishing, fraud, fake sites, malware distribution; registrar investigates and may suspend or delete domain
Applicable Laws: Computer Misuse Act 1993 §§3+, Penal Code §§415–420 (cheating), Online Criminal Harms Act (OCHA)
OSINT et renseignement
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certificats WHOIS Wayback
DNS et réseau
nslookup.io DNS bgp.tools ASN /Itinéraire
Référencement naturel et nom de domaine
SpyFu Moz DA/PA Ahrefs Liens entrants
Analyse approfondie
Analyse approfondie

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Ce site vous a-t-il affecté ?

4 evidence signal groups linked 1 stored notification records Dernier actif connu
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.

Immediate steps Find reporting contacts
Official reporting routes
PhishDestroy listing review Pas un rapport des forces de l'ordre
Recours en matière de nom de domaine
Demandez un examen si vous possédez ce domaine et pensez que la liste est incorrecte
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 quicknode.fhlac.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

Vérifier n'importe quel domaine

Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique

Scanner maintenant

Signaler une tentative d'hameçonnage

Signalez les domaines suspects à notre base de données des menaces — protégez la communauté

Signaler

Flux d'alertes en temps réel

Rapports de phishing récents et changements de disponibilité observés

Surveiller

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
Read the evidence in context

À propos de ce rapport : quicknode.fhlac.com

Ce rapport présente les dernières preuves stockées disponibles pour PhishDestroy. Les horodatages sources sont affichés lorsqu'ils sont disponibles ; la disponibilité et les verdicts des fournisseurs peuvent changer après la collecte.

Le site capturé affichait le titre de la page “Home” et usurpait peut-être l'identité de Google.

PhishDestroy répertorie quicknode.fhlac.com comme suspect. Il a été vérifié par les moteurs de sécurité 92 ; les verdicts automatisés peuvent changer. La surveillance se poursuit. Observé: 2026-10-16 15:09:16 UTC

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

Si vous pensez que cette liste est inexacte, déposer un recours. Pour en savoir plus sur notre méthodologie, visitez le Page FAQ.

Embed this report

A 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/quicknode.fhlac.com"
  title="PhishDestroy threat report for quicknode.fhlac.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>