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.
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.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-19 01:15:19 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-15 22:17:51 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-15 22:17:51 UTC → 2026-09-30 16:14:55 UTC · 353.95hmidpoint 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.
技术 · 1 identified
N
Nginx
Web serversReverse proxies
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
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?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(SG)
