VirusTotal
5 / 92
SignalerEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“403 Forbidden”
Assessment based on the stored source evidence below. Review sources →
firelightfi.cc — Non vérifié. Usurpation de l'identité de la marque : ["across"]; Type d'arnaque : Impersonation. Résumé des preuves: VirusTotal 5/92 (ChainPatrol, alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet); Spamhaus DBL_SPAM; 3 external blocklist matches (MetaMask, ScamSniffer, SEAL); PhishDestroy score 90/100. Bureau d’enregistrement: NiceNIC.
The evidence summary below uses retained observations. Each source keeps its own collection date.
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.
5 / 92
SignalerEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
3 external matches
DétailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
DBL_SPAM
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
3 community references
SignalerCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: suspicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
rapport stocké
View stored capture ↗A preserved page image documents what the collector received; a capture is not a safety verdict.
Analyse terminée
SignalerThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
SignalerA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Evidence-based analysis Generated from the observations retained in this report. No stored AI narrative is available for this record. Each source retains its own collection date.
PhishDestroy first observed firelightfi.cc on Oct 7, 2026. Stored content metadata identifies ["across"] as the apparent target. The captured page title is “403 Forbidden”. Page analysis recorded additional brand references to Across. Stored page analysis classifies the content as impersonation. Current evidence score: 90/100 (critical).
Positive findings are stored from 5 sources: VirusTotal, MetaMask, ScamSniffer, SEAL, and Spamhaus DBL. VirusTotal recorded 5 detections among 92 engines: ChainPatrol, alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet on Oct 17, 2026 at 19:40 UTC. MetaMask, ScamSniffer, and SEAL listed the hostname in the separate external-blocklist snapshot on Oct 17, 2026 at 18:20 UTC. Spamhaus DBL: DBL_SPAM on Oct 7, 2026 at 10:30 UTC. Additional recorded evidence: AlienVault OTX listed 3 community pulse references (not vendor detections) on Oct 17, 2026 at 19:40 UTC.
Latest classified outcome: dns inactive; cause dns nxdomain on Oct 16, 2026 at 18:22 UTC. Registration records for the domain list NICENIC INTERNATIONAL GROUP CO., LIMITED as the registrar and Oct 5, 2026 as the creation date. Registration preceded first observation by 1 day. At collection time, the hostname resolved to 94.156.119.252 on AS211673 (Mynymbox Mynymbox Hosting LLC, KN). The recorded endpoint location is Amsterdam, NL. The stored server header is Apache/2. DOM analysis on Oct 9, 2026 at 18:23 UTC returned 10/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists Let's Encrypt / YE1 as the certificate issuer with validity through Jan 3, 2027; checked Oct 7, 2026 at 10:02 UTC.
The content indicators and 5 positive source findings support the current ["across"]-themed impersonation classification.
18 · datasets with records / 13 · 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.
These checks have no retained result. This does not mean they passed or that a scan is running.
3 · external source matches
NICENIC INTERNATIONAL GROUP CO., LIMITED · 94.156.119.252 · DNS, TLS and retained responses
dns2.mynymhosting.netmail.firelightfi.ccpriority 10Location describes the IP network.
89773f5e6a38a93f0f92e03cfc61e627dfbbecb6f8029313faa27534762ffd08Saved 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 firelightfi.cc · checked Oct 7, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
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.
Note relative à la numérisation: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='firelightfi.cc', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
Collection history, report status and investigation channels
94.156.119.252.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
dns_inactive→Inconnu
probe_inconclusive
Inconnu→dns_inactive
dns_nxdomain
4→5
5→4
4→5
dns_inactive→Inconnu
probe_inconclusive
Inconnu→dns_inactive
dns_nxdomain
5→4
dns_inactive→Inconnu
probe_inconclusive
Inconnu→dns_inactive
dns_nxdomain
4→5
dns_inactive→Inconnu
probe_inconclusive
Inconnu→dns_inactive
dns_nxdomain
dns_inactive→Inconnu
probe_inconclusive
Inconnu→dns_inactive
dns_nxdomain
dns_inactive→Inconnu
probe_inconclusive
Inconnu→dns_inactive
dns_nxdomain
dns_inactive→Inconnu
probe_inconclusive
Inconnu→dns_inactive
dns_nxdomain
3→4
dns_inactive→Inconnu
probe_inconclusive
live_content→dns_inactive
dns_nxdomain
8→3
Inconnu→live_content
content_served
live_content→Inconnu
probe_inconclusive
Inconnu→live_content
content_served
7→8
6→7
live_content→Inconnu
probe_inconclusive
5→6
Inconnu→live_content
content_served
4→5
2→4
live_content→Inconnu
probe_inconclusive
Inconnu→live_content
content_served
Inconnu
stale_current_evidence
Inconnu
24 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.
Shared hosting, registrar records and related domains
Original reports, independent checks and evidence links
Recovery steps, reporting contacts and complaint drafts
Listed domains receive at least one abuse report; this entry has no retained notification history.
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.
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
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 ↗
firelightfi.cc)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.
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
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerRapports de phishing récents et changements de disponibilité observés
SurveillerSurveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif
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 “403 Forbidden” et usurpait peut-être l'identité de ["across"].
Depuis 2026-10-17 19:40:16 UTC, firelightfi.cc avait des détections provenant des moteurs de sécurité 5.
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.