VirusTotal
2 / 91 engine detections
Raporu aç“Dashboard - BotPanel (Beta)”
Discord taklidi: discordbot.website — Bilinen son aktif (HTTP 200). Kanıt özeti: VirusTotal 2/91 (Chong Lua Dao, Gridinsoft); PhishDestroy score 81/100. Kayıt…
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
2 / 91 engine detections
Raporu aç16 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
The domain discordbot.website is currently hosting a web page that returns HTTP 200 and presents the title “Dashboard - BotPanel (Beta)”. The site presents a valid TLS certificate issued by Google Trust Services under the WE1 intermediate, indicating that transport encryption is correctly configured. Network resolution points to the address 104.21.19.237, which is owned by Cloudflare, Inc. and geolocated to the United States (CA). The domain was registered on May 07, 2026 through Cloudflare, Inc. and uses the authoritative name servers huxley.ns.cloudflare.com and ligia.ns.cloudflare.com. Reputation services assign a Gridinsoft trust score of 0 out of 100 and the domain appears on a single security blocklist. Threat intelligence sources note that the domain is listed in one AlienVault OTX pulse and has been flagged by the PhishDestroy blocklist. The current risk level is marked as under investigation, and the designation of generic_phishing suggests that the site is being used to harvest credentials, although no specific phishing kit or compromised accounts have been publicly disclosed. Defenders should treat discordbot.website as malicious and enforce blocking at network perimeter and endpoint controls. Continuous monitoring of DNS queries for the domain and its associated IP address is advised, as is the use of sinkholing or URL filtering to prevent user interaction. Incident response teams should collect any payloads or network traffic associated with visits to the site for further forensic analysis.
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.
ligia.ns.cloudflare.comLocation describes the IP network.
572116ff7c52f2fc783e41e8b55bd3d5c4faac7dda4345ca873950c983d192daSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
discordbot.website
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
No threat flag
View source2/91 engine detections
View source16 community references
View sourcediscordbot.website
View source1 topluluk üyesi tarafından bildirildi; ilk görülme 07.05.2026
Listed 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 ↗
discordbot.website)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.