Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@name.com.
The latest stored availability evidence still shows the domain reachable; 4 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
rblx[.]foo
Verifica phishing e sicurezza per rblx.foo
“Kyxn Dev — Developer Platforms & APIs”
rblx.foo — Ultimo attivo conosciuto (HTTP 303). Simulazione del marchio: Facebook; Tipo di truffa: Social Media Phishing. Riepilogo delle prove: VirusTotal 11/91 (ADMINUSLabs, Criminal IP, alphaMountain.ai, BitDefender, ESET); URLQuery 4 alerts; PhishDestroy score 97/100. Registrar: Name.com.
L’analisi dettagliata di PhishDestroy AI resta in inglese per preservare il rapporto forense originale.
Riepilogo delle prove
PhishDestroy first observed rblx.foo on Mar 16, 2026. Stored content metadata identifies Facebook as the apparent target. The captured page title is “Kyxn Dev — Developer Platforms & APIs”. Evidence score: 97/100 (critical).
3 independent sources recorded positive findings: VirusTotal, DNS security resolvers, and URLQuery. VirusTotal recorded 11 detections among 91 engines: ADMINUSLabs, Criminal IP, alphaMountain.ai, BitDefender, ESET, Fortinet, G-Data, Gridinsoft on Jul 28, 2026 at 02:24 UTC. DNS security checks returned 6 blocking results across 14 tested policies: Adguard Default, Adguard Family, Control D Adblock, Control D Family, Control D Malware, Quad9 Secure; no observation timestamp was retained. URLQuery recorded 4 threat-system alerts on Mar 16, 2026 at 12:16 UTC.
HTTP 303 was recorded on Aug 9, 2026 at 02:27 UTC. Registration records for the domain list Name.com, Inc. as the registrar and Mar 3, 2026 as the creation date. At collection time, the hostname resolved to 34.111.179.208 on AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US). The evidence archive retains 3 visual captures from PhishDestroy, URLScan, and URLQuery.
Copertura dei dati12 recorded checks
Informazioni sulla sicurezza di rete
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| OpenDNS | rblx.foo |
phishing | Phishing Block |
| Hagezi Threat Feed | rblx.foo |
malicious | Sinkholed |
| DNS4EU | rblx.foo |
malicious | Sinkholed |
| Quad9 DNS | rblx.foo |
malicious | Sinkholed |
Pipeline di risposta alle minacce
Stato della lista di blocco pubblica
Acquisizione salvata
Analisi dei domini
Dettagli tecniciDNS, SAN SSL, timestamp
ICANN OVERSIGHT
Accreditamento e contesto RAA
Accreditamento e contesto RAA
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Tecnologie · 6 identified
JavaScript runtime built on Chrome V8 engine for server-side development.
Suite of cloud computing services running on Google infrastructure.
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
Content delivery network built on Google global edge infrastructure.
Third major version of HTTP protocol, built on QUIC for faster, more reliable connections.
Analisi di VirusTotal
Analisi delle prestazioni del sito
Google PageSpeed Insights — mobile performance audit of rblx.foo · checked Mar 16, 2026
Analisi della configurazione del sito
Dati e relazioni esterneIndependent lookups and source reports
PD-20260316-1D2F56 Recipient: abuse@name.com Victim safety and official reportingImmediate actions and verified reporting channels
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.
Segnalalo alle autorità locali
Seleziona il tuo Paese per ottenere contatti ufficiali del crimine informatico o creare una bozza di reclamo →.