Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 15. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
usernamerobux13.blogspot.com favicon

usernamerobux13.blogspot.com

In short

PhishDestroy stores a record for usernamerobux13.blogspot.com. Source observations are dated separately; missing checks do not establish safety.

“Roblox Robux”

Review the evidence
Registrar
United StatesGoogle Domains
Resolved IP
United States142.251.20.132GOOGLE - Google LLC, US
First observed
Oct 25, 2026
PhishDestroy assessment Critical
95/100
Evidence score
Availability Content unavailable Content was unavailable in the latest observation Observed HTTP probe
Risk signals
VirusTotal detections: 15/92
VirusTotal
15 / 92
engine detections ·
Page captures
3
open gallery
Oct 25, 2026
X Telegram API

Questions about usernamerobux13.blogspot.com

Is usernamerobux13.blogspot.com legit?

PhishDestroy stores a record for usernamerobux13.blogspot.com. Source observations are dated separately; missing checks do not establish safety.

Is usernamerobux13.blogspot.com safe to connect a wallet?

This report does not record which wallet requests usernamerobux13.blogspot.com makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used usernamerobux13.blogspot.com?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Source evidenceVirusTotal 15 / 92 6 sources

VirusTotal

15 / 92 engine detections

Open report

URLScan

Malicious

SHA-256 7f121549e188a307cb0044b7caff10c202228857a0196472aef2808ec61bfb40

Open report
Separate monitor record · 2026-10-25 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a1712e-a3bc-71ff-ac80-5b82c8ad1f88
score
100
malicious
true
result_at
2026-10-25T04:30:43Z
enriched_at
2026-10-26T09:20:15Z
source_timestamps
{"urlscan_result_at":"2026-10-25 05:30:43","urlscan_enriched_at":"2026-10-26 10:20:15"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

20 / 100 · heuristic score · 2 brand references · 1 classification

Open report
Separate monitor score · 20 / 100 · 2026-10-25T07:20:22Z

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

record_source
domain_monitor.dom_analysis
heuristic_score
20
analyzed_at
2026-10-25T07:20:22Z
source_timestamp
2026-10-25 08:20:22
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 3 captures

Primary capture 1 / 3
SourcePrimary capture
Recorded
StateStored capture
Position1 / 3
Open capture Wayback Download
All capture links and hashes (3)
usernamerobux13.blogspot.com: caution — 15/92 VirusTotal engines. PhishDestroy risk score 95/100 (critical).
Social preview card usernamerobux13.blogspot.com: caution — 15/92 VirusTotal engines. PhishDestroy risk score 95/100 (critical). v 1db0b4cd5d2a

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Roblox report ↗
IP Reputation United States142.251.20.132 abuse score 0/100 13 reports Email SpamPort ScanHackingBrute-ForceSSH checked Oct 25, 2026 last reported
Platform provider Google Domains US(US)
Abuse contactnetwork-abuse@google.com, abuse@google.com
Hosting abuse contact network-abuse@google.com, abuse@google.com GOOGLE - Google LLC, US · AS15169
HTTP Status404 Not Found
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 20/1002 brand signals
Submitted URLhttp://usernamerobux13.blogspot.com/
Favicon Hash
Observed page title
Roblox Robux
Automated brand references
Roblox Robux
TLS Certificate
Issued by Google Trust Services / WE2 · stored validity ends in 50 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States142.251.20.132
Network ASN
AS15169
Organization
GOOGLE - Google LLC, US
Observed location
United StatesUS
Server header
GSE

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE2
Valid from
2026-09-28 18:40:34
Valid until
2026-12-21 18:40:33
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-25 05:02:11 UTC
Collection source
PhishDestroy collector
Certificate fingerprint7e702db2cd863f12878210369da95cee319bdb748393501d05c91b69cf032638
Certificate names · 70 SANs
  • blogspot.ae
  • blogspot.al
  • blogspot.am
  • blogspot.ba
  • blogspot.be
  • blogspot.bg
  • blogspot.ca
  • blogspot.ch
  • blogspot.cl
  • blogspot.co.at
  • blogspot.co.id
  • blogspot.co.il
  • blogspot.co.ke
  • blogspot.co.nz
  • blogspot.co.uk
  • blogspot.co.za
  • blogspot.com
  • blogspot.com.ar
  • blogspot.com.au
  • blogspot.com.br
  • blogspot.com.by
  • blogspot.com.co
  • blogspot.com.cy
  • blogspot.com.ee
  • blogspot.com.eg
  • blogspot.com.es
  • blogspot.com.mt
  • blogspot.com.ng
  • blogspot.com.tr
  • blogspot.com.uy
  • blogspot.cz
  • blogspot.de
  • blogspot.dk
  • blogspot.fi
  • blogspot.fr
  • blogspot.gr
  • blogspot.hk
  • blogspot.hr
  • blogspot.hu
  • blogspot.ie
  • blogspot.in
  • blogspot.is
  • blogspot.it
  • blogspot.jp
  • blogspot.kr
  • blogspot.li
  • blogspot.lt
  • blogspot.lu
  • blogspot.md
  • blogspot.mk
  • blogspot.mx
  • blogspot.my
  • blogspot.nl
  • blogspot.no
  • blogspot.pe
  • blogspot.pt
  • blogspot.qa
  • blogspot.ro
  • blogspot.rs
  • blogspot.ru
  • blogspot.se
  • blogspot.sg
  • blogspot.si
  • blogspot.sk
  • blogspot.sn
  • blogspot.tw
  • blogspot.ug
  • blogspot.vn
  • bp.blogspot.com
  • misc-sni.blogspot.com

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

viewdns.info · 142.251.20.132rapiddns.io

Latest Classified Outcome 2026-10-31 23:04:49 UTC

No phishing content was served at the latest check.

Technical details
Primary outcome Inactive reason: Http No Content 70% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Root path has no content Content: Absent At Root DNS: Resolved Registration: Unknown
Latest HTTP observation Inactive Http No Content 70% 2026-10-31 23:04:49 UTC
RDAP registration
Observed timeline last reachable: 2026-10-25 03:52:22 UTC current episode first observed: 2026-10-25 12:03:47 UTC observed RIP window: 2026-10-25 03:52:22 UTC → 2026-10-25 12:03:47 UTC · 8.19h midpoint estimate ≈ 2026-10-25 07:58:04 UTC · precision medium · 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

15 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
CyRadar
Ermes
ESET
Emsisoft
Fortinet
G-Data
Gridinsoft
Lionic
Netcraft
OpenPhish
SOCRadar
Webroot
Yandex Safebrowsing

Archived Evidence

Wayback Machine Snapshot
View Archive
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://usernamerobux13.blogspot.com/
Final URL: https://usernamerobux13.blogspot.com/
Roblox Robux
Response
HTTP 200
HTML body
16.2 KB
Compressed
4.1 KB
Links
1 internal · 0 external
Selected response headers
Content-Type: text/html; charset=UTF-8
Cache-Control: private, max-age=0
Content-Encoding: gzip
Server: GSE
Security headers present
X-Content-Type-OptionsX-XSS-Protection
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 9fe741c1385e35b0da5b3cf15aad81e7714fac5bfb4cf535b2e04613c0a2b059
Saved response-header values · 12
Alt-Svc
h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
Cache-Control
private, max-age=0
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Sun, 25 Oct 2026 03:49:35 GMT
Etag
W/"30ce249f1556b1cbbfa10ef7526e85cd7dc6537395374d7c0ad07fc39d289287"
Expires
Sun, 25 Oct 2026 03:49:35 GMT
Last-Modified
Sat, 04 Jul 2026 01:04:22 GMT
Server
GSE
Transfer-Encoding
chunked
X-Content-Type-Options
nosniff
X-XSS-Protection
1; mode=block

Values retained by the collector; long values may be shortened during collection.

Archived
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
8.19
Estimate basis
Bounded by observations
Estimate precision
Medium

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

Captured network requests

Network requests: 32 SHA-256 hashes: 26 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-10-29 01:58 UTC.

Open this scan on URLScan 01a1712e-a3bc-71ff-ac80-5b82c8ad1f88 ↗

Check for cloaking

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

Page titles differ

Our scanner could not complete this check.

Browser
Roblox Robux
Crawler
Blog nicht gefunden.
usernamerobux13.blogspot.com
Stored observation history5

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

    inactive

    http_no_content

  2. Availability monitor · Recorded state

    inactive

    http_no_content

  3. Availability monitor · Recorded state

    inactive

    http_no_content

  4. Availability monitor · Recorded state

    inactive

    http_no_content

  5. Domain monitor · First collection record

    Reachable

All retained availability observations33

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:04:49.000000
    Evidence SHA-256
    c71a3b12e4acd42ab6fe3caedb4c2a3ff028700fb51c900cf9f76021c841e01b
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-11-01 00:04:49
    Evidence reason
    http_other
  2. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:04:49.000000
    Evidence SHA-256
    c71a3b12e4acd42ab6fe3caedb4c2a3ff028700fb51c900cf9f76021c841e01b
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-11-01 00:04:49
    Evidence reason
    http_other
  3. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:05:07.000000
    Evidence SHA-256
    cc7304ec8560d4178782fcb3237871359d0b53a96473ec708bfc9f0181fbda6d
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-31 12:05:07
    Evidence reason
    http_other
  4. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:05:07.000000
    Evidence SHA-256
    cc7304ec8560d4178782fcb3237871359d0b53a96473ec708bfc9f0181fbda6d
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-31 12:05:07
    Evidence reason
    http_other
  5. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 11:20:09.112163
    Evidence SHA-256
    b5c6551e799cfe4d3cb298004536f14652a7bd27158039d9a8bde93b0611124a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 11:20:09.112163
    Evidence reason
  6. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:25:52.000000
    Evidence SHA-256
    d40f0e67760fd409f98858f7e7094feb4e60c8295315e3b97f29f6d9d9ad1e8c
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-31 03:25:52
    Evidence reason
    http_other
  7. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:25:52.000000
    Evidence SHA-256
    d40f0e67760fd409f98858f7e7094feb4e60c8295315e3b97f29f6d9d9ad1e8c
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-31 03:25:52
    Evidence reason
    http_other
  8. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:01:23.000000
    Evidence SHA-256
    3456f47f3a22b6a21c888086c056318259887a69e6ec82a40a950a4d0f9507c8
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-30 12:01:23
    Evidence reason
    http_other
  9. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:01:23.000000
    Evidence SHA-256
    3456f47f3a22b6a21c888086c056318259887a69e6ec82a40a950a4d0f9507c8
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-30 12:01:23
    Evidence reason
    http_other
  10. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 05:03:05.462458
    Evidence SHA-256
    bbc8a7612fad967fe6394ef6e3533c42adb354b0403e4f596ca1b553348f1852
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 05:03:05.462458
    Evidence reason
  11. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:01:47.000000
    Evidence SHA-256
    f0f771d2821d25239e95dd9c8b76dd458abf40e5b2ba6e8221fbb3b23dac29fe
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-30 00:01:47
    Evidence reason
    http_other
  12. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:01:47.000000
    Evidence SHA-256
    f0f771d2821d25239e95dd9c8b76dd458abf40e5b2ba6e8221fbb3b23dac29fe
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-30 00:01:47
    Evidence reason
    http_other
  13. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:02:07.000000
    Evidence SHA-256
    b08c690cecd40d92450815113dc9bf170be1d633316c67d1cf1a10a088e2234e
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-29 12:02:07
    Evidence reason
    http_other
  14. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:02:07.000000
    Evidence SHA-256
    b08c690cecd40d92450815113dc9bf170be1d633316c67d1cf1a10a088e2234e
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-29 12:02:07
    Evidence reason
    http_other
  15. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 01:01:30.000000
    Evidence SHA-256
    0b851d63926ebadc997038e99934b3681eceb608666f3efe664f5ea70d20e0b9
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-29 01:01:30
    Evidence reason
    http_other
  16. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 01:01:30.000000
    Evidence SHA-256
    0b851d63926ebadc997038e99934b3681eceb608666f3efe664f5ea70d20e0b9
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-29 01:01:30
    Evidence reason
    http_other
  17. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 17:03:14.895165
    Evidence SHA-256
    73d1f345e73e3fe3ec20cf30f9fc86221ba9885e7af8cdcc18189657c73b0d4e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-28 17:03:14.895165
    Evidence reason
  18. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 13:08:59.000000
    Evidence SHA-256
    b790b693d4fcf671564628c627e0f3ce11a893c94cda32aa7eb3b1858eef4a73
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-28 13:08:59
    Evidence reason
    http_other
  19. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 13:08:59.000000
    Evidence SHA-256
    b790b693d4fcf671564628c627e0f3ce11a893c94cda32aa7eb3b1858eef4a73
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-28 13:08:59
    Evidence reason
    http_other
  20. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 01:11:03.000000
    Evidence SHA-256
    4cc90a525033eac99518a7ebf6b8fae87e5e6f8c2f9afaf14ce864451fcc1f6b
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-28 01:11:03
    Evidence reason
    http_other
  21. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 01:11:03.000000
    Evidence SHA-256
    4cc90a525033eac99518a7ebf6b8fae87e5e6f8c2f9afaf14ce864451fcc1f6b
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-28 01:11:03
    Evidence reason
    http_other
  22. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 13:08:46.000000
    Evidence SHA-256
    fed77aa9c34a42c0bd4dcbaf0ee9d497fffcb41d0b58fc035ef9aaac229a5fb8
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-27 13:08:46
    Evidence reason
    http_other
  23. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 13:08:46.000000
    Evidence SHA-256
    fed77aa9c34a42c0bd4dcbaf0ee9d497fffcb41d0b58fc035ef9aaac229a5fb8
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-27 13:08:46
    Evidence reason
    http_other
  24. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 05:01:51.000000
    Evidence SHA-256
    4557f444d539dbe6389122f971934420d799a10908c725b76ba56677e06ed551
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-27 05:01:51
    Evidence reason
    http_other
  25. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 05:01:51.000000
    Evidence SHA-256
    4557f444d539dbe6389122f971934420d799a10908c725b76ba56677e06ed551
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-27 05:01:51
    Evidence reason
    http_other
  26. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:58:21.000000
    Evidence SHA-256
    6eb50ee7cb58a4ade5476522b50e1da9e381f317bc1b3145098561a7bc607765
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-26 12:58:21
    Evidence reason
    http_other
  27. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:58:21.000000
    Evidence SHA-256
    6eb50ee7cb58a4ade5476522b50e1da9e381f317bc1b3145098561a7bc607765
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-26 12:58:21
    Evidence reason
    http_other
  28. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:01:29.000000
    Evidence SHA-256
    b0782461ba370d369359aa83ce18d3ed56402bf2fbf57c42049e8c558a685f9b
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-26 01:01:29
    Evidence reason
    http_other
  29. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:01:29.000000
    Evidence SHA-256
    b0782461ba370d369359aa83ce18d3ed56402bf2fbf57c42049e8c558a685f9b
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-26 01:01:29
    Evidence reason
    http_other
  30. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 13:03:47.000000
    Evidence SHA-256
    5b610906339aa2c5f8d06ae8a2af9a933e90366914f37d15572e8f7fbc7b05ce
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-25 13:03:47
    Evidence reason
    http_other
  31. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 13:03:47.000000
    Evidence SHA-256
    5b610906339aa2c5f8d06ae8a2af9a933e90366914f37d15572e8f7fbc7b05ce
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-25 13:03:47
    Evidence reason
    http_other
  32. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:52:22.000000
    Evidence SHA-256
    7d06a02addb665fbb9d910fb9db53bc24cbc029089af575ac77fd8522bc18018
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 04:52:22
    Evidence reason
  33. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:52:22.000000
    Evidence SHA-256
    7d06a02addb665fbb9d910fb9db53bc24cbc029089af575ac77fd8522bc18018
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 04:52:22
    Evidence reason

Threat Response Pipeline

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

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: 1 of 1
  • Threat Ingested
    usernamerobux13.blogspot.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Web Archive · VirusTotal · Automated brand label: Roblox · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 15/92
  • Automated brand label: Roblox
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Content Observed Unavailable Recorded: 2 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Content Observed Unavailable
    The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.

Recorded activity

4 entries
  1. VirusTotal

    15/92 engine detections

    View source
  2. Added to PhishDestroy

    usernamerobux13.blogspot.com

    View source
  3. URLScan

    Page captured

    View source
  4. Wayback Machine

    Page archived

    View source
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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 15 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Content unavailable
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. Silence is the scammer’s greatest advantage. Break it.
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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
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.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
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

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 usernamerobux13.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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

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.

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.

Request a correction or appeal How PhishDestroy works
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/usernamerobux13.blogspot.com"
  title="PhishDestroy threat report for usernamerobux13.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>