Skip to security report
robuxtime.blogspot.com favicon
Domain security and threat intelligence

robuxtime.blogspot.com

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

The robuxtime.blogspot.com page runs on blogspot.com and asks visitors to input their Roblox account username to claim currency or rewards. If you visited the site and submitted your username, change your Roblox account password immediately and enable two-factor authentication.

Page title: “Roblox - Robux Generator”

More about the sources
Recorded security signals

Stored VirusTotal result: 14/92 engines flagged. Analysis time (as stored): 2026-11-18 04:50 UTC. Retrieved (as stored): 2026-11-20 14:50 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 14/92
Resolved IP
United States142.251.14.132Google LLC
First seen by PhishDestroy
2026-11-20
Page captures
open gallery
2026-11-20

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded robuxtime.blogspot.com on 2026-11-20. Stored VirusTotal result: 14/92 engines flagged. Analysis time (as stored): 2026-11-18 04:50 UTC. Retrieved (as stored): 2026-11-20 14:50 UTC. Risk: critical (evidence score 100/100). Status: Last known active. Hosting: Google LLC. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
14 / 92
Hosting
United States142.251.14.132Google LLC
Page captures
7

URLScan capture · 2026-11-20 14:43 UTC · SHA-256 b75836c6…8e54be0

PhishDestroy analysis, reviewed version

Roblox username harvesting on blogspot.com

The robuxtime.blogspot.com page presents a minimalist interface hosted on the blogspot.com platform, featuring a prominent input field labelled "Your Username..." accompanied by a player icon and an arrow graphic. The layout is designed to mimic official Roblox reward or currency generation tools in order to entice visitors into typing their account identifiers. Visitors are expected to supply their login handle, which typically leads to secondary phishing prompts or account compromise attempts. Because the domain uses free hosting rather than the official roblox.com infrastructure, these elements underline the risk of credential theft.

Security detections and independent analysis

urlscan classified the page as malicious, and 14 of 92 VirusTotal engines flagged it on 18 Nov 2026, with Kaspersky, ESET and BitDefender among the engines identifying the URL as malicious, so this is a known data-collection page rather than a false alarm. PhishDestroy's evidence score for it is 60/100 (high).

Recommended actions for visitors

Anyone who entered their username or password on robuxtime.blogspot.com should immediately secure their Roblox account by changing their password and logging out of all active sessions from the account security settings. Enable multi-factor authentication to prevent unauthorized access if credentials were exposed. Always obtain game currency and promotional items exclusively through the official roblox.com platform rather than third-party subdomains.

Source evidenceVirusTotal 14 / 92 6 sources

VirusTotal

14 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

Source
VirusTotal
Result state
observed
Numerator
14
Denominator
92
Vendors
BitDefender, CyRadar, ESET, Emsisoft, Fortinet, G-Data, Gridinsoft, Kaspersky, LevelBlue, Lionic, Netcraft, Sophos, VIPRE, Webroot
Observed at
2026-11-18 04:50:36
Checked at
2026-11-20 15:50:23
Fetched at
2026-11-20 14:50:24

Gridinsoft

1/100

URLScan

Malicious

SHA-256 d936f6e3…49b2ebf

Open report
URLScanOriginal source recordObserved: 21 fields
Separate monitor record · 2026-11-21 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a1f969-41a3-72f6-bbfd-3f452409e216
Score
100
Malicious
✓
Result at
2026-11-21T04:30:18Z
Enriched at
2026-11-21T09:12:13Z
Source timestamps
Urlscan result at: 2026-11-21 05:30:18; Urlscan enriched at: 2026-11-21 10:12:13

PhishDestroy DOM

15 / 100 · heuristic score · 3 brand references · 0 classifications

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 15 / 100 · 2026-11-20 15:20 UTC

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

Heuristic score
15
Analyzed at
2026-11-20T15:20:08Z
Source timestamp
2026-11-20 16:20:08
Technical metadata

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

AI title
robuxtime.blogspot.com — Roblox currency generator
AI description
robuxtime.blogspot.com hosted a Roblox username entry form on blogspot.com, flagged by urlscan and 14 VirusTotal engines. Do not submit your credentials here.
AI summary
Roblox username harvesting on blogspot.com The robuxtime.blogspot.com page presents a minimalist interface hosted on the blogspot.com platform, featuring a prominent input field labelled "Your Username..." accompanied by a player icon and an arrow graphic. The layout is designed to mimic official Roblox reward or currency generation tools in order to entice visitors into typing their account identifiers. Visitors are expected to supply their login handle, which typically leads to secondary phishing prompts or account compromise attempts. Because the domain uses free hosting rather than the official roblox.com infrastructure, these elements underline the risk of credential theft. Security detections and independent analysis urlscan classified the page as malicious, and 14 of 92 VirusTotal engines flagged it on 18 Nov 2026, with Kaspersky, ESET and BitDefender among the engines identifying the URL as malicious, so this is a known data-collection page rather than a false alarm. PhishDestroy's evidence score for it is 60/100 (high). Recommended actions for visitors Anyone who entered their username or password on robuxtime.blogspot.com should immediately secure their Roblox account by changing their password and logging out of all active sessions from the account security settings. Enable multi-factor authentication to prevent unauthorized access if credentials were exposed. Always obtain game currency and promotional items exclusively through the official roblox.com platform rather than third-party subdomains.
AI generated by
threat-v10-gemini
AI generated at
2026-11-20T15:49:49Z
Revision
06c1f2788221014869e20e1962503e481b248b1816de1ecf7a891eb4cb49e430
Mode
reviewed
Interpretation
Selected public package; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 22 fields

Mail configuration

SPF lookups
0

CAA records

Count
1
Domain
blogspot.com
Allowed issuers
  • pki.goog

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Crawler rules

Allow
  • /
User agents
  • Mediapartners-Google
  • *
Present
Yes
Disallow
  • /search
  • /share-widget
Sitemap URLs
  • https://robuxtime.blogspot.com/sitemap.xml

Page title and metadata

Page title
Roblox - Robux Generator
Indexing directives
noindex,nofollow
Open Graph title
Roblox - Robux Generator

Trackers

Requests
24
Observed services
  • Name
    Amazon CloudFront
    Company
    Amazon
    Country
    US
    Category
    Hosting
    Requests
    16
  • Name
    fontawesome.com
    Company
    fontawesome.com
    Category
    Hosting
    Requests
    1
  • Name
    Google APIs
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    2
  • Name
    Google Analytics
    Company
    Google
    Country
    US
    Category
    Site Analytics
    Requests
    1
  • Name
    Sentry
    Company
    Sentry
    Country
    US
    Category
    Utilities
    Requests
    1

Forms and mixed content

Scripts without SRI
  • https://d34kbf3dt5iqei.cloudfront.net/750f852.js
  • https://d13pxqgp3ixdbh.cloudfront.net/uploads/assets/155941537994074c153d8517ea8b52f5cac84312a8.js
  • https://d13pxqgp3ixdbh.cloudfront.net/uploads/assets/1559362555ec79a5a2f5b81fb62c1408059a6368dc.js
  • https://d13pxqgp3ixdbh.cloudfront.net/uploads/assets/15607272053787c9f516c16e5a1a9288d97413bdb2.js
  • https://ajax.googleapis.com/ajax/libs/jquery/2.2.4/jquery.min.js
Third-party scripts
6

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
0
Waiting
1304
Download
12
Response time, ms
1362

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
67615
CO₂, grams
0.0025
Cleaner than, %
30

DNS servers

Nameservers
  • IP address
    216.239.36.10
    Host
    ns3.google.com
  • IP address
    216.239.32.10
    Host
    ns1.google.com
  • IP address
    216.239.34.10
    Host
    ns2.google.com
  • IP address
    216.239.38.10
    Host
    ns4.google.com
DNS zone
blogspot.com

Page quality

Layout shift (CLS)
0
SEO score
54
First Contentful Paint (FCP), s
3.01
Largest Contentful Paint (LCP), s
8.8
Total Blocking Time (TBT), ms
152
Accessibility score
77
Best practices score
96

Location

IP address
2a00:1450:4001:c21::84
ASN
15169
Organization
Google LLC
City
Frankfurt am Main
Country
DE

TLS certificate

Subject alternative names
  • misc-sni.blogspot.com
  • blogspot.ae
  • *.blogspot.ae
  • blogspot.al
  • *.blogspot.al
  • blogspot.am
  • *.blogspot.am
  • blogspot.ba
  • *.blogspot.ba
  • blogspot.be
  • *.blogspot.be
  • blogspot.bg
  • *.blogspot.bg
  • blogspot.ca
  • *.blogspot.ca
  • blogspot.ch
  • *.blogspot.ch
  • blogspot.cl
  • *.blogspot.cl
  • blogspot.co.at
  • *.blogspot.co.at
  • blogspot.co.id
  • *.blogspot.co.id
  • blogspot.co.il
  • *.blogspot.co.il
  • blogspot.co.ke
  • *.blogspot.co.ke
  • blogspot.co.nz
  • *.blogspot.co.nz
  • blogspot.co.uk
  • *.blogspot.co.uk
  • blogspot.co.za
  • *.blogspot.co.za
  • blogspot.com
  • *.blogspot.com
  • blogspot.com.ar
  • *.blogspot.com.ar
  • blogspot.com.au
  • *.blogspot.com.au
  • blogspot.com.br
  • *.blogspot.com.br
  • blogspot.com.by
  • *.blogspot.com.by
  • blogspot.com.co
  • *.blogspot.com.co
  • blogspot.com.cy
  • *.blogspot.com.cy
  • blogspot.com.ee
  • *.blogspot.com.ee
  • blogspot.com.eg
Key size, bits
256
Certificate chain
  • misc-sni.blogspot.com
  • WE2
  • GTS Root R4
Issuer
Google Trust Services / WE2
Serial
BE9362B229C6A5E7105430FBFB588354
SHA-256
410aa334dd10ce86a20d47f491f7acecd522eb9eb5c9cfa584840c3ad95eef27
Subject
misc-sni.blogspot.com
Valid until
Valid from

DNS records

A
  • 142.251.14.132
AAAA
  • 2a00:1450:4001:c21::84
CNAME
  • blogspot.l.googleusercontent.com

DNSSEC

DS record
Yes
RRSIG
No
DNSKEY
Yes

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
1; mode=block
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2a00:1450:4001:c21::84
IP version
6

Redirects

Redirect chain
  • https://robuxtime.blogspot.com

HTTP headers

Response headers
Server
GSE
Content-Type
text/html; charset=UTF-8
X-Content-Type-Options
nosniff
Original source fields · JSON
Mail configuration
Spf lookups: 0
Caa records
Count: 1; Domain: blogspot.com; Issuers: pki.goog
Protective DNS results
Resolvers: 12; Blocked count: 0
Crawler rules
Allow: /; Agents: Mediapartners-Google, *; Present: ✓; Disallow: /search, /share-widget; Sitemaps: https://robuxtime.blogspot.com/sitemap.xml
Page title and metadata
Title: Roblox - Robux Generator; Robots: noindex,nofollow; Ogtitle: Roblox - Robux Generator
Trackers
Requests: 24; Trackers: (Name: Amazon CloudFront; Company: Amazon; Country: US; Category: Hosting; Requests: 16), (Name: fontawesome.com; Company: fontawesome.com; Category: Hosting; Requests: 1), (Name: Google APIs; Company: Google; Country: US; Category: Hosting; Requests: 1), (Name: Google Fonts; Company: Google; Country: US; Category: Hosting; Requests: 2), (Name: Google Analytics; Company: Google; Country: US; Category: Site Analytics; Requests: 1), (Name: Sentry; Company: Sentry; Country: US; Category: Utilities; Requests: 1)
Forms and mixed content
No sri: https://d34kbf3dt5iqei.cloudfront.net/750f852.js, https://d13pxqgp3ixdbh.cloudfront.net/uploads/assets/155941537994074c153d8517ea8b52f5cac84312a8.js, https://d13pxqgp3ixdbh.cloudfront.net/uploads/assets/1559362555ec79a5a2f5b81fb62c1408059a6368dc.js, https://d13pxqgp3ixdbh.cloudfront.net/uploads/assets/15607272053787c9f516c16e5a1a9288d97413bdb2.js, https://ajax.googleapis.com/ajax/libs/jquery/2.2.4/jquery.min.js; Third party scripts: 6
Status
Up: ✓; Code: 200; Timings: DNS: 0; Wait: 1304; Download: 12; Response ms: 1362
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443
Carbon
Bytes: 67615; Co2 grams: 0.0025; Cleaner than: 30
DNS server
NS: (IP: 216.239.36.10; Host: ns3.google.com), (IP: 216.239.32.10; Host: ns1.google.com), (IP: 216.239.34.10; Host: ns2.google.com), (IP: 216.239.38.10; Host: ns4.google.com); Zone: blogspot.com
Quality
Cls: 0; Seo: 54; Fcp s: 3.01; Lcp s: 8.8; Tbt ms: 152; Accessibility: 77; Best practices: 96
Location
IP: 2a00:1450:4001:c21::84; ASN: 15169; Org: Google LLC; City: Frankfurt am Main; Country: DE
SSL
San: misc-sni.blogspot.com, blogspot.ae, *.blogspot.ae, blogspot.al, *.blogspot.al, blogspot.am, *.blogspot.am, blogspot.ba, *.blogspot.ba, blogspot.be, *.blogspot.be, blogspot.bg, *.blogspot.bg, blogspot.ca, *.blogspot.ca, blogspot.ch, *.blogspot.ch, blogspot.cl, *.blogspot.cl, blogspot.co.at, *.blogspot.co.at, blogspot.co.id, *.blogspot.co.id, blogspot.co.il, *.blogspot.co.il, blogspot.co.ke, *.blogspot.co.ke, blogspot.co.nz, *.blogspot.co.nz, blogspot.co.uk, *.blogspot.co.uk, blogspot.co.za, *.blogspot.co.za, blogspot.com, *.blogspot.com, blogspot.com.ar, *.blogspot.com.ar, blogspot.com.au, *.blogspot.com.au, blogspot.com.br, *.blogspot.com.br, blogspot.com.by, *.blogspot.com.by, blogspot.com.co, *.blogspot.com.co, blogspot.com.cy, *.blogspot.com.cy, blogspot.com.ee, *.blogspot.com.ee, blogspot.com.eg; Bits: 256; Chain: misc-sni.blogspot.com, WE2, GTS Root R4; Issuer: Google Trust Services / WE2; Serial: BE9362B229C6A5E7105430FBFB588354; SHA256: 410aa334dd10ce86a20d47f491f7acecd522eb9eb5c9cfa584840c3ad95eef27; Subject: misc-sni.blogspot.com; Valid to: 2027-01-26T08:28:11Z; Valid from: 2026-11-03T08:28:12Z
DNS records
A: 142.251.14.132; Aaaa: 2a00:1450:4001:c21::84; Cname: blogspot.l.googleusercontent.com
Dnssec
Ds: ✓; Rrsig: ✗; Dnskey: ✓
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: 1; mode=block; Permissionspolicy: ✗; Xcontenttypeoptions: nosniff; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 2a00:1450:4001:c21::84; Family: 6
Redirects
Chain: https://robuxtime.blogspot.com
HTTP headers
Headers: Server: GSE; Content type: text/html; charset=UTF-8; X content type options: nosniff
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing

Questions about robuxtime.blogspot.com

Is robuxtime.blogspot.com a legitimate Roblox site?

No, it has no affiliation with the official roblox.com platform. It uses a third-party blogging service to impersonate reward generators.

What happens if I entered my username on robuxtime.blogspot.com?

Entering your username on an unauthorized third-party page exposes your account to social engineering, targeted phishing messages, or automated brute-force attacks. You should change your password immediately.

How can I secure my account after visiting robuxtime.blogspot.com?

Log into your official Roblox account via roblox.com, update your password to a strong unique combination, and enable two-factor authentication via authenticator apps or email verification.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (7)

All capture links and hashes (7)

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Roblox report ↗
IP Reputation United States142.251.14.132 0/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worse This IP address has a low abuse score, but the domain itself is recognized as phishing. 31 reports Email SpamPort ScanHacking checked 2026-11-20 last reported
Platform provider blogspot.com
Hosting abuse contact network-abuse@google.com, abuse@google.com Google LLC · AS15169
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-20
DOM Analysisanalyzed 2026-11-20score 15/1003 brand signals
Submitted URLhttp://robuxtime.blogspot.com/
Favicon Hash
Observed page title
Roblox - Robux Generator
Automated brand references
Roblox Robux Xbox
TLS Certificate
Issued by Google Trust Services / WE2 · stored validity ends in 64 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States142.251.14.132
Network ASN
AS15169
AS name
GOOGLE - Google LLC, US
Organization
Google LLC
Observed location
United StatesNew Haven, US
Server header
GSE

Nameservers 4

  • ns1.google.com
  • ns2.google.com
  • ns3.google.com
  • ns4.google.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE2
Valid from
2026-11-03 08:28:12
Valid until
2027-01-26 08:28:11
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint410aa334dd10ce86a20d47f491f7acecd522eb9eb5c9cfa584840c3ad95eef27
Certificate names · 50 SANs
  • misc-sni.blogspot.com
  • blogspot.ae
  • *.blogspot.ae
  • blogspot.al
  • *.blogspot.al
  • blogspot.am
  • *.blogspot.am
  • blogspot.ba
  • *.blogspot.ba
  • blogspot.be
  • *.blogspot.be
  • blogspot.bg
  • *.blogspot.bg
  • blogspot.ca
  • *.blogspot.ca
  • blogspot.ch
  • *.blogspot.ch
  • blogspot.cl
  • *.blogspot.cl
  • blogspot.co.at
  • *.blogspot.co.at
  • blogspot.co.id
  • *.blogspot.co.id
  • blogspot.co.il
  • *.blogspot.co.il
  • blogspot.co.ke
  • *.blogspot.co.ke
  • blogspot.co.nz
  • *.blogspot.co.nz
  • blogspot.co.uk
  • *.blogspot.co.uk
  • blogspot.co.za
  • *.blogspot.co.za
  • blogspot.com
  • *.blogspot.com
  • blogspot.com.ar
  • *.blogspot.com.ar
  • blogspot.com.au
  • *.blogspot.com.au
  • blogspot.com.br
  • *.blogspot.com.br
  • blogspot.com.by
  • *.blogspot.com.by
  • blogspot.com.co
  • *.blogspot.com.co
  • blogspot.com.cy
  • *.blogspot.com.cy
  • blogspot.com.ee
  • *.blogspot.com.ee
  • blogspot.com.eg

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-11-21 11:13 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-21 11:13 UTC
RDAP registration
Observed timeline last reachable: 2026-11-21 11:13 UTC last content: 2026-11-21 11:13 UTC
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.
Technologies · 9 identified
Open complete records

VirusTotal Analysis

14 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy
ESET
VIPRE
G-Data
Lionic
Sophos
CyRadar
Webroot
Emsisoft
Fortinet
Netcraft
Kaspersky
LevelBlue
Gridinsoft
BitDefender
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data100
Open complete records

Captured network requests

Network requests: 27 SHA-256 hashes: 13 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-20 14:45 UTC.

Open this scan on URLScan 01a1f969-41a3-72f6-bbfd-3f452409e216 ↗

Stored observation history2

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Serving page content

    page content returned

  2. Domain monitor · First collection record

    Reachable

All retained availability observations6
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 10. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    robuxtime.blogspot.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Cloudflare Radar: Malicious · Automated brand label: Roblox · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+9605 d 7 h
  3. Added to PhishDestroy+57 h 54 min
  1. Cloudflare Radar

    Phishing

    +2 min
  2. Added to PhishDestroy

    robuxtime.blogspot.com

    same minute
  3. URLScan

    Page captured

    +57 h 54 min
  4. VirusTotal

    14/92 engine detections

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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

robuxtime.blogspot.com

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including robuxtime.blogspot.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

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 →
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/robuxtime.blogspot.com"
  title="PhishDestroy threat report for robuxtime.blogspot.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>