VirusTotal
19 / 92 engine detections
Buka laporan“Steam Community”
Peniruan Counter-strike: frytt.dev — Terakhir diketahui aktif (HTTP 200). Ringkasan bukti: VirusTotal 19/92 (alphaMountain.ai, BitDefender, CRDF, CyRadar…
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
19 / 92 engine detections
Buka laporanBerbahaya
Buka laporanBerbahaya
Buka laporanScan report
Buka laporanno community references
Buka laporanNo threat flag
Buka laporanResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy has placed frytt.dev on its internal blocklist as a suspicious domain. The domain was first observed by PhishDestroy on 2026-10-19. No page title was recorded for the site. Google Safe Browsing checked the domain on 2026-10-19 and did not flag it. An external blocklist, OpenPhish, also listed the domain as of the same date.
The current evidence does not point to a specific malicious mechanism. Suspicious domains like this can be used for phishing, credential harvesting, or fraud, but no particular behavior has been observed on frytt.dev. Without a concrete classification, the risk remains undefined and should be treated with caution.
VirusTotal retrieved on 2026-10-19 reported 19 detections out of 92 scanning engines, with vendors such as alphaMountain.ai, BitDefender, CRDF, CyRadar, Ermes, ESET, Emsisoft and Forcepoint ThreatSeeker flagging the site. Google Safe Browsing reported no threat on the same date. OpenPhish listed the domain, giving one external blocklist count. PhishDestroy’s internal list also includes frytt.dev. OTX showed zero pulses as of 2026-10-19.
The domain was registered on 2026-10-16 through Name.com, Inc. The recorded IP address is 88.80.135.136. The domain was observed three days after registration. No further network or hosting details are available.
If you visited the site, avoid entering any credentials or personal information and monitor accounts for unexpected activity. Change passwords for any services where credentials may have been submitted. Security teams should add frytt.dev to blocklists, review access logs for connections to the recorded IP, and apply standard web‑filtering policies to this exact address.
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.
ns1bqx.name.comns2glx.name.comns3fqs.name.comns4ksy.name.comLocation describes the IP network.
71fa946bf5aa814625c4780924419386beb5442f3dcfa467163df4f54909566ewww.frytt.devSaved 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.
www.frytt.devDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of frytt.dev · checked Oct 19, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://frytt.dev/Server: nginxContent-Type: text/html; charset=utf-8Cache-Control: no-cacheContent-Encoding: gzip607ea6e6883404c7f835e4e270d4d46036c72fe0e7cfee4edc7323bf3f7b3319no-cachekeep-alivegziptext/html; charset=utf-8Mon, 19 Oct 2026 18:30:51 GMTnginxchunkedUser-AgentbrowserValues 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.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Tidak diketahui→live_content
content_served
Dapat dijangkau
PD-20261019-0D5110
Page captured
View sourceNo threat flag
View source19/92 engine detections
View sourcefrytt.dev
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
frytt.dev
PD-20261019-0D5110 Recipient: abuse@name.com 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 ↗
frytt.dev)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.