VirusTotal
5 / 90 engine detections
Ouvrir le rapport“Jackson Template”
Usurpation de Google: brightonbitcore.digital — Contenu indisponible. Résumé des preuves: VirusTotal 5/90 (alphaMountain.ai, Chong Lua Dao, Forcepoint…
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
5 / 90 engine detections
Ouvrir le rapportDBL_PHISH
no community references
Ouvrir le rapportprovider verdict: clean
Ouvrir le rapportNo threat flag
Ouvrir le rapportNo malicious flag
Ouvrir le rapportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain brightonbitcore.digital was registered on July 22, 2025 through Hosting Concepts B.V. d/b/a Registrar.eu and is hosted on a single authoritative nameserver. It resolves to IPv4 address 45.9.148.217, which is announced by AS49447 (Nice IT Services Group Inc.) and geolocated to the Netherlands. The site presents a valid‑looking TLS certificate issued by Google Trust Services with the WE1 intermediate, providing a credible HTTPS appearance. An HTTP request returns status code 200 and the page title reported is “Jackson Template,” but the page content has not been disclosed in the current intelligence.
Infrastructure analysis indicates the domain is fronted by Cloudflare and negotiates HTTP/3, suggesting CDN use for traffic concealment. The domain is listed on one security blocklist and has been flagged by PhishDestroy as still active. VirusTotal scans show 2 of 95 security vendors flagging the domain as malicious, and Gridinsoft assigns a trust score of 0 out of 100, reinforcing the high‑risk classification.
The domain is explicitly categorized as a brand‑impersonation of Google. No further details about credential‑harvesting pages or payloads are available, leaving the exact malicious behavior uncertain.
Defenders should block or sinkhole DNS queries for brightonbitcore.digital and any traffic to 45.9.148.217, add the domain to URL filtering and email security policies, and monitor for new domains registered with the same registrar or hosting provider. Ongoing re‑scanning with multi‑engine services is recommended to capture any evolving malicious components.
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.
1Location describes the IP network.
b4962f140d9dedb9595c2367603295a74627c9b2c77634e7912ef2fb9c466995Saved 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 brightonbitcore.digital · checked Mar 2, 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.
content_divergence · unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='brightonbitcore.digital', port=80): Max retries exceeded with url: / (Caused by NewConnect
brightonbitcore.digital
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
Accessible→Indisponible
Accessible→Indisponible
5/90 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcebrightonbitcore.digital
View sourceSignalé par 1 membre de la communauté ; première observation le 02/08/2025
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 ↗
brightonbitcore.digital)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.