securelinkbank[.]com
securelinkbank.com 网络钓鱼与安全检查
“Wait But Why”
securelinkbank.com — 最后已知的活跃状态 (HTTP 302). 诈骗类型:Credential Phishing. 证据摘要: VirusTotal 14/91 (ADMINUSLabs, alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar); URLQuery 2 alerts; Spamhaus DBL_PHISH; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. 注册商: eNom.
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
证据摘要
PhishDestroy first observed securelinkbank.com on Jun 15, 2026. The captured page title is “Wait But Why”. Stored page analysis classifies the content as credential phishing. Evidence score: 100/100 (critical).
5 independent sources recorded positive findings: VirusTotal, MetaMask, SEAL, Spamhaus DBL, and URLQuery. VirusTotal recorded 14 detections among 91 engines: ADMINUSLabs, alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet on Aug 5, 2026 at 14:42 UTC. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Aug 9, 2026 at 06:20 UTC. Spamhaus DBL: DBL_PHISH on Jul 13, 2026 at 14:36 UTC. URLQuery recorded 2 threat-system alerts on Jun 1, 2026 at 02:40 UTC.
HTTP 302 was recorded on Aug 9, 2026 at 02:28 UTC. Registration records for the domain list eNom, LLC as the registrar and May 14, 2026 as the creation date. At collection time, the hostname resolved to 172.67.135.77 on AS13335 (Cloudflare, Inc.). The evidence archive retains 1 visual capture from URLQuery.
数据覆盖范围12 recorded checks
网络安全情报
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Hagezi Threat Feed | securelinkbank.com |
malicious | Sinkholed |
| DNS4EU | securelinkbank.com |
malicious | Sinkholed |
威胁响应 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 分析
证据与外部报告Independent lookups and source reports
Victim safety and official reportingImmediate actions and verified reporting channels
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。