PhishDestroy first observed duplicate-disabled-401596.invalid on Aug 9, 2026. Stored page analysis classifies the content as impersonation. Campaign clustering links the hostname to the Unknown kit. Current evidence score: 90/100 (critical).
Positive findings are stored from 3 sources: VirusTotal, Spamhaus DBL, and URLQuery. VirusTotal recorded 8 detections among 89 engines: alphaMountain.ai, BitDefender, Chong Lua Dao, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, SOCRadar on Sep 21, 2026 at 02:06 UTC. Spamhaus DBL: DBL_PHISH on Sep 9, 2026 at 02:30 UTC. URLQuery recorded 2 threat-system alerts on Aug 9, 2026 at 21:40 UTC. Additional recorded evidence: AlienVault OTX listed 4 community pulse references (not vendor detections) on Aug 21, 2026 at 06:57 UTC.
Latest classified outcome: unknown; cause probe inconclusive on Oct 10, 2026 at 23:30 UTC. Registration records for the domain list Dynadot, LLC as the registrar and Aug 7, 2026 as the creation date. Registration preceded first observation by 2 days. At collection time, the hostname resolved to 130.12.180.128 on AS202412 (Omegatech LTD). The recorded endpoint location is Amsterdam, NL. The stored server header is openresty. DOM analysis on Aug 9, 2026 at 22:20 UTC returned 88/100. The evidence archive retains 3 visual captures from PhishDestroy, URLScan, and URLQuery; the captures preserve the landing-page appearance. TLS metadata lists YE1 as the certificate issuer; checked Aug 9, 2026 at 22:02 UTC.
The content indicators and 3 positive source findings support the current impersonation classification.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-401596.invalid', port=80): Max retries exceeded with url: / (Caused by
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 01:30:50 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-15 22:18:16 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
技术 · 3 identified
P
PHP
Programming languages
PHP is a general-purpose scripting language used for web development.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-09-25 01:31:08 UTC
Domain state transitioned from alive to dead.
威胁响应 Pipeline
发现
Analysis
Monitoring
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
(US)
