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.
Analisi di rilevamento ed evasione
Verifica del cloaking e della distribuzione del traffico
Non ancora scansionatoNon è stata ancora rilevata alcuna differenza tra crawler e browser
Osservazioni archiviate relative al confronto tra crawler e browser per questo host, oltre a una verifica in tempo reale delle impronte digitali per i sistemi di distribuzione del traffico in stile Keitaro.
Flag di occultamento memorizzato
Non ancora scansionato
Ultima scansione di occultamento
Nota dello scanner: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(
Verifica delle impronte digitali in tempo reale TDS
Sette impronte digitali di Keitaro più un confronto tra crawler e browser, eseguiti dallo scanner PhishDestroy quando questa finestra è aperta.
Cosa conteggiamo
Tempo trascorso dalla prima segnalazione di abuso archiviata alla prima osservazione che il contenuto non era disponibile. Ciò non ne stabilisce la causa.
Cosa contiene ogni rapporto
I record archiviati dei report in uscita possono fare riferimento a prove disponibili in quel momento, come verdetti dei fornitori, dati di registrazione, dettagli di hosting, classificazioni o screenshot. Questa pagina non deduce l'esatto carico utile consegnato, la ricevuta, la conferma o l'azione da parte di un destinatario.
Dettagli tecniciProvenance & timestamps
Rilevato per la prima volta19/09/2026
DOM Analysisanalyzed 19/09/2026score 88/100
Submitted URLhttps://fortnite.my.id/
Favicon Hash
ID del caso
Titolo della pagina
403 · Forbidden — SilkGuard
Certificato TLS
Hostname coverage not recorded·
Emesso da Let's Encrypt / YR2· stored validity ends in 19 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 inattivoreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationSconosciutoProbe Inconclusive20%2026-10-11 01:32:15 UTC
RDAP registrationSconosciuto
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.
Pipeline di risposta alle minacce
Scoperta
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.
Minaccia rilevata
fortnite.my.id rilevati e inseriti in coda per un’analisi completa
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.
Gli ultimi controlli memorizzati indicano che il contenuto segnalato non è disponibile; questo non stabilisce chi o cosa ha causato il cambiamento.
29/09/2026
Tempo fino alla prima indisponibilità
226 ore trascorse dal rilevamento alla prima osservazione non disponibile.
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 recordedContenuto non disponibile
If credentials were compromised, report immediately. Do not engage with recovery scammers.
Se hai inserito credenziali dell'account, informazioni personali o di pagamento oppure hai scaricato un file da questo dominio, agisci immediatamente. Di seguito sono riportate le risorse per aiutarti a segnalare l'incidente e proteggerti.
Attenzione ai truffatori che promettono il recupero dei fondi! I criminali possono contattare nuovamente le vittime fingendo di essere investigatori, avvocati o agenti di recupero. Non pagare commissioni anticipate né condividere credenziali.Scopri di più sulle frodi relative ai sussidi di recupero →
Template-based draft · optional AI wording assistance requires separate consent
Bozza assistita dall'intelligenza artificiale: i dettagli dell'incidente vengono elaborati dal fornitore di intelligenza artificiale · Controllalo e invialo tu stesso
Infrastruttura e rapporti correlati
Le relazioni archiviate sono raggruppate in base all'attributo di corrispondenza esatta. Un fornitore o un registrar condiviso da solo non dimostra la proprietà comune.
Link diretto Condivide una registrazione o un kit di phishing identico.
Segnale di supporto Condivide l'infrastruttura o un marchio di riferimento; non costituisce prova della presenza di un unico operatore.
Solo per la scoperta Elencato ai fini della navigazione; nessun attributo in comune con questo host.
Mappa delle infrastrutture · fortnite.my.id
Ogni riga rappresenta un motivo per cui un dominio è collegato a questo host. I nodi a dimensione intera indicano rilevamenti di VirusTotal, mentre quelli tratteggiati sono già offline. Di seguito è riportato l'elenco completo.
Risultati corrispondenti8
Stesso hash della favicon o stesso titolo della pagina di questo host.
Registrati tramite lo stesso registrar. Un registrar serve milioni di clienti non collegati tra loro, quindi questo dato indica semplicemente un raggruppamento piuttosto che dimostrare un nesso.
Segnala 
