VirusTotal
11 / 89 engine detections
Ouvrir le rapport“403 Forbidden”
Hameçonnage: bringjp37.icu — Contenu indisponible. Résumé des preuves: VirusTotal 11/89 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker)…
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
11 / 89 engine detections
Ouvrir le rapportno 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
bringjp37.icu is an impersonation phishing site. It posed as a legitimate service to get visitors to trust it with their credentials or personal details. PhishDestroy first flagged it on 2026-09-11, and it went offline on 2026-09-17. As of 2026-10-19 the domain no longer resolves in DNS, so the site is dead. The page title read "403 Forbidden", a server error message, even though we classified the site as an impersonation phishing page.
Impersonation pages copy the look of a brand people already use, such as its logo, layout and login form. Victims arrive through links in messages, ads or search results. Whatever they type into the fake form goes to the operators, not the real company. That can include usernames, passwords, one-time codes, card numbers or identity details. Attackers then use the stolen access to take over accounts, make purchases or run follow-up fraud against the same person.
On 2026-09-11, 11 of 89 VirusTotal engines marked the domain as malicious. The vendors that flagged it include alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker, G-Data, Gridinsoft and LevelBlue. That is a modest share of engines, but these are several unrelated commercial vendors reaching the same verdict on their own. The domain also appears on the PhishDestroy blocklist.
The domain was registered on 2026-01-06 through Gname.com Pte. Ltd. on the low-cost .icu extension. It sat for about eight months before it was detected, which suggests it was registered in advance and held until a campaign needed it. The server ran on Tencent's network at an address in Singapore. Its certificate was a free, automated one from Let's Encrypt, so the padlock in the browser said nothing about whether the site could be trusted.
If you entered a password on this site, change it now on the real service and on any other account that uses the same password. Then turn on app-based two-factor authentication. If you entered card or bank details, call your bank to block the card and dispute any charges you don't recognize. If you shared identity documents or personal data, expect convincing follow-up phishing that uses those details. Defenders should block the domain, search mail and proxy logs for traffic to it between 2026-09-11 and 2026-09-17, and reset credentials for any users who reached it.
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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.
Location describes the IP network.
9cd7031c35c01926209daaad2f4877425c00690b9d600e2c4681ef412c8821e5Saved 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 bringjp37.icu · checked Sep 11, 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.
bringjp37.icu
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
No threat flag
View sourcePage captured
View source11/89 engine detections
View sourcebringjp37.icu
View sourceListed 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 ↗
bringjp37.icu)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.