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

freerobuxxc.blogspot.com

In short

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

“Free Robux - Official Claim Portal”

Review the evidence
Registrar
United StatesGoogle Domains
Resolved IP
Germany142.251.127.132Google LLC
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: 10/92
VirusTotal
10 / 92
engine detections ·
URLQuery
5
detections
URLScan
Malicious
Page captures
10
open gallery
Oct 25, 2026
X Telegram API

Questions about freerobuxxc.blogspot.com

Is freerobuxxc.blogspot.com legit?

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

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

This report does not record which wallet requests freerobuxxc.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 freerobuxxc.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 10 / 92 7 sources

VirusTotal

10 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
49
Malicious
10
Suspicious
0
Undetected
33

Vendor labels

ESET
phishing
G-Data
phishing
Sophos
phishing
Webroot
malicious
Emsisoft
phishing
Netcraft
malicious
SOCRadar
phishing
LevelBlue
phishing
BitDefender
phishing
alphaMountain.ai
phishing

Reputation score

0

Registrar

MarkMonitor Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    173.194.64.132
  • TTL, seconds
    300
    Type
    CNAME
    Value
    blogspot.l.googleusercontent.com
  • TTL, seconds
    299
    Type
    CNAME
    Value
    blogspot.l.googleusercontent.com
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2607:f8b0:4001:c6a::84

DNS records observed

JARM fingerprint

27d40d40d29d40d1dc42d43d00041ded961c16c68658e95145597cf992c36c

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
Issuer
Google Trust Services / WE2
Serial
814ac5b024f8ff6f10caaecf9f796a9f
SHA-256
7e702db2cd863f12878210369da95cee319bdb748393501d05c91b69cf032638
Subject
misc-sni.blogspot.com
Valid until
Valid from

Registration record

Registrar
MarkMonitor Inc.
Registrar IANA ID
292
Registrar URL
http://www.markmonitor.com
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
  • serverDeleteProhibited
  • serverTransferProhibited
  • serverUpdateProhibited
Nameservers
  • ns1.google.com
  • ns2.google.com
  • ns3.google.com
  • ns4.google.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 49,
    "malicious": 10,
    "suspicious": 0,
    "undetected": 33
}
Vendor labels
{
    "ESET": "phishing",
    "G-Data": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Netcraft": "malicious",
    "SOCRadar": "phishing",
    "LevelBlue": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Registrar
MarkMonitor Inc.
Created
2000-07-31T21:38:58Z
Expires
2027-07-31T21:38:58Z
Updated
2026-06-29T10:34:06Z
First seen
2026-08-05T03:17:27Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "173.194.64.132"
    },
    {
        "ttl": 300,
        "type": "CNAME",
        "value": "blogspot.l.googleusercontent.com"
    },
    {
        "ttl": 299,
        "type": "CNAME",
        "value": "blogspot.l.googleusercontent.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2607:f8b0:4001:c6a::84"
    }
]
Dns at
2026-10-23T22:51:56Z
Jarm
27d40d40d29d40d1dc42d43d00041ded961c16c68658e95145597cf992c36c
Certificate
{
    "san": [
        "misc-sni.blogspot.com",
        "blogspot.ae",
        "*.blogspot.ae",
        "blogspot.al",
        "*.blogspot.al",
        "blogspot.am",
        "*.blogspot.am",
        "blogspot.ba",
        "*.blogspot.ba",
        "blogspot.be"
    ],
    "issuer": "Google Trust Services / WE2",
    "serial": "814ac5b024f8ff6f10caaecf9f796a9f",
    "sha256": "7e702db2cd863f12878210369da95cee319bdb748393501d05c91b69cf032638",
    "subject": "misc-sni.blogspot.com",
    "valid_to": "2026-12-21T18:40:33Z",
    "valid_from": "2026-09-28T18:40:34Z"
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "registrar_iana_id": "292",
    "registrar_url": "http://www.markmonitor.com",
    "created": "2000-07-31T07:00:00Z",
    "updated": "2026-06-29T10:34:06Z",
    "expires": "2027-07-31T00:00:00Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited",
        "serverDeleteProhibited",
        "serverTransferProhibited",
        "serverUpdateProhibited"
    ],
    "nameservers": [
        "ns1.google.com",
        "ns2.google.com",
        "ns3.google.com",
        "ns4.google.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 10 malicious + 0 suspicious / 92 · 2026-10-23 22:51:37 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-23T22:51:37Z
fetched_at
2026-10-25T02:13:45Z
stats
{"timeout":0,"harmless":49,"malicious":10,"suspicious":0,"undetected":33}

URLScan

Malicious

SHA-256 c266b6f62e7a147c17913a51d392654ef960c8d7ae71e89721a17ee6229af5e2

Open report
URLScanOriginal source recordObserved: 24 fields

Observed: · Retrieved:

Report ID

01a170cf-a910-708a-aa96-33e261974514

Final URL

https://freerobuxxc.blogspot.com/

HTTP response

200

Redirect type

same-domain

Redirects

  • To
    https://freerobuxxc.blogspot.com/
    From
    http://freerobuxxc.blogspot.com/
    Status
    307
  • To
    http://freerobuxxc.blogspot.com/
    From
    https://freerobuxxc.blogspot.com/
    Status
    307
  • To
    http://freerobuxxc.blogspot.com/
    From
    http://freerobuxxc.blogspot.com/
    Status
    302
  • To
    https://freerobuxxc.blogspot.com/
    From
    http://freerobuxxc.blogspot.com/
    Status
    301

IP address

142.251.13.132

Reverse DNS (PTR)

wt-in-f132.1e100.net

Contacted domains

  • s4.histats.com
  • s10.histats.com
  • www.blogger.com
  • i.postimg.cc

Contacted IP addresses

  • 149.56.240.131
  • 104.20.8.131
  • 142.250.154.191
  • 195.154.239.27
  • 142.251.13.132

Autonomous systems (ASN)

  • 16276
  • 13335
  • 15169
  • 12876

Server countries

  • CA
  • US
  • FR

Linked domains

  • www.blogger.com

Document hash

3f65da0ffdec084c8839de8a0d3ed03cd50cfec4efbd42ef3c4896b66cc48f33

Script hashes

  • 068ffe90977f2b5b2dc2ef18572166e85281bd0ecb31c4902464b23db54d2568

JavaScript globals

  • adsbygoogle
  • showBlockScreen
  • openLocker
  • HISTATS_ID
  • _Hasync
  • chfh
  • chfh2
  • _HST_cntval
  • Histats
  • BLOG_attachCsiOnload
  • _WidgetManager
  • _WidgetInfo
  • widget_module_provide
  • _AdSenseView
  • _BlogArchiveView
  • _AttributionView
  • _BlogView
  • _BlogListView
  • _BlogSearchView
  • _ContactFormView
  • _ExampleView
  • _FeaturedPostView
  • _FeedView
  • _FollowersView
  • _HeaderView
  • _TextView
  • _HTMLView
  • _ImageView
  • _LabelView
  • _TextListView
  • _LinkListView
  • _BloggerButtonView
  • _NavbarView
  • _PageListView
  • _PollView
  • _PopularPostsView
  • _ProfileView
  • _RecentPostsView
  • _ReportAbuseView
  • _SharingView

Cookies

  • HstCfa5030533
  • HstCla5030533
  • HstCmu5030533
  • HstPn5030533
  • HstPt5030533
  • HstCnv5030533
  • HstCns5030533

TLS session and 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
Cipher
AES_128_GCM
Issuer
WE2
Subject
misc-sni.blogspot.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

11

Registered domain age, days

11

Certificate age, days

26

Certificate validity, days

83

Page requests

7

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
98
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • roblox
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Roblox
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
GSE
Content-type
text/html; charset=UTF-8
X-content-type-options
nosniff
Original source fields · JSON
Uuid
01a170cf-a910-708a-aa96-33e261974514
Final url
https://freerobuxxc.blogspot.com/
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://freerobuxxc.blogspot.com/",
        "from": "http://freerobuxxc.blogspot.com/",
        "status": 307
    },
    {
        "to": "http://freerobuxxc.blogspot.com/",
        "from": "https://freerobuxxc.blogspot.com/",
        "status": 307
    },
    {
        "to": "http://freerobuxxc.blogspot.com/",
        "from": "http://freerobuxxc.blogspot.com/",
        "status": 302
    },
    {
        "to": "https://freerobuxxc.blogspot.com/",
        "from": "http://freerobuxxc.blogspot.com/",
        "status": 301
    }
]
Ip
142.251.13.132
Ptr
wt-in-f132.1e100.net
Contacted domains
[
    "s4.histats.com",
    "s10.histats.com",
    "www.blogger.com",
    "i.postimg.cc"
]
Contacted IP addresses
[
    "149.56.240.131",
    "104.20.8.131",
    "142.250.154.191",
    "195.154.239.27",
    "142.251.13.132"
]
Asns
[
    "16276",
    "13335",
    "15169",
    "12876"
]
Countries
[
    "CA",
    "US",
    "FR"
]
Linked domains
[
    "www.blogger.com"
]
Document hash
3f65da0ffdec084c8839de8a0d3ed03cd50cfec4efbd42ef3c4896b66cc48f33
Script hashes
[
    "068ffe90977f2b5b2dc2ef18572166e85281bd0ecb31c4902464b23db54d2568"
]
Globals
[
    "adsbygoogle",
    "showBlockScreen",
    "openLocker",
    "HISTATS_ID",
    "_Hasync",
    "chfh",
    "chfh2",
    "_HST_cntval",
    "Histats",
    "BLOG_attachCsiOnload",
    "_WidgetManager",
    "_WidgetInfo",
    "widget_module_provide",
    "_AdSenseView",
    "_BlogArchiveView",
    "_AttributionView",
    "_BlogView",
    "_BlogListView",
    "_BlogSearchView",
    "_ContactFormView",
    "_ExampleView",
    "_FeaturedPostView",
    "_FeedView",
    "_FollowersView",
    "_HeaderView",
    "_TextView",
    "_HTMLView",
    "_ImageView",
    "_LabelView",
    "_TextListView",
    "_LinkListView",
    "_BloggerButtonView",
    "_NavbarView",
    "_PageListView",
    "_PollView",
    "_PopularPostsView",
    "_ProfileView",
    "_RecentPostsView",
    "_ReportAbuseView",
    "_SharingView"
]
Cookies
[
    "HstCfa5030533",
    "HstCla5030533",
    "HstCmu5030533",
    "HstPn5030533",
    "HstPt5030533",
    "HstCnv5030533",
    "HstCns5030533"
]
Tls
{
    "san": [
        "misc-sni.blogspot.com",
        "blogspot.ae",
        "*.blogspot.ae",
        "blogspot.al",
        "*.blogspot.al",
        "blogspot.am",
        "*.blogspot.am",
        "blogspot.ba",
        "*.blogspot.ba",
        "blogspot.be"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE2",
    "subject": "misc-sni.blogspot.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-21T18:40:33Z",
    "valid_from": "2026-09-28T18:40:34Z"
}
Domain age days
11
Apex age days
11
Tls age days
26
Tls valid days
83
Requests
7
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 98,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "roblox"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Roblox"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "GSE",
    "content-type": "text/html; charset=UTF-8",
    "x-content-type-options": "nosniff"
}
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
01a170cf-a910-708a-aa96-33e261974514
score
100
malicious
true
result_at
2026-10-25T04:30:46Z
enriched_at
2026-10-25T09:12:19Z
source_timestamps
{"urlscan_result_at":"2026-10-25 05:30:46","urlscan_enriched_at":"2026-10-25 10:12:19"}
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 · 3 brand references · 1 classification

Open report
Separate monitor score · 20 / 100 · 2026-10-25T03:20:41Z

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-25T03:20:41Z
source_timestamp
2026-10-25 04:20:41
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.

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
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Crawler rules

User agents
  • Mediapartners-Google
  • *
Present
Yes
Sitemap URLs
  • https://freerobuxxc.blogspot.com/sitemap.xml

Page title and metadata

Page title
Free Robux - Official Claim Portal
Open Graph type
website
Open Graph image
https://i.postimg.cc/J7KmXfgj/file-000000007aec71faadca3db1f0f4c464.png
Open Graph title
Free Robux - Official Claim Portal
Twitter card
summary_large_image
Open Graph description
Claim your free Robux instantly. Limited time official promotional event. Verify now!

Trackers

Requests
4
Observed services
  • Name
    blogspot.com
    Company
    Google
    Country
    US
    Category
    Misc
    Requests
    1
  • Name
    Histats
    Company
    Histats
    Country
    US
    Category
    Site Analytics
    Requests
    2

Forms and mixed content

Scripts without SRI
  • https://www.blogger.com/static/v1/widgets/3961732468-widgets.js
Third-party scripts
1

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
2
TLS
19
Waiting
127
Connection
6
Download
5
Response time, ms
159

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
17248
CO₂, grams
0.0006
Cleaner than, %
60

DNS servers

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

Cookies

Cookies
  • Name
    HstCfa5030533
  • Name
    HstCla5030533
  • Name
    HstCmu5030533
  • Name
    HstPn5030533
  • Name
    HstPt5030533
  • Name
    HstCnv5030533
  • Name
    HstCns5030533

Location

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

TLS certificate

Issuer
Google Trust Services / WE2
Subject
misc-sni.blogspot.com

DNS records

A
  • 142.251.110.132
AAAA
  • 2a00:1450:4001:c25::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:c25::84
IP version
6

Redirects

Redirect chain
  • https://freerobuxxc.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_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Crawler rules
{
    "agents": [
        "Mediapartners-Google",
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://freerobuxxc.blogspot.com/sitemap.xml"
    ]
}
Page title and metadata
{
    "title": "Free Robux - Official Claim Portal",
    "ogType": "website",
    "ogImage": "https://i.postimg.cc/J7KmXfgj/file-000000007aec71faadca3db1f0f4c464.png",
    "ogTitle": "Free Robux - Official Claim Portal",
    "twitterCard": "summary_large_image",
    "ogDescription": "Claim your free Robux instantly. Limited time official promotional event. Verify now!"
}
Trackers
{
    "requests": 4,
    "trackers": [
        {
            "name": "blogspot.com",
            "company": "Google",
            "country": "US",
            "category": "Misc",
            "requests": 1
        },
        {
            "name": "Histats",
            "company": "Histats",
            "country": "US",
            "category": "Site Analytics",
            "requests": 2
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://www.blogger.com/static/v1/widgets/3961732468-widgets.js"
    ],
    "third_party_scripts": 1
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 19,
        "wait": 127,
        "connect": 6,
        "download": 5
    },
    "response_ms": 159
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 17248,
    "co2_grams": 0.0006,
    "cleaner_than": 60
}
Dns server
{
    "ns": [
        {
            "ip": "216.239.32.10",
            "host": "ns1.google.com"
        },
        {
            "ip": "216.239.38.10",
            "host": "ns4.google.com"
        },
        {
            "ip": "216.239.34.10",
            "host": "ns2.google.com"
        },
        {
            "ip": "216.239.36.10",
            "host": "ns3.google.com"
        }
    ],
    "zone": "blogspot.com"
}
Cookies
{
    "cookies": [
        {
            "name": "HstCfa5030533"
        },
        {
            "name": "HstCla5030533"
        },
        {
            "name": "HstCmu5030533"
        },
        {
            "name": "HstPn5030533"
        },
        {
            "name": "HstPt5030533"
        },
        {
            "name": "HstCnv5030533"
        },
        {
            "name": "HstCns5030533"
        }
    ]
}
Location
{
    "ip": "2a00:1450:4001:c25::84",
    "asn": "15169",
    "org": "Google LLC",
    "city": "Frankfurt am Main",
    "country": "DE"
}
Ssl
{
    "issuer": "Google Trust Services / WE2",
    "subject": "misc-sni.blogspot.com"
}
DNS records
{
    "A": [
        "142.251.110.132"
    ],
    "AAAA": [
        "2a00:1450:4001:c25::84"
    ],
    "CNAME": [
        "blogspot.l.googleusercontent.com"
    ]
}
Dnssec
{
    "ds": true,
    "rrsig": false,
    "dnskey": true
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": "1; mode=block",
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "2a00:1450:4001:c25::84",
    "family": 6
}
Redirects
{
    "chain": [
        "https://freerobuxxc.blogspot.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "GSE",
        "content-type": "text/html; charset=UTF-8",
        "x-content-type-options": "nosniff"
    }
}
Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 10 captures

Primary capture 1 / 10
SourcePrimary capture
Recorded
StateStored capture
Position1 / 10
Open capture Wayback Download
All capture links and hashes (10)
freerobuxxc.blogspot.com: Suspected Robux impersonation — 12/92 VirusTotal engines. PhishDestroy risk score 95/100 (critical).
Social preview card freerobuxxc.blogspot.com: Suspected Robux impersonation — 12/92 VirusTotal engines. PhishDestroy risk score 95/100 (critical). v 04437a097eba

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Roblox report ↗
IP Reputation Germany142.251.127.132 abuse score 0/100 7 reports Email SpamPort ScanHackingBrute-Force 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 LLC · AS15169
HTTP Status404 Not Found
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 20/1003 brand signals
Submitted URLhttp://freerobuxxc.blogspot.com/
Favicon Hash
Observed page title
Free Robux - Official Claim Portal
Automated brand references
Google Roblox Robux
TLS Certificate
Issued by WE2 · stored validity ends in 50 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Germany142.251.127.132
Network ASN
AS15169
AS name
GOOGLE - Google LLC, US
Organization
Google LLC
Observed location
GermanyFrankfurt am Main, DE
Server header
GSE

Location describes the IP network.

TLS certificate

Issuer
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 source
PhishDestroy collector
Certificate fingerprint7e702db2cd863f12878210369da95cee319bdb748393501d05c91b69cf032638
Certificate names · 10 SANs
  • misc-sni.blogspot.com
  • blogspot.ae
  • *.blogspot.ae
  • blogspot.al
  • *.blogspot.al
  • blogspot.am
  • *.blogspot.am
  • blogspot.ba
  • *.blogspot.ba
  • blogspot.be

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.127.132rapiddns.io

Latest Classified Outcome 2026-10-31 23:10:56 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:10:56 UTC
RDAP registration
Observed timeline last reachable: 2026-10-31 11:11:40 UTC current episode first observed: 2026-10-31 23:10:56 UTC observed RIP window: 2026-10-31 11:11:40 UTC → 2026-10-31 23:10:56 UTC · 11.99h midpoint estimate ≈ 2026-10-31 17:11:18 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

10 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
ESET
Emsisoft
G-Data
Gridinsoft
LevelBlue
MalwareURL
Netcraft
SOCRadar
Sophos
Webroot

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://freerobuxxc.blogspot.com/
Final URL: https://freerobuxxc.blogspot.com/
Free Robux - Official Claim Portal
Response
HTTP 200
HTML body
15.2 KB
Compressed
5.5 KB
Links
0 internal · 0 external
Detected technologies
bootstrap
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: observed Cloaking flag: not observed
Open Graph title: Free Robux - Official Claim Portal
Open Graph description: Claim your free Robux instantly. Limited time official promotional event. Verify now!
Twitter card: summary_large_image
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 02:02:45 GMT
Etag
W/"898cc307e46f2d82706b06d0fe69327541272211f787991d5b591c549d974656"
Expires
Sun, 25 Oct 2026 02:02:45 GMT
Last-Modified
Sat, 04 Jul 2026 01:04:26 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
11.99
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: 7 SHA-256 hashes: 7 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 01a170cf-a910-708a-aa96-33e261974514 ↗

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
Free Robux - Official Claim Portal
Crawler
Blog niet gevonden
freerobuxxc.blogspot.com
Stored observation history7

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

    redirected→inactive

    http_no_content

  2. Availability monitor · Recorded state

    redirected

    http_redirect

  3. Availability monitor · Recorded state

    inactive

    http_no_content

  4. Availability monitor · Recorded state

    inactive

    http_no_content

  5. Availability monitor · Recorded state

    protected→inactive

    http_no_content

Earlier observations 2
  1. Availability monitor · Recorded state

    protected

    captcha · challenge

  2. Domain monitor · First collection record

    Reachable

All retained availability observations31

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:10:56.000000
    Evidence SHA-256
    6813678ca3a37566c8051eb58e7fbc5a5eb9e320dd74787a26ad6b624aad794c
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-11-01 00:10:56
    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:10:56.000000
    Evidence SHA-256
    6813678ca3a37566c8051eb58e7fbc5a5eb9e320dd74787a26ad6b624aad794c
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-11-01 00:10:56
    Evidence reason
    http_other
  3. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:11:40.000000
    Evidence SHA-256
    320c6105b476b4e68b4e662d29b068d45dd7c29ec25646c0605b9f3fa85760ff
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-31 12:11:40
    Evidence reason
    redirect
  4. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:11:40.000000
    Evidence SHA-256
    320c6105b476b4e68b4e662d29b068d45dd7c29ec25646c0605b9f3fa85760ff
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-31 12:11:40
    Evidence reason
    redirect
  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:32:49.000000
    Evidence SHA-256
    47bfccc4932bb87264609e720a048d8404ea4afbf77bfb82fff22439def226e6
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-31 03:32:49
    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:32:49.000000
    Evidence SHA-256
    47bfccc4932bb87264609e720a048d8404ea4afbf77bfb82fff22439def226e6
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-31 03:32:49
    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:09:17.000000
    Evidence SHA-256
    f0086159a2f4f1bdc04710b048d88012e519a379b6a0d2d1be50baec0c2c3750
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-30 12:09:17
    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:09:17.000000
    Evidence SHA-256
    f0086159a2f4f1bdc04710b048d88012e519a379b6a0d2d1be50baec0c2c3750
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-30 12:09:17
    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:09:33.000000
    Evidence SHA-256
    2855d3a07eec2dd5226fd24bd462d09868fcc419dd4e70121828f9784bb4aa04
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-30 00:09:33
    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:09:33.000000
    Evidence SHA-256
    2855d3a07eec2dd5226fd24bd462d09868fcc419dd4e70121828f9784bb4aa04
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-30 00:09:33
    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:10:03.000000
    Evidence SHA-256
    c42bc44aae03f81761762f54e24824175a0accd5a0e1f98c028053ba6000b251
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-29 12:10:03
    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:10:03.000000
    Evidence SHA-256
    c42bc44aae03f81761762f54e24824175a0accd5a0e1f98c028053ba6000b251
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-29 12:10:03
    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 03:38:48.000000
    Evidence SHA-256
    c9ebe936d76b614f50c97889defbd24208744e7f68c89aeb200e9eaa7bcf14de
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-29 03:38:48
    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 03:38:48.000000
    Evidence SHA-256
    c9ebe936d76b614f50c97889defbd24208744e7f68c89aeb200e9eaa7bcf14de
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-29 03:38:48
    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 12:04:59.000000
    Evidence SHA-256
    f3e6dec78a07eaf871104ced1b43f2fa80b7e19f621dbf772768966d2154a87e
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-28 12:04: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 12:04:59.000000
    Evidence SHA-256
    f3e6dec78a07eaf871104ced1b43f2fa80b7e19f621dbf772768966d2154a87e
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-28 12:04: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 00:05:22.000000
    Evidence SHA-256
    8e7dfb447c2d8bef6b9ad3d840f339c0c9cc976037f85291fd99ff4e709f899c
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-28 00:05:22
    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 00:05:22.000000
    Evidence SHA-256
    8e7dfb447c2d8bef6b9ad3d840f339c0c9cc976037f85291fd99ff4e709f899c
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-28 00:05:22
    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 12:05:35.000000
    Evidence SHA-256
    81d8a91be30b3a0a15eac35c9cdd34580d2a891a0a348bf28ac862b90a80efc0
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-27 12:05:35
    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 12:05:35.000000
    Evidence SHA-256
    81d8a91be30b3a0a15eac35c9cdd34580d2a891a0a348bf28ac862b90a80efc0
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-27 12:05:35
    Evidence reason
    http_other
  24. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:00:42.000000
    Evidence SHA-256
    7649bd26c05b1d6368685a0d16d80b0fcdb18952bf28a40c429d35cc552c317d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:00:42
    Evidence reason
    captcha
  25. http_observationprotected
    Observation source
    http_observation
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:00:42.000000
    Evidence SHA-256
    7649bd26c05b1d6368685a0d16d80b0fcdb18952bf28a40c429d35cc552c317d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:00:42
    Evidence reason
    captcha
  26. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:00:49.000000
    Evidence SHA-256
    a771bff521dd78dac40539e4cdd6b0096a382478af042e469eafceb0c5e14113
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:00:49
    Evidence reason
    captcha
  27. http_observationprotected
    Observation source
    http_observation
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:00:49.000000
    Evidence SHA-256
    a771bff521dd78dac40539e4cdd6b0096a382478af042e469eafceb0c5e14113
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:00:49
    Evidence reason
    captcha
  28. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:01:00.000000
    Evidence SHA-256
    38ca11e3340b92135362fd86b2eedc6cf9baa7ed9e1e960eee3680239de565e3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:01:00
    Evidence reason
    captcha
  29. http_observationprotected
    Observation source
    http_observation
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:01:00.000000
    Evidence SHA-256
    38ca11e3340b92135362fd86b2eedc6cf9baa7ed9e1e960eee3680239de565e3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:01:00
    Evidence reason
    captcha
  30. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 03:08:18.000000
    Evidence SHA-256
    a3dded9a081473685e0c35eae651b11e375a912a757da5bda1d53cdbec4fb1df
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 03:08:18
    Evidence reason
  31. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 03:08:18.000000
    Evidence SHA-256
    a3dded9a081473685e0c35eae651b11e375a912a757da5bda1d53cdbec4fb1df
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 03:08:18
    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
    freerobuxxc.blogspot.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Web Archive · VirusTotal · Automated brand label: Robux · 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: 10/92
  • Automated brand label: Robux
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, 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. Added to PhishDestroy

    freerobuxxc.blogspot.com

    View source
  2. URLScan

    Page captured

    View source
  3. Wayback Machine

    Page archived

    View source
  4. VirusTotal

    10/92 engine detections

    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 10 det. ChainPatrol URLQuery 5 det. 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?

4 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 freerobuxxc.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/freerobuxxc.blogspot.com"
  title="PhishDestroy threat report for freerobuxxc.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>