Ir para o relatório de segurança
Segurança de domínio e inteligência contra ameaças
bringjp37.icu favicon

bringjp37.icu

“403 Forbidden”

Registrador
Gname
Resolved IP
43.160.212.119
Registered
06/01/2026
PhishDestroy assessment Crítico
Disponibilidade Conteúdo indisponível O conteúdo estava indisponível na última observação Observado · HTTP probe
Detecções do VirusTotal: 11/89 Tipo de golpe: Impersonation
11/09/2026
API
Este domínio foi sinalizado como malicioso
Mecanismos de segurança relatando uma detecção: 11. Tenha extremo cuidado – não insira credenciais ou informações pessoais.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Resumo do relatório

Phishing: bringjp37.icu — Conteúdo indisponível. Resumo das evidências: VirusTotal 11/89 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker)…

A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.

Source evidenceVirusTotal 11 / 89 5 sources

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Crítico
VirusTotal
11 / 89
Page captures
2

PhishDestroy threat report

Overview

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.

How the scam works

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.

Evidence

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.

Infrastructure

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.

What to do

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.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Captura armazenada · 2 captures

Observed page title
403 Forbidden
Certificado TLS
Emitido por Let's Encrypt / YE1 · stored validity ends in 50 days

Domain details

Domínio
URLScan verdict Análise concluída score 0 report ↗
Reputação do IP abuse score 0/100 0 reports checked 11/09/2026
Registrador Gname SG(SG)
RegistroCriado 06/01/2026 (287d)
Tempo até a primeira indisponibilidade 5 days
O que contabilizamos Tempo decorrido desde a primeira denúncia de abuso armazenada até a primeira observação de que o conteúdo estava indisponível. Isto não estabelece a causa.
O que cada relatório contém Os registros de relatórios de saída armazenados podem fazer referência a evidências disponíveis no momento, como veredictos de fornecedores, dados de registro, detalhes de hospedagem, classificações ou capturas de tela. Esta página não infere a carga exata entregue, recebimento, confirmação ou ação de um destinatário.
Detalhes técnicosProvenance & timestamps
Detectado pela primeira vez11/09/2026
DOM Analysisanalyzed 12/09/2026score 73/100
Submitted URLhttp://bringjp37.icu/JeremyTemple
Favicon Hash
ZONA SHORTDOT · EVIDÊNCIAS PÚBLICAS .icu

ShortDot zone evidence

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.

ShortDot SA · Luxembourg 7 zonas · evidências das zonas completas atualizadas diariamente Abrir o repositório de evidências da ShortDot (GitLab)
ICANN OVERSIGHT

Credenciamento e contexto RAA

Registrar accreditation and DNS abuse obligations

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.

Accreditation is a contract, not a safety certification.

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.

Accountability draft Nada é enviado automaticamente.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
43.160.212.119
Network ASN
AS132203
Organization
Tencent Building, Kejizhongyi Avenue
Observed location
Singapore, SG
Server header
nginx/1.30.0

Location describes the IP network.

Certificado TLS

Issuer
Let's Encrypt / YE1
Valid from
2026-09-11 01:38:25
Valid until
2026-12-10 01:38:24
Validity
Within stored validity dates
Collection time
2026-09-11 22:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint9cd7031c35c01926209daaad2f4877425c00690b9d600e2c4681ef412c8821e5

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

Latest Classified Outcome 2026-10-20 08:21:37 UTC

Primary outcome DNS inativo reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Desconhecido Probe Inconclusive 20% 2026-10-19 01:15:19 UTC
RDAP registration Desconhecido
Observed timeline last reachable: 2026-09-15 22:17:51 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-09-15 22:17:51 UTC → 2026-09-30 16:14:55 UTC · 353.95h midpoint estimate ≈ 2026-09-23 07:16:23 UTC · precision low · basis bounded
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.
Tecnologias · 1 identified
Detected via Cloudflare Radar · Wappalyzer engine
Denunciar este domínio Envie evidências e ajude a proteger outras pessoas

Análise do VirusTotal

11 / Os fornecedores de segurança 89 sinalizaram este domínio
View on VT
Last analyzed
alphaMountain.ai
BitDefender
CRDF
ESET
Forcepoint ThreatSeeker
G-Data
Gridinsoft
LevelBlue
SOCRadar
Sophos
Webroot
Análise de desempenho do site

Google PageSpeed Insights — mobile performance audit of bringjp37.icu · checked Sep 11, 2026

100
Good
Performance
FCP
0.79s
First Contentful Paint
LCP
0.79s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.86s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
353.95
Estimate basis
Bounded by observations
Estimate precision
Low

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

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

bringjp37.icu
Resultado salvo
Inacessível
Stored observation history11

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

    Desconhecido→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

Earlier observations 6
  1. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    Acessível→Indisponível

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. URLScan

    Page captured

    View source
  3. VirusTotal

    11/89 engine detections

    View source
  4. Added to PhishDestroy

    bringjp37.icu

    View source

Evidências e relatórios externos

Análise aprofundada
Help & reporting

Você foi afetado por este site?

3 evidence signal groups linked 0 stored notification records Conteúdo indisponível

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

Se você inseriu credenciais de conta, informações pessoais ou de pagamento, ou baixou um arquivo deste domínio, tome medidas imediatas. Abaixo estão os recursos para ajudá-lo a relatar o incidente e se proteger.

Official reporting routes

Cuidado com os golpistas que prometem recuperação! Os criminosos podem entrar em contato novamente com as vítimas fingindo ser investigadores, advogados ou agentes de recuperação. Não pague taxas antecipadas nem compartilhe credenciais. Saiba mais sobre fraudes relacionadas à recuperação →

Notifique as autoridades locais

Selecione seu país para obter contactos oficiais do cibercrime ou crie um rascunho de reclamação →.

Diretório de 97 países

Template-based draft · optional AI wording assistance requires separate consent

Rascunho assistido por IA – os detalhes do incidente são processados pelo provedor de IA · Revise e envie você mesmo
After a phishing incident

Recomendações e orientações para as vítimas

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

O que devo fazer agora mesmo?

Urgente

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Alterar todas as senhas — e-mail, contas do Exchange, qualquer coisa que use a mesma senha
  • Ativar a autenticação de dois fatores usando um aplicativo autenticador (não por SMS). Desative a recuperação por SMS
  • Cartões de congelamento se você inseriu dados bancários no site de phishing

Que informações devo coletar para o meu relatório?

Diretrizes do 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.
  • Datas e horários exatos — de cada transação e do primeiro contato com o golpista
  • Capturas de tela — sites fraudulentos, mensagens de bate-papo, e-mails, transações em carteiras digitais, redes sociais
  • Todas as URLs e domínios utilizado pelo golpista (incluindo bringjp37.icu)
  • Comunicações — e-mails, mensagens de texto, números de telefone e nomes de usuário que o golpista utilizou

Mesmo que você não tenha todos os detalhes — registre uma ocorrência mesmo assim. Mesmo informações parciais ainda ajudam nas investigações.

A quem devo denunciar o golpe?

  • FBI IC3 — Centro de Denúncias de Crimes na Internet (sistema federal de denúncias dos EUA)
  • Europol — Relatórios sobre crimes cibernéticos na Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Polícia local — cria um registro oficial, mesmo que não possam agir imediatamente

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?

  • Sites falsos — clones idênticos, até o último pixel, de sites legítimos, com domínios ligeiramente alterados
  • Abate de suínos — confiança construída ao longo de semanas pelo Telegram, WhatsApp e aplicativos de namoro; em seguida, o dinheiro foi roubado
  • Golpes relacionados à recuperação — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Golpes baseados em IA — deepfakes, phishing automatizado e sites gerados por IA, o que torna a fraude mais difícil de detectar

Como posso me proteger no futuro?

  • Adicione os sites oficiais aos favoritos — nunca clique em links de e-mails, mensagens diretas ou anúncios
  • Verificar domínios — verificar PhishDestroy antes de interagir. Verifique se o site usa HTTPS, a ortografia e a idade do domínio
  • "Bom demais para ser verdade" = golpe — retornos garantidos, endossos de celebridades, prazos urgentes

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Mantenha-se informado, mantenha-se seguro

Monitore ameaças em tempo real ou conteste esta listagem caso acredite que se trate de um falso positivo

Feed de ameaças em tempo real Recorrer deste anúncio
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Incorporar este relatório

Compartilhe essas informações sobre ameaças em seu site ou blog

embed.html
<iframe
  src="https://phishdestroy.io/pt-br/embed/domain/bringjp37.icu"
  title="PhishDestroy threat report for bringjp37.icu"
  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>