VirusTotal
5 / 89 engine detections
Mở báo cáoLừa đảo: jbhuntbrokerage.com — Nội dung không có sẵn. Tóm tắt bằng chứng: VirusTotal 5/89 (Abusix, alphaMountain.ai, CRDF, PhishFort, SOCRadar); Spamhaus…
Phân tích chi tiết của PhishDestroy AI bên dưới được giữ bằng tiếng Anh để bảo toàn hồ sơ pháp chứng gốc.
5 / 89 engine detections
Mở báo cáoDBL_PHISH
3 community references
Mở báo cáoprovider verdict: clean
Mở báo cáo80/100
Mở báo cáoNo threat flag
Mở báo cáoResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
jbhuntbrokerage.com is a domain on the PhishDestroy blocklist whose name pairs "jbhunt" with "brokerage", wording that reads like the brokerage arm of a known freight company rather than a neutral name. PhishDestroy first saw it on 2026-09-15, one day after registration. The site went offline on 2026-09-21 and its DNS was still inactive at the last check on 2026-10-19.
We have not confirmed what the page displayed or which brand it imitated, so we do not assign it a specific scheme. Spamhaus lists the domain as phishing, and several detections point the same way. That points to a page built to collect what a visitor types, such as account logins, contact details or payment and banking information, under a brokerage-style name that invites trust. Domains like this are often handed out in emails or messages that ask the recipient to sign in, confirm an account or update payment instructions.
Five of 89 VirusTotal engines flagged the domain at the 2026-09-23 check: Abusix, alphaMountain.ai, CRDF, PhishFort and SOCRadar. That is a modest count, but it comes from vendors that specialise in phishing and abuse feeds. Spamhaus DBL lists it under its phishing category, and it appears in three AlienVault OTX threat pulses. Taken together, independent sources agree on a phishing risk, although the detection count is not high.
The domain was registered through NameCheap, Inc. on 2026-09-14 and was being tracked within a day, so it had almost no history before it drew attention. It stayed online for roughly a week, from first sighting until it stopped resolving on 2026-09-21. A short life after a fresh registration is common for throwaway domains used in a single phishing push.
If you entered a username or password on this site, change it right away on the real service and on any account that reuses it, then turn on two-factor authentication. If you shared banking details or changed payment instructions after a message that linked here, contact your bank and confirm the change by phone with your counterpart, using a number you already trust. Treat any further emails that reference this domain as hostile. Defenders should block the domain at DNS, proxy and mail gateways and search mail logs for messages that contained it between 2026-09-14 and 2026-09-21.
dns2.registrar-servers.comAn estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Không rõ→dns_inactive
dns_nxdomain
Không rõ→dns_inactive
dns_nxdomain
Không rõ→dns_inactive
dns_nxdomain
Không rõ→dns_inactive
dns_nxdomain
Không rõ→dns_inactive
dns_nxdomain
Không rõ→dns_inactive
dns_nxdomain
Không rõ→dns_inactive
dns_nxdomain
Không rõ→dns_inactive
dns_nxdomain
Không rõ→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
4→5
3→4
Có thể truy cập→Không có sẵn
Có thể truy cập
3 community references
View sourceNo threat flag
View source5/89 engine detections
View sourcejbhuntbrokerage.com
View source1 báo cáo từ cộng đồng
Danh mụcPHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-09-15T02:01:22.218Z.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
jbhuntbrokerage.com
Listed domains receive at least one abuse report; this entry has no retained notification history.
Nếu bạn đã nhập thông tin xác thực tài khoản, thông tin cá nhân hoặc thông tin thanh toán hoặc đã tải xuống tệp từ miền này, hãy hành động ngay lập tức. Dưới đây là các nguồn lực giúp bạn báo cáo vụ việc và bảo vệ chính mình.
Chọn quốc gia của bạn để nhận liên hệ tội phạm mạng chính thức hoặc soạn thảo đơn khiếu nại →.
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 ↗
jbhuntbrokerage.com)Dù bạn chưa nắm rõ tất cả các chi tiết — vẫn nên nộp báo cáo. Ngay cả những thông tin không đầy đủ cũng vẫn có ích cho công tác điều tra.
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
Phân tích mối đe dọa bằng cách sử dụng danh sách chặn được lưu trữ, WHOIS, DNS và bằng chứng quét công khai
Quét ngayHãy gửi các tên miền đáng ngờ đến cơ sở dữ liệu mối đe dọa của chúng tôi — để bảo vệ cộng đồng
Báo cáoCác báo cáo lừa đảo gần đây và những thay đổi về tính khả dụng được quan sát thấy
Theo dõiTheo dõi các mối đe dọa đang diễn ra hoặc phản đối danh sách này nếu bạn cho rằng đây là kết quả báo động sai
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.