Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@namecheap.com.
The latest stored availability evidence still shows the domain reachable; 19 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
securealliance[.]xyz
“securealliance.xyz is registered at Namecheap”
securealliance.xyz — 未検証. 証拠の概要: VirusTotal 12/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. レジストラ: Namecheap.
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
The domain securealliance.xyz was registered on July 23, 2026 through NameCheap, Inc. and is currently delegated to the authoritative servers dns1.registrar-servers.com and dns2.registrar-servers.com. DNS resolution points the name to the IPv4 address 192.64.119.104, which remains active as of the report date (July 25, 2026). The domain is listed on a single public security blocklist and has been actively blocked by the PhishDestroy sinkhole network. VirusTotal scans show that two of ninety‑one submitted security engines flagged the domain as malicious, indicating that at least a subset of detection products recognize it as a credential‑phishing threat.
No additional intelligence such as Safe Browsing status, OTX tags, SSL certificate details, or HTTP response codes is available in the current dataset, and the page title or landing‑page content has not been captured, leaving the exact phishing lure unspecified. Analysis of the available infrastructure suggests a typical low‑cost phishing deployment: a recently created domain, a generic registrar, and a single IP address that is not presently associated with known legitimate services. The limited detection coverage (2/91) implies that many AV or URL‑filtering products may still allow traffic to the site, increasing exposure risk. Defenders should proactively deny outbound connections to 192.64.119.104 and add securealliance.xyz to local DNS blocklists or firewall deny lists.
Continuous monitoring of the IP address for new host changes or additional domain registrations from the same nameservers is advised. Organizations employing email security gateways should ensure that credential‑phishing signatures are up‑to‑date, and incident response teams should be prepared to investigate any credential submissions that reference the securealliance.xyz domain.
ネットワークセキュリティインテリジェンス
脅威対応 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.
VirusTotalによる分析
証拠および外部報告書
“Phishing website!”
PD-20260725-E13450 Recipient: abuse@namecheap.com このサイトによって何か影響を受けましたか?
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
お住まいの地域の当局へ報告してください
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
任意のドメインを確認する
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャンフィッシングを報告する
不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポートリアルタイム脅威情報フィード
最近のフィッシングレポートと観察された可用性の変化
監視最新情報を入手し、安全を確保しましょう
リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください