Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
SSL certificate is invalid or expired. Issuer: Let's Encrypt
证据摘要
高
VirusTotal
6/91
OTX
2 community refs
URLScan
Stored capture
PhishDestroy first observed duplicate-disabled-505207.invalid on Aug 17, 2026. The captured page title is “Redirecting...”. Stored page analysis classifies the content as impersonation. Current evidence score: 68/100 (high).
One source contains a positive finding: VirusTotal. VirusTotal recorded 6 detections among 91 engines: alphaMountain.ai, Chong Lua Dao, Forcepoint ThreatSeeker, Kaspersky, SOCRadar, VIPRE on Aug 30, 2026 at 02:14 UTC. Additional recorded evidence: AlienVault OTX listed 2 community pulse references (not vendor detections) on Aug 21, 2026 at 22:28 UTC.
Latest classified outcome: unknown; cause probe inconclusive on Oct 12, 2026 at 23:14 UTC. Registration records for the domain list NameSilo, LLC as the registrar. At collection time, the hostname resolved to 172.234.25.42 on AS63949 (Akamai Connected Cloud). The IP and ASN identify shared Akamai edge infrastructure; the origin server is not established by this address. The stored server header is openresty. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists Let's Encrypt as the certificate issuer with validity through Nov 11, 2026; checked Aug 17, 2026 at 10:02 UTC.
Stored content provides classification context alongside the positive source finding.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-505207.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-13 01:14:40 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-08-27 22:16:00 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.
Google PageSpeed Insights — mobile performance audit of duplicate-disabled-505207.invalid· checked Aug 17, 2026
84
Needs Work
Performance
FCP
0.75s
First Contentful Paint
LCP
2.26s
Largest Contentful Paint
CLS
0.287
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.08s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
威胁响应 Pipeline
发现
Analysis
Monitoring
10 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.
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)
PhishDestroy Investigation
