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; 21 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 您是否受到本网站的影响?
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。