VirusTotal
3 / 90 engine detections
Raporu aç“404: NOT_FOUND”
This domain, www.fisch.club, is currently flagged as a high-risk generic phishing threat.
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
3 / 90 engine detections
Raporu açno community references
Raporu açprovider verdict: clean
Raporu açNo threat flag
Raporu açPage capture
Raporu açResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This domain, www.fisch.club, is currently flagged as a high-risk generic phishing threat. Registered on September 7, 2025, through Hosting Concepts B.V. d/b/a Registrar.eu, the domain remains active as of July 12, 2026. Infrastructure analysis reveals it resolves to the IP address 64.29.17.65, hosted on Amazon.com, Inc.'s network (AS16509) in the United States. The domain is associated with nameservers ns1.dns-parking.com and ns2.dns-parking.com, a configuration often observed in domains linked to malicious activity due to its use of low-cost or bulk DNS services. The domain lacks an SSL certificate, which is atypical for legitimate websites but common among phishing domains aiming to evade detection or reduce operational costs. A 404: NOT_FOUND page title was observed, indicating either a placeholder state, a takedown of the malicious content, or a deliberate attempt to mislead automated scanning tools. Despite this, the domain returns an HTTP 200 status code, suggesting the server is operational and may still host or redirect to malicious content. It appears on one security blocklist and is flagged by four out of ninety-five security vendors on VirusTotal, though the absence of further detections does not imply safety. Defenders should treat this domain as an active threat. The combination of a recent registration, lack of SSL, use of parking-style nameservers, and minimal blocklist presence suggests it may be part of a larger, low-profile phishing campaign. Network-level blocking is recommended for organizations, particularly those with exposure to generic credential-harvesting attacks. Monitoring for changes in the domain's behavior, such as the deployment of SSL certificates or alterations in page content, is advised. Given the domain's current state, the exact phishing target or method remains unconfirmed, but the infrastructure aligns with known phishing patterns.
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.
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.
Edge-IP itibarı bu etki alanıyla ilişkilendirilmez.
ns1.dns-parking.comns2.dns-parking.comLocation describes the IP network.
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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-7054.invalid', port=80): Max retries exceeded with url: / (Caused by Ne
duplicate-disabled-7054.invalid
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Erişilebilir→Mevcut değil
3/90 engine detections
View sourcePage captured
View sourceNo threat flag
View sourceduplicate-disabled-7054.invalid
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 ↗
duplicate-disabled-7054.invalid)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.