MALICIOUS — CRITICAL
joinmeetings[.]live
joinmeetings.live was registered on 27 April 2026 through NameCheap, Inc.
- VirusTotal
- 4/91
- Blocklists
- 2 · MetaMask, SEAL
- 可用性
- 最後に確認されたアクティブな状態 · HTTP 200
Do not enter credentials, seed phrases, payment details, or personal information on this domain.
Jump to section
joinmeetings.live — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 4/91 (alphaMountain.ai, CRDF, Gridinsoft, SOCRadar); 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 83/100. レジストラ: NameCheap.
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
Evidence Analysis
joinmeetings.live was registered on 27 April 2026 through NameCheap, Inc. The domain uses Namecheap’s default parking nameservers dns1.namecheaphosting.com and dns2.namecheaphosting.com and resolves to the IPv4 address 198.54.116.159, which geolocates to the United States and is owned by Namecheap, Inc. An SSL certificate issued by Sectigo Limited (Sectigo Public Server Authentication CA DV R36) is present and the HTTP response code is 200, with the page title reported as "Namecheap Parking Page". MX records include mx1-hosting.jellyfish.systems (priority 5) and an additional record with priority 10 whose host field is incomplete in the current data set. The domain is listed on three security blocklists and has a Gridinsoft trust score of 0/100. AlienVault OTX references the domain in one threat pulse. A VirusTotal scan involving 91 vendors returned no detections, but this result does not confirm the domain’s safety. The overall risk rating is high and the domain remains active. Analysts should continue to monitor DNS and hosting changes, enforce blocklist updates, and consider sinkhole or takedown actions if malicious activity is observed. Defensive teams should treat any traffic to joinmeetings.live as potentially malicious and block it at perimeter or endpoint controls until further investigation clarifies its intent.
データの網羅性13 recorded checks
脅威対応 Pipeline
公開ブロックリスト登録状況
ドメイン・インテリジェンス
技術的な詳細DNS、SSL SAN、タイムスタンプ
ICANN OVERSIGHT
認定と RAA の背景
認定と 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.
脅威情報の照合 · source references
VirusTotalによる分析
証拠および外部報告書Independent lookups and source reports
Victim safety and official reportingImmediate actions and verified reporting channels
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
お住まいの地域の当局へ報告してください
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。