VirusTotal
1 / 93 engine detections
Ouvrir le rapport“Signalpointjs: Most Popular Online Crypto Casino Based on Blockchain”
Arnaque de casino crypto: signalpointjs.online — Contenu indisponible. Résumé des preuves: VirusTotal 1/93 (SOCRadar); URLScan malicious verdict; PhishDestroy…
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
1 / 93 engine detections
Ouvrir le rapportMalveillant
Ouvrir le rapportchecked — no detections recorded
Ouvrir le rapportno community references
Ouvrir le rapportprovider verdict: clean
Ouvrir le rapportNo threat flag
Ouvrir le rapportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
Analysis of signalpointjs.online, observed as offline as of July 25 2026, indicates the domain is being used for a crypto‑focused phishing campaign. The site was registered on 26 February 2026 via NameCheap, Inc., and resolves to the Cloudflare address 172.67.196.5, which belongs to AS13335 in the United States. The domain appears on a single security blocklist and has been explicitly blocked by PhishDestroy. No SSL certificate is presented, and the authoritative name servers are craig.ns.cloudflare.com and princess.ns.cloudflare.com, confirming reliance on Cloudflare’s DNS infrastructure.
VirusTotal scans show that one of ninety‑three security vendors flagged the domain, reinforcing the suspicion of malicious intent. The page title retrieved from the live snapshot reads “Signalpointjs: Most Popular Online Crypto Casino Based on Blockchain,” and the campaign has been linked to the Gambler Scam phishing kit, a known template used to lure victims into fake cryptocurrency casino offers. The classification of the threat is a Crypto Scam, consistent with the title and kit association. While the offline status prevents direct interaction, the presence of the domain on a blocklist, the lack of TLS protection, and the vendor detection collectively substantiate a credible phishing risk.
Uncertainties remain regarding the exact payload delivered to victims, the extent of credential harvesting, and whether additional infrastructure (e.g., command‑and‑control servers) is associated with the same IP range. Defenders should immediately add signalpointjs.online to URL filtering and DNS sinkhole policies, block the associated IP 172.67.196.5 at the network perimeter, and monitor for any traffic to Cloudflare name servers that match the observed pattern. Continuous re‑scanning of the domain and its IP is recommended in case the site is re‑hosted, and any observed attempts to mimic the casino branding should be flagged for further forensic analysis.
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.
La réputation Edge-IP n’est pas attribuée à ce domaine.
craig.ns.cloudflare.comprincess.ns.cloudflare.comLocation describes the IP network.
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.
signalpointjs.online
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
Inconnu→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
https://radar.cloudflare.com/scan/fd55bcf1-6ae9-4742-b7b0-ef56fdf41c2b
No threat flag
View source1/93 engine detections
View sourcesignalpointjs.online
View sourceSignalé par 1 membre de la communauté ; première observation le 26/02/2026
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 ↗
signalpointjs.online)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
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.