fortnite.my.id returned HTTP status 502 in the check recorded on 2026-10-01, a dated response that describes only that request. The same domain was first observed on 2026-09-19, according to the recorded observation timeline.
Recorded Evidence
The HTTP check recorded on 2026-10-01 produced status 502 for fortnite.my.id. VirusTotal, checked on 2026-09-26, reported 5 detections across 91 scanners. OTX, checked on 2026-09-20, listed 4 pulses. The PhishDestroy internal listing was recorded as true. An SSL scan on 2026-09-19 named Let's Encrypt / YR2 as the issuer, and a PageSpeed check that same date returned a performance score of 72.
Interpretation
The named sources measure different things on different dates, so their values should be read separately rather than combined. The HTTP response, VirusTotal detections, OTX pulses and PhishDestroy listing each describe a distinct recorded observation, and the shared or adjacent dates do not establish that they were captured together. The chronology from first observation to the later checks is useful for ordering records, not for asserting a trend.
Recommended Actions
For fortnite.my.id, preserve the HTTP check record, the VirusTotal result, the OTX pulses and the PhishDestroy listing as separate source records. Compare the HTTP response record against the VirusTotal and OTX records in separate reviews, since each captures a different measurement. Re-check the domain's HTTP response and retain the new result alongside the existing records for later comparison.
Analisis deteksi dan penghindaran
Pemeriksaan penyamaran dan distribusi lalu lintas
Belum dipindaiBelum ada perbedaan yang tercatat antara crawler dan browser
Data pengamatan perbandingan crawler versus browser yang telah disimpan untuk host ini, ditambah pemeriksaan sidik jari secara real-time untuk sistem distribusi lalu lintas bergaya Keitaro.
Bendera penyamaran yang tersimpan
Belum dipindai
Pemindaian penyamaran terakhir
Catatan pemindai:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='fortnite.my.id', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
Pemeriksaan sidik jari secara langsung melalui TDS
Tujuh sidik jari Keitaro ditambah perbandingan antara crawler dan browser; jalankan dari pemindai PhishDestroy saat panel ini terbuka.
Yang kami hitung
Waktu yang berlalu sejak laporan penyalahgunaan pertama kali disimpan hingga pengamatan pertama bahwa konten tersebut tidak tersedia. Hal ini tidak dapat menentukan penyebabnya.
Isi setiap laporan
Catatan laporan keluar yang disimpan dapat merujuk pada bukti yang tersedia pada saat itu, seperti keputusan vendor, data pendaftaran, detail hosting, klasifikasi, atau tangkapan layar. Halaman ini tidak menyimpulkan secara pasti muatan yang dikirimkan, penerimaan, pengakuan, atau tindakan oleh penerima.
Detail teknisProvenance & timestamps
Pertama Kali Terdeteksi19/09/2026
DOM Analysisanalyzed 19/09/2026score 88/100
Submitted URLhttps://fortnite.my.id/
Favicon Hash
ID kasus
Judul Halaman
403 · Forbidden — SilkGuard
Sertifikat TLS
Hostname coverage not recorded·
Diterbitkan oleh Let's Encrypt / YR2· stored validity ends in 18 days
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS tidak aktifreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationTidak diketahuiProbe Inconclusive20%2026-10-13 01:32:54 UTC
RDAP registrationTidak diketahui
Observed timelinelast reachable: 2026-09-28 10:01:20 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-28 10:01:20 UTC → 2026-09-30 16:14:55 UTC · 54.23hmidpoint estimate ≈ 2026-09-29 13:08:07 UTC · precision low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Google PageSpeed Insights — mobile performance audit of fortnite.my.id· checked Sep 19, 2026
72
Needs Work
Performance
FCP
4.51s
First Contentful Paint
LCP
4.57s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
76ms
Total Blocking Time
SI
4.51s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-09-28 22:01:08 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-20 10:38:06 UTC
VirusTotal scanner detections updated from 2 to 3. Added scanner alerts: alphaMountain.ai.
VirusTotal Detections Update2026-09-20 02:54:04 UTC
VirusTotal scanner detections updated from 1 to 2. Added scanner alerts: CRDF.
VirusTotal Detections Update2026-09-19 12:51:25 UTC
VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-19 11:49:07 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 109.238.86.76.
Alur Tanggapan Ancaman Pipeline
Penemuan
Analysis
Notifications
Monitoring
17 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Ancaman Telah Diterima
fortnite.my.id telah terdeteksi dan dimasukkan ke dalam antrian untuk analisis menyeluruh
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Pemeriksaan terakhir yang disimpan menunjukkan bahwa konten yang dilaporkan tidak tersedia; ini tidak menentukan siapa atau apa yang menyebabkan perubahan tersebut.
29/09/2026
Waktu hingga pertama kali tidak tersedia
226 jam berlalu dari deteksi hingga observasi pertama yang tidak tersedia.
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
7 evidence signal groups linked1 reports recordedKonten tidak tersedia
If credentials were compromised, report immediately. Do not engage with recovery scammers.
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.
Waspadalah terhadap penipu yang mengatasnamakan pemulihan! Penjahat dapat menghubungi korban lagi sambil berpura-pura menjadi penyelidik, pengacara, atau agen pemulihan. Jangan membayar biaya di muka atau membagikan kredensial.Pelajari lebih lanjut tentang penipuan dalam proses pemulihan →
Laporkan kepada Pihak Berwenang di Daerah Anda
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
Direktori 97 negara
Template-based draft · optional AI wording assistance requires separate consent
Draf yang dibantu AI — detail insiden diproses oleh penyedia AI · Tinjau dan kirimkan sendiri
Infrastruktur dan Laporan Terkait
Hubungan yang disimpan dikelompokkan berdasarkan atribut pencocokan tepat. Penyedia atau registrar bersama saja tidak membuktikan kepemilikan bersama.
Tautan langsung Menggunakan pendaftaran yang sama atau perangkat phishing yang identik.
Sinyal pendukung Berbagi infrastruktur atau merek sasaran; bukan bukti adanya satu operator.
Hanya untuk penemuan Terdaftar untuk navigasi; tidak ada atribut yang sama dengan host ini.
Peta infrastruktur · fortnite.my.id
Setiap jalur merupakan salah satu alasan mengapa sebuah domain terhubung ke host ini. Ukuran node menandai deteksi VirusTotal, sedangkan node bergaris putus-putus menunjukkan bahwa node tersebut sudah offline. Daftar lengkapnya tercantum di bawah ini.
Konten cocok8
Hash favicon yang sama atau judul halaman yang sama dengan host ini.
Didaftarkan melalui penyedia layanan pendaftaran yang sama. Sebuah penyedia layanan pendaftaran melayani jutaan pelanggan yang tidak saling terkait, sehingga hal ini sekadar mengelompokkan laporan-laporan tersebut, bukan membuktikan adanya hubungan.
Laporan 
