VirusTotal
7 / 92 engine detections
Raporu aç“com-keysrecovery.com”
Oltalama: com-keysrecovery.com — Bilinen son aktif (HTTP 301). Kanıt özeti: VirusTotal 7/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet…
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
7 / 92 engine detections
Raporu açSuspicious
Raporu açDBL_PHISH
no community references
Raporu açNo threat flag
Raporu açNo malicious flag
Raporu açResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
com-keysrecovery.com is an impersonation phishing page. Its name poses as a wallet key recovery service, and it targets cryptocurrency wallet users who believe they need help restoring access. PhishDestroy first detected it on 2026-10-16, three days after the domain was registered. As of 2026-10-19 the site was still online and redirecting visitors.
The "com-" prefix is a common lookalike trick. In a quick glance or a truncated link it can pass for a subdomain of a legitimate site. Fake recovery pages usually ask for a seed phrase, private key or keystore file and present this as a routine step to restore or verify a wallet. Whoever submits those secrets gives the operator full control of the wallet, and the funds can be drained without any further approval from the victim. The page title shows only the bare domain name and gives no indication of which brand is being imitated.
On VirusTotal, 3 of 92 engines flagged the domain as of 2026-10-16: alphaMountain.ai, Fortinet and Gridinsoft. That count is low, which is typical for a domain only days old, but other sources back the verdict. Spamhaus DBL lists it as DBL_PHISH. It also appears on the PhishDestroy, MetaMask and SEAL blocklists, and the latter two focus specifically on threats to crypto wallet users.
The domain was registered on 2026-10-13 through NICENIC INTERNATIONAL GROUP CO., LIMITED. It resolves to 104.194.158.243 on the RouterHosting LLC network (ROUTERHOSTING), a US-based provider, with the server located in Germany. Its TLS certificate comes from Let's Encrypt (YR2), so the browser padlock shows only that the connection is encrypted, not that the site is legitimate.
If you only opened the page, close it and do not return. If you typed a seed phrase or private key into it, treat that wallet as compromised. Create a new wallet on a trusted device with a fresh phrase, and move any remaining assets there immediately. No genuine wallet provider or recovery service will ever ask for your recovery phrase. Security teams should block the domain and its IP address at DNS and proxy level, and search mail and chat logs for links containing "com-keysrecovery" so they can warn affected users.
Last checked
a.dnspod.comb.dnspod.comc.dnspod.comLocation describes the IP network.
25b20182ba34b9e30d3e95673fc02709b28a2bfc08f11e8344ce8c5a14931697254413.fornex.cloudSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
blockchain.com-keysrecovery.comDomain recordThe original observation time is not recorded for these hostnames.
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://com-keysrecovery.com/Server: nginxContent-Type: text/html; charset=utf-8Content-Encoding: gzipbytesgzip1062text/html; charset=utf-8Fri, 16 Oct 2026 14:24:04 GMT"9d8-639674886e665-gzip"Tue, 08 Jul 2025 09:07:01 GMTnginxAccept-EncodingValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
redirect: raw=redirect_301; http=301; via=https_proxy; location=http://com-keysrecovery.com/; server=nginx
com-keysrecovery.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Bilinmiyor→redirected
http_redirect
Bilinmiyor→redirected
http_redirect
Bilinmiyor→redirected
http_redirect
Bilinmiyor→redirected
http_redirect
Erişilebilir
No threat flag
View source7/92 engine detections
View sourcePage captured
View sourcecom-keysrecovery.com
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
Hesap kimlik bilgilerini, kişisel bilgileri veya ödeme bilgilerini girdiyseniz ya da bu alan adından bir dosya indirdiyseniz hemen harekete geçin. Aşağıda olayı bildirmenize ve kendinizi korumanıza yardımcı olacak kaynaklar bulunmaktadır.
resmi siber suç iletişim bilgileri veya şikayet taslağı oluştur → almak için ülkenizi seçin.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
com-keysrecovery.com)Tüm ayrıntıları bilmeseniz bile — yine de şikayette bulun. Kısmi bilgiler de soruşturmalara yardımcı olmaktadır.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Saklanan engelleme listesi, WHOIS, DNS ve genel tarama kanıtlarını kullanarak tehdit analizi
Şimdi TaraŞüpheli alan adlarını tehdit veritabanımıza bildirin — topluluğu koruyun
BildirSon kimlik avı raporları ve gözlemlenen kullanılabilirlik değişiklikleri
İzleCanlı tehditleri izleyin veya bunun yanlış bir uyarı olduğunu düşünüyorsanız bu kayda itiraz edin
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.