VirusTotal
3 / 91 engine detections
Buka laporan“DamnBruh”
Analysis of www.damnbruh.net indicates this domain was actively flagged as a wallet/seed phishing threat prior to being taken offline on July 25, 2026.
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
3 / 91 engine detections
Buka laporanno community references
Buka laporanprovider verdict: clean
Buka laporanNo threat flag
Buka laporanNo malicious flag
Buka laporanResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
Analysis of www.damnbruh.net indicates this domain was actively flagged as a wallet/seed phishing threat prior to being taken offline on July 25, 2026. The domain, registered through Tucows Domains Inc. on August 27, 2025, resolved to a Cloudflare-hosted IP (172.67.142.163, AS13335) in the United States. No SSL certificate was present at the time of assessment, and the page title was recorded as 'DamnBruh,' offering no explicit branding or target identification beyond the scam classification. Two of 95 security vendors on VirusTotal flagged the domain, and it appeared on one security blocklist, reinforcing its elevated risk designation.
Infrastructure analysis reveals Cloudflare nameservers (amalia.ns.cloudflare.com, neil.ns.cloudflare.com) were in use, a common pattern among phishing domains leveraging CDN services for anonymity and resilience. The domain's trust score from Gridinsoft was 0/100, and it was blocked by PhishDestroy, though no additional details about the specific phishing kit or targeted wallet services were provided in available intelligence. The exact content of the phishing page remains unanalyzed, as the domain is currently offline. Defenders should treat this domain as confirmed malicious for wallet/seed phishing activity.
Given its prior status and detection history, any residual DNS or cached resolutions should be blocked at the network level. If the domain reappears under the same or similar infrastructure (e.g., Cloudflare hosting, lack of SSL), it should be reassessed for continued threat activity. No further action is required for offline domains unless new resolutions or detections emerge.
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.
Reputasi Edge-IP tidak dikaitkan dengan domain ini.
amalia.ns.cloudflare.comneil.ns.cloudflare.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-4800.invalid', port=80): Max retries exceeded with url: / (Caused by Ne
duplicate-disabled-4800.invalid
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Dapat dijangkau→Tidak tersedia
3/91 engine detections
View sourcePage captured
View sourceNo threat flag
View sourceduplicate-disabled-4800.invalid
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
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-4800.invalid)Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.
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
Analisis ancaman menggunakan daftar blokir yang disimpan, WHOIS, DNS, dan bukti pemindaian publik
Pindai SekarangLaporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas
LaporanLaporan phishing terbaru dan perubahan ketersediaan yang diamati
PantauPantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive
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.