Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 12/92 engines flagged. malicious: 11. suspicious: 1. Analysis time (as stored): 2026-11-06T18:08:15Z. Retrieved (as stored): 2026-11-08T02:16:00Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
rewardbuxclaimhere.blogspot.com favicon

rewardbuxclaimhere.blogspot.com

In short

PhishDestroy first recorded rewardbuxclaimhere.blogspot.com on 2026-11-07. Stored VirusTotal result: 12/92 engines flagged. malicious: 11. suspicious: 1. Analysis time (as stored): 2026-11-06T18:08:15Z. Retrieved (as stored): 2026-11-08T02:16:00Z. Google Safe Browsing flags it.

“Блог не найден”

Review the evidence
Registrar
MarkMonitor
Resolved IP
Germany172.253.152.132Google LLC
First observed
Nov 7, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability HTTP 404 · Content unavailable The saved response applies to the checked URL. It does not establish that every path on the domain is unavailable. Observed HTTP probe
Risk signals
VirusTotal detections: 12/92 Google Safe Browsing: threat flag recorded
VirusTotal
12 / 92
engine detections ·
Google Safe Browsing
Flagged
URLScan
Malicious
engine verdict · score 74
Cloudflare Radar
Phishing
Page captures
7
open gallery
Nov 7, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded rewardbuxclaimhere.blogspot.com on 2026-11-07. Stored VirusTotal result: 12/92 engines flagged. malicious: 11. suspicious: 1. Analysis time (as stored): 2026-11-06T18:08:15Z. Retrieved (as stored): 2026-11-08T02:16:00Z. Google Safe Browsing flags it. Risk: critical (100/100). Registrar: MarkMonitor. Status: HTTP 404 · Content unavailable. Hosting: Google LLC. Do not enter credentials or connect a wallet.

Critical
Status
HTTP 404 · Content unavailable
VirusTotal
12 / 92
Hosting
Germany172.253.152.132Google LLC
Registrar
MarkMonitor
Page captures
7
Page captures Source results Registration record

Recorded source summary

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

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidenceVirusTotal 12 / 92 · Google Safe Browsing: flagged 6 sources

VirusTotal

12 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
46
Malicious
11
Suspicious
1
Undetected
34

Vendor labels

ESET
phishing
G-Data
phishing
Lionic
phishing
Webroot
malicious
Emsisoft
phishing
Fortinet
phishing
Netcraft
malicious
SOCRadar
suspicious
Gridinsoft
phishing
BitDefender
phishing
alphaMountain.ai
phishing
Google Safe Browsing
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

MarkMonitor Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    CNAME
    Value
    blogspot.l.googleusercontent.com
  • TTL, seconds
    300
    Type
    A
    Value
    173.194.64.132
  • 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
df5f64f180a7d2ab12c150dcb1b1c5ce
SHA-256
fadd233a6c56e1e80d8f04b45a10d6c9e3ad14ba6d28401c13599390461a9cfd
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": 46,
    "malicious": 11,
    "suspicious": 1,
    "undetected": 34
}
Vendor labels
{
    "ESET": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "SOCRadar": "suspicious",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Google Safe Browsing": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
MarkMonitor Inc.
Created
2000-07-31T21:38:58Z
Expires
2027-07-31T21:38:58Z
Updated
2026-06-29T10:34:06Z
First seen
2026-11-06T18:08:15Z
DNS records
[
    {
        "ttl": 300,
        "type": "CNAME",
        "value": "blogspot.l.googleusercontent.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "173.194.64.132"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2607:f8b0:4001:c6a::84"
    }
]
Dns at
2026-11-06T18:08:25Z
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": "df5f64f180a7d2ab12c150dcb1b1c5ce",
    "sha256": "fadd233a6c56e1e80d8f04b45a10d6c9e3ad14ba6d28401c13599390461a9cfd",
    "subject": "misc-sni.blogspot.com",
    "valid_to": "2026-12-30T19:08:51Z",
    "valid_from": "2026-10-07T19:08:52Z"
}
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-31T07: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 collector summary

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

source
VirusTotal
scope
unknown
result_state
observed
numerator
12
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","ESET","Emsisoft","Fortinet","G-Data","Google Safe Browsing","Gridinsoft","Lionic","Netcraft","SOCRadar","Webroot"]
observed_at
2026-11-06 18:08:15
checked_at
2026-11-08 03:16:00
fetched_at
2026-11-08 02:16:01
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

7beb79d9-4fd4-453d-b5d9-df918f4e3c25

Final URL

https://rewardbuxclaimhere.blogspot.com/

HTTP response

404

Navigation history

  • URL
    https://rewardbuxclaimhere.blogspot.com/
    Status
    404

DOM structure hash

c7ac6bf954f4bdddc3973031e94ef3fa1fbe56e830a188485b72ecebc049f7a9

Document hash

d3e7a5d7bda307b411f46b5d0240ef4c31b741b1539c91a282b501a73e1e1324

URL risk categories

  • Phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    rewardbuxclaimhere.blogspot.com
    Type
    CNAME
    Value
    blogspot.l.googleusercontent.com
  • Name
    rewardbuxclaimhere.blogspot.com
    Type
    CNAME
    Value
    blogspot.l.googleusercontent.com

DNSSEC valid

No

IP address

127.0.1.7

127.0.1.7 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
MarkMonitor Inc.
Registered
Updated
Expires
Nameservers
  • ns1.google.com
  • ns2.google.com
  • ns3.google.com
  • ns4.google.com
Original source fields · JSON
Uuid
7beb79d9-4fd4-453d-b5d9-df918f4e3c25
Final url
https://rewardbuxclaimhere.blogspot.com/
Status
404
History
[
    {
        "url": "https://rewardbuxclaimhere.blogspot.com/",
        "status": 404
    }
]
DOM structure hash
c7ac6bf954f4bdddc3973031e94ef3fa1fbe56e830a188485b72ecebc049f7a9
Document hash
d3e7a5d7bda307b411f46b5d0240ef4c31b741b1539c91a282b501a73e1e1324
Url risks
[
    "Phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "rewardbuxclaimhere.blogspot.com",
        "type": "CNAME",
        "value": "blogspot.l.googleusercontent.com"
    },
    {
        "name": "rewardbuxclaimhere.blogspot.com",
        "type": "CNAME",
        "value": "blogspot.l.googleusercontent.com"
    }
]
Dnssec valid
false
Ip
127.0.1.7

127.0.1.7 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "created": "2000-07-31T21:38:58Z",
    "updated": "2026-06-29T10:34:06Z",
    "expires": "2027-07-31T21:38:58Z",
    "nameservers": [
        "ns1.google.com",
        "ns2.google.com",
        "ns3.google.com",
        "ns4.google.com"
    ]
}

Google Safe Browsing

Threat flag recorded

Open report

URLScan

Malicious · engine verdict · score 74

SHA-256 671c59fe116c540684d2209eaecc2915fea5ed17219c04a50d5cd55ce3c8fa5f

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a1b61a-ee4b-7159-ae15-f1ac34eba08a

Final URL

https://www.rewardbuxclaimhere.blogspot.com/

HTTP response

404

Redirect type

https-only

Redirects

  • To
    https://www.rewardbuxclaimhere.blogspot.com/
    From
    http://www.rewardbuxclaimhere.blogspot.com/
    Status
    307

IP address

2a00:1450:4001:c13::84

Contacted domains

  • www.gstatic.com
  • fonts.gstatic.com
  • fonts.googleapis.com
  • ogads-pa.clients6.google.com
  • www.blogger.com
  • www.google.com
  • play.google.com

Contacted IP addresses

  • 2a00:1450:4001:c25::5f
  • 142.251.110.94
  • 2a00:1450:4001:c15::bf
  • 142.251.151.119
  • 2a00:1450:4001:c15::5f
  • 2a00:1450:4001:c13::84

Autonomous systems (ASN)

  • 15169

Server countries

  • DE
  • US

Linked domains

  • www.google.ch
  • accounts.google.com
  • support.google.com
  • www.blogger.com
  • www.google.de

Document hash

f8604e7c8385c7ca948297af341de37803ce951f3ba157c85c42269a0fb4a427

JavaScript globals

  • d
  • g
  • m
  • n
  • p
  • r
  • t
  • u
  • v
  • w
  • x
  • y
  • A
  • B
  • C
  • D
  • E
  • F
  • G
  • H
  • gbar_
  • _F_toggles_gbar_
  • gbar
  • __PVT
  • closure_uid_120683188
  • closure_lm_457022
  • onegoog

TLS session and certificate

Subject alternative names
  • *.googleusercontent.com
  • commondatastorage.googleapis.com
  • *.commondatastorage.googleapis.com
  • storage.googleapis.com
  • *.storage.googleapis.com
  • storage-p2.googleapis.com
  • *.storage-p2.googleapis.com
  • storage.mtls.googleapis.com
  • *.appspot.com.storage.googleapis.com
  • *.content-storage.googleapis.com
Cipher
AES_128_GCM
Issuer
WR2
Subject
*.googleusercontent.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

0

Registered domain age, days

0

Certificate age, days

30

Certificate validity, days

83

Page requests

17

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-2aab354
Score
74
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
GSE
Content-type
text/html; charset=UTF-8
Content-security-policy
frame-ancestors 'self'
X-frame-options
SAMEORIGIN
X-content-type-options
nosniff
Original source fields · JSON
Uuid
01a1b61a-ee4b-7159-ae15-f1ac34eba08a
Final url
https://www.rewardbuxclaimhere.blogspot.com/
Status
404
Redirected
https-only
Redirects
[
    {
        "to": "https://www.rewardbuxclaimhere.blogspot.com/",
        "from": "http://www.rewardbuxclaimhere.blogspot.com/",
        "status": 307
    }
]
Ip
2a00:1450:4001:c13::84
Contacted domains
[
    "www.gstatic.com",
    "fonts.gstatic.com",
    "fonts.googleapis.com",
    "ogads-pa.clients6.google.com",
    "www.blogger.com",
    "www.google.com",
    "play.google.com"
]
Contacted IP addresses
[
    "2a00:1450:4001:c25::5f",
    "142.251.110.94",
    "2a00:1450:4001:c15::bf",
    "142.251.151.119",
    "2a00:1450:4001:c15::5f",
    "2a00:1450:4001:c13::84"
]
Asns
[
    "15169"
]
Countries
[
    "DE",
    "US"
]
Linked domains
[
    "www.google.ch",
    "accounts.google.com",
    "support.google.com",
    "www.blogger.com",
    "www.google.de"
]
Document hash
f8604e7c8385c7ca948297af341de37803ce951f3ba157c85c42269a0fb4a427
Globals
[
    "d",
    "g",
    "m",
    "n",
    "p",
    "r",
    "t",
    "u",
    "v",
    "w",
    "x",
    "y",
    "A",
    "B",
    "C",
    "D",
    "E",
    "F",
    "G",
    "H",
    "gbar_",
    "_F_toggles_gbar_",
    "gbar",
    "__PVT",
    "closure_uid_120683188",
    "closure_lm_457022",
    "onegoog"
]
Tls
{
    "san": [
        "*.googleusercontent.com",
        "commondatastorage.googleapis.com",
        "*.commondatastorage.googleapis.com",
        "storage.googleapis.com",
        "*.storage.googleapis.com",
        "storage-p2.googleapis.com",
        "*.storage-p2.googleapis.com",
        "storage.mtls.googleapis.com",
        "*.appspot.com.storage.googleapis.com",
        "*.content-storage.googleapis.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR2",
    "subject": "*.googleusercontent.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-30T19:08:58Z",
    "valid_from": "2026-10-07T19:08:59Z"
}
Domain age days
0
Apex age days
0
Tls age days
30
Tls valid days
83
Requests
17
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-2aab354"
        ],
        "score": 74,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "GSE",
    "content-type": "text/html; charset=UTF-8",
    "content-security-policy": "frame-ancestors 'self'",
    "x-frame-options": "SAMEORIGIN",
    "x-content-type-options": "nosniff"
}
Separate monitor record · 2026-11-08 04:31 UTC

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

record_source
domain_monitor.urlscan
uuid
01a1b61a-ee4b-7159-ae15-f1ac34eba08a
score
0
malicious
false
result_at
2026-11-08T04:31:11Z
enriched_at
null
source_timestamps
{"urlscan_result_at":"2026-11-08 05:31:11","urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

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: 15 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

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

DNS servers

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

Location

IP address
2a00:1450:4001:c1f::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:c1f::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
0
Permissions-Policy
No
X-Content-Type-Options
No
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:c1f::84
IP version
6

Technology stack

Technologies
  • Blogger
  • Python
  • Java
  • OpenGSE
  • Google Font API
  • Closure Library
  • HTTP/3

HTTP headers

Response headers
Server
scaffolding on HTTPServer2
Content-type
text/html
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
}
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
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "216.239.36.10",
            "host": "ns3.google.com"
        },
        {
            "ip": "216.239.38.10",
            "host": "ns4.google.com"
        },
        {
            "ip": "216.239.32.10",
            "host": "ns1.google.com"
        },
        {
            "ip": "216.239.34.10",
            "host": "ns2.google.com"
        }
    ],
    "zone": "blogspot.com"
}
Location
{
    "ip": "2a00:1450:4001:c1f::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:c1f::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": "0",
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "2a00:1450:4001:c1f::84",
    "family": 6
}
Tech stack
{
    "technologies": [
        "Blogger",
        "Python",
        "Java",
        "OpenGSE",
        "Google Font API",
        "Closure Library",
        "HTTP/3"
    ]
}
HTTP headers
{
    "headers": {
        "server": "scaffolding on HTTPServer2",
        "content-type": "text/html"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Security threats Phishing
View full Cloudflare Radar report

Questions about rewardbuxclaimhere.blogspot.com

Is rewardbuxclaimhere.blogspot.com legit?

PhishDestroy rates rewardbuxclaimhere.blogspot.com as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-11-07. Stored VirusTotal result: 12/92 engines flagged. malicious: 11. suspicious: 1. Analysis time (as stored): 2026-11-06T18:08:15Z. Retrieved (as stored): 2026-11-08T02:16:00Z. Google Safe Browsing flags it. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

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

This report does not record which wallet requests rewardbuxclaimhere.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 rewardbuxclaimhere.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

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

Checked, no match

Last checked

Stored Capture · 7 captures

URLScan · 2026-11-07 1 / 7
SourceURLScan · 2026-11-07
Recorded
StateStored capture
HTTP status404
Final URLhttps://www.rewardbuxclaimhere.blogspot.com/
Position1 / 7
Open capture Source Report Wayback Download
All capture links and hashes (7)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 74 report ↗
Google Safe Browsing Flagged Social engineering checked Nov 8, 2026
IP Reputation Germany172.253.152.132 abuse score 0/100 0 reports checked Nov 7, 2026 last reported
Platform provider MarkMonitor
Abuse contact["abusecomplaints@markmonitor.com", "2d8644446d24f14as@"]
HTTP Status404 Not Found
Technical detailsProvenance & timestamps
First DetectedNov 7, 2026
Submitted URLhttp://rewardbuxclaimhere.blogspot.com/
Observed page title
Блог не найден
TLS Certificate
Issued by WR2 · stored validity ends in 52 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Germany172.253.152.132
Network ASN
AS15169
Organization
Google LLC
Observed location
GermanyFrankfurt am Main, DE
Server header
GSE

Nameservers 4

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

Location describes the IP network.

TLS certificate

Issuer
WR2
Valid from
2026-10-07 19:08:59
Valid until
2026-12-30 19:08:58
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintfadd233a6c56e1e80d8f04b45a10d6c9e3ad14ba6d28401c13599390461a9cfd
Certificate names · 10 SANs
  • *.googleusercontent.com
  • commondatastorage.googleapis.com
  • *.commondatastorage.googleapis.com
  • storage.googleapis.com
  • *.storage.googleapis.com
  • storage-p2.googleapis.com
  • *.storage-p2.googleapis.com
  • storage.mtls.googleapis.com
  • *.appspot.com.storage.googleapis.com
  • *.content-storage.googleapis.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 · 172.253.152.132rapiddns.io

Latest Classified Outcome 2026-11-08 00:35:53 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: Stale Registration: Unknown
Latest HTTP observation Inactive Http No Content 70% 2026-11-08 00:35:53 UTC
RDAP registration
Observed timeline current episode first observed: 2026-11-07 14:27:50 UTC first terminal observation: 2026-11-07 14:27:50 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Threat Intel Cross-Reference · source references
ScamAdviser Public lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
View on ScamAdviser
Fetched directly from the site by PhishDestroy · cached up to 24 h
Technologies · 5 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

12 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
ESET
G-Data
Lionic
Webroot
Emsisoft
Fortinet
Netcraft
SOCRadar
Gridinsoft
BitDefender
alphaMountain.ai
Google Safe Browsing
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of rewardbuxclaimhere.blogspot.com · checked Nov 7, 2026

91
Good
Performance
FCP
1.92 s
First Contentful Paint
LCP
3.12 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
9 ms
Total Blocking Time
SI
3.15 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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 404
Requested URL: http://rewardbuxclaimhere.blogspot.com/
وبلاگ یافت نشد
‏Blogger یک ابزار انتشار وبلاگ است که توسط Google برای اشتراک آسان نظرات شما با دنیا ارائه شده است. Blogger، ارسال متن، عکس و فیلم را به وبلاگ شخصی یا گروهی شما به راحتی امکان‌پذیر می‌کند.
Response
HTTP 404
HTML body
116.8 KB
Compressed
35.7 KB
Links
2 internal · 12 external
Selected response headers
Content-Type: text/html; charset=UTF-8
Content-Encoding: gzip
Cache-Control: private, max-age=0
Server: GSE
Security headers present
Content-Security-PolicyX-Frame-OptionsX-Content-Type-OptionsX-XSS-Protection
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 11
Cache-Control
private, max-age=0
Content-Encoding
gzip
Content-Length
36646
Content-Security-Policy
frame-ancestors 'self'
Content-Type
text/html; charset=UTF-8
Date
Sat, 07 Nov 2026 14:17:52 GMT
Expires
Sat, 07 Nov 2026 14:17:52 GMT
Server
GSE
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN
X-XSS-Protection
1; mode=block

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

Archived
Registration & observation details3

Availability observations

Outcome first observed
Observation window ends
Estimate basis
first_observation_only

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: 17 SHA-256 hashes: 13 URLScan scan:

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

Open this scan on URLScan 01a1b61a-ee4b-7159-ae15-f1ac34eba08a ↗

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
Блог не найден
Crawler
وبلاگ یافت نشد
rewardbuxclaimhere.blogspot.com
Stored observation history3

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

  1. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  2. Availability monitor · Recorded state

    inactive

    http_no_content

  3. Availability monitor · Recorded state

    inactive

    http_no_content

All retained availability observations5

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-08 01:35:53.000000
    Evidence SHA-256
    4a0fa35c3e23d8736767de8ea2c55e7c0b98b6913d58b4fecdec42565af03deb
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-11-08 01:35:53
    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-08 01:35:53.000000
    Evidence SHA-256
    4a0fa35c3e23d8736767de8ea2c55e7c0b98b6913d58b4fecdec42565af03deb
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-11-08 01:35:53
    Evidence reason
    http_other
  3. 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-11-07 23:22:04.326583
    Evidence SHA-256
    19ed99e260d67463304cd035997394a09991119b8c1f635f2967c41ae291fdce
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 23:22:04.326583
    Evidence reason
  4. current_state_backfillinactive
    Observation source
    current_state_backfill
    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-11-07 15:27:50.000000
    Evidence SHA-256
    a50a964c33085f3f7730b65f77febbdc82b0a155ef839ebe2764e0882629cf82
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-11-07 15:27:50
    Evidence reason
  5. 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-07 15:27:50.000000
    Evidence SHA-256
    a50a964c33085f3f7730b65f77febbdc82b0a155ef839ebe2764e0882629cf82
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-11-07 15:27:50
    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
    rewardbuxclaimhere.blogspot.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Google Safe Browsing · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 74
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • VirusTotal
    Detections recorded on VirusTotal: 12/92
  • Google Safe Browsing
    Listed as unsafe by Google Safe Browsing (Google Transparency Report)
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as Phishing, Security threats
  • 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 Recorded: 1 of 1

Recorded activity

5 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. Cloudflare Radar

    Phishing

    View source
  3. Added to PhishDestroy

    rewardbuxclaimhere.blogspot.com

    View source
  4. URLScan

    Malicious · engine verdict · score 74

    View source
  5. VirusTotal

    12/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
All stored records by source

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

Download all records as JSON

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 12 det. ChainPatrol URLQuery Google SB Flagged SSL Labs Certificate hostname mismatch CF Radar Malicious 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 HTTP 404 · 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 rewardbuxclaimhere.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/rewardbuxclaimhere.blogspot.com"
  title="PhishDestroy threat report for rewardbuxclaimhere.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>