VirusTotal
14 / 91 engine detections
レポートを開く“Sign In”
認証情報フィッシング: team.insure — 未検証. 証拠の概要: VirusTotal 14/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar, Forcepoint ThreatSeeker); Spamhaus DBL_PHISH…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
14 / 91 engine detections
レポートを開くDBL_PHISH
23 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This domain, team.insure, is under investigation for credential theft phishing targeting users of insurance services. Analysis indicates the site mimics legitimate login portals, presenting a 'Sign In' page title to harvest user credentials. No direct association with a specific insurance brand or crypto drainer kit has been confirmed, but the generic login interface aligns with credential harvesting tactics commonly deployed in financial and insurance fraud schemes. Infrastructure analysis reveals the domain was registered on April 21, 2026, through NICENIC INTERNATIONAL GROUP CO., LIMITED. It resolves to the IP address 188.114.97.3 and employs a Let's Encrypt SSL certificate. The domain appears on one security blocklist (PhishDestroy) and is referenced in a single AlienVault OTX threat intelligence pulse. VirusTotal reports 0 detections out of 95 engines, suggesting limited prior flagging. Technologies detected include Cloudflare, Cloudflare Browser Insights, and HTTP/3, which may be leveraged to obfuscate malicious activity or enhance delivery speed. As of the latest assessment, team.insure has been taken offline, reducing immediate exposure risk. However, the domain's recent creation date and use of evasion techniques (e.g., Cloudflare, HTTP/3) warrant continued monitoring. Users who may have interacted with the site are advised to reset credentials for any insurance or financial accounts accessed during the exposure window. Organizations should update blocklists to include this domain and its associated IP to prevent potential reuse of the infrastructure.
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.
Edge-IP の評判はこのドメインに起因しません。
sarah.ns.cloudflare.comLocation describes the IP network.
784a53c3caf39e02ef4806ef72e00fdbfcbe0e63d92746d485f4be561f196ec9Saved 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 team.insure · checked Jun 26, 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.
timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='team.insure', port=80): Read timed out. (read timeout=7)
team.insure
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
6→Observation retained
https://radar.cloudflare.com/scan/abc7097a-fb90-4291-8d7f-2f7b4b5b501d
23 community references
View source14/91 engine detections
View sourceNo threat flag
View sourceteam.insure
View sourceコミュニティの 1 人が報告・初回確認 2026年4月21日
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
team.insure)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.