Security engines reporting a detection: 7. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
https-roblox.com was observed by Google Safe Browsing on 2026-10-07, which flagged it for social engineering threats. The domain was also listed on two external blocklists as of the same date.
Recorded Evidence
On 2026-10-07, Google Safe Browsing identified https-roblox.com with a social engineering threat. The domain appeared on both Phishunt and PhishFeed blocklists as of 2026-10-07. VirusTotal reported 7 detections out of 92 scanners on 2026-10-01. OTX referenced the domain in 4 separate pulses as of 2026-10-07. The registrar was recorded as Dynadot Inc, with a registration date of 2026-09-20.
Interpretation
These source records reflect multiple independent observations of https-roblox.com within a short period. The presence on two blocklists, a Google Safe Browsing flag for social engineering, and several VirusTotal detections indicate that several monitoring services have documented concerns related to this domain. The OTX pulses further show that the domain has attracted attention from threat intelligence contributors.
Recommended Actions
For https-roblox.com, retain the Google Safe Browsing, VirusTotal, Phishunt, PhishFeed, and OTX records for ongoing reference. Compare future scans and blocklist entries to these dated observations to monitor any changes in how the domain is classified.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
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.
Last analyzed Previous stored snapshot: 7 detections
alphaMountain.ai
Chong Lua Dao
CRDF
Forcepoint ThreatSeeker
Fortinet
SOCRadar
Webroot
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of https-roblox.com· checked Oct 7, 2026
100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
0.76s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.76s
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.
Status Check2026-10-07 05:34:34 UTC
Telemetry event observed.
Threat First Observed2026-10-07 05:34:03 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 188.114.97.1.
Threat Response Pipeline
Discovery
Analysis
Monitoring
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
https-roblox.com detected and queued for full analysis
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.
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.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · https-roblox.com
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(US)
