Skip to security report
This domain has been flagged as malicious
Security engines reporting a detection: 14. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
caznelo.shop favicon

caznelo.shop

In short

caznelo.shop is a phishing page detected by PhishDestroy on 2026-10-24.

Registrar
Spaceship
Resolved IP
45.151.91.66
Registered
Oct 10, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 14/92 Spamhaus DBL: spam domain Young domain: 16 days old
VirusTotal
engine detections ·
OTX
community references
Cloudflare Radar
source verdict
Page captures
open gallery
Domain age
Reports sent
No sent record
OTX: 3 refs Oct 24, 2026
X Telegram API

Analysis

Domain summary

caznelo.shop is a phishing page detected by PhishDestroy on 2026-10-24. Risk: critical (100/100). Registrar: Spaceship. Status: Last known active. Hosting: IP Vendetta Inc. VirusTotal: 14/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

Critical
VirusTotal
14 / 92
OTX
3 community refs
Page captures
5

PhishDestroy threat report

Overview

PhishDestroy listed caznelo.shop on its internal blocklist as a suspicious domain because the page performed an HTTP redirect to mipzaro.shop, which was noted in the intake reason. The domain was first observed by PhishDestroy on 2026-10-24. An HTTP request on that date returned a 200 status after the cross‑site redirect.

How the scam works

Redirector domains are commonly used to hide the final destination and can funnel visitors to phishing sites, malware distributors, or other fraudulent services. No specific malicious payload or credential‑capture page was observed in the recorded response.

Evidence

VirusTotal scanned the domain on 2026-10-24, reporting 14 detections from 92 engines – 11 labeled malicious and 3 suspicious, with vendors such as BitDefender, G‑Data and Kaspersky flagging it as phishing. Google Safe Browsing checked on the same day did not flag the site, while URLScan’s analysis on 2026-10-14 gave a high malicious score (97) but an overall non‑malicious verdict, and Cloudflare Radar on 2026-10-24 marked the domain as malicious under the malware category. OTX listed three pulses referencing caznelo.shop, and PhishDestroy’s internal blocklist contains the domain, matching the intake note that the redirect to mipzaro.shop triggered the alert.

Infrastructure

The domain was registered four days before its first observation, and a Let's Encrypt certificate issued on 2026-10-14 was valid until 2027-01-12. The recorded IP was 45.151.91.66, belonging to ASN 209101 (IP Vendetta Inc.) and the country code SC; DNSSEC was observed as enabled and the authoritative nameservers were launch1.spaceship.net and launch2.spaceship.net. Port scans on the recorded address showed ports 22, 80 and 443 open, and the HTTP response included an HSTS header with a max‑age of 63072000 seconds.

What to do

Visitors should avoid interacting with caznelo.shop and refrain from entering credentials or personal data. Defenders should add the exact domain to blocklists, monitor network logs for connections to it, and treat any traffic as potentially malicious.

Source evidenceVirusTotal 14 / 92 · OTX 3 references 7 sources

VirusTotal

14 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 8 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
46
Malicious
11
Suspicious
3
Undetected
32

Vendor labels

CRDF
malicious
DNS8
suspicious
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Sophos
phishing
Fortinet
spam
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
phishing
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

First seen

DNS records

  • TTL, seconds
    1800
    Type
    NS
    Value
    launch2.spaceship.net
  • TTL, seconds
    3600
    Type
    A
    Value
    45.151.91.66
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    support.spaceship.com
    Value
    launch1.spaceship.net
  • TTL, seconds
    1800
    Type
    NS
    Value
    launch1.spaceship.net

DNS records observed

JARM fingerprint

1dd40d40d00040d00042d43d000000ffd4768d0539f26c1eea462bed21f172

Certificate

Subject alternative names
  • caznelo.shop
  • www.caznelo.shop
Issuer
Let's Encrypt / YE1
Serial
572b762a494f00ff652a9b2601f0c92aff1
SHA-256
47bbc403465c5a3588791b3f79e3a2b4e3239ca542e349fc434ddc91a701a664
Subject
caznelo.shop
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 11,
    "suspicious": 3,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Sophos": "phishing",
    "Fortinet": "spam",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
First seen
2026-10-14T09:04:54Z
DNS records
[
    {
        "ttl": 1800,
        "type": "NS",
        "value": "launch2.spaceship.net"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "45.151.91.66"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "support.spaceship.com",
        "value": "launch1.spaceship.net"
    },
    {
        "ttl": 1800,
        "type": "NS",
        "value": "launch1.spaceship.net"
    }
]
Dns at
2026-10-23T14:42:44Z
Jarm
1dd40d40d00040d00042d43d000000ffd4768d0539f26c1eea462bed21f172
Certificate
{
    "san": [
        "caznelo.shop",
        "www.caznelo.shop"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "572b762a494f00ff652a9b2601f0c92aff1",
    "sha256": "47bbc403465c5a3588791b3f79e3a2b4e3239ca542e349fc434ddc91a701a664",
    "subject": "caznelo.shop",
    "valid_to": "2027-01-12T07:34:11Z",
    "valid_from": "2026-10-14T07:34:12Z"
}
Separate source record · 11 malicious + 3 suspicious / 92 · 2026-10-23 14:39:31 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-23T14:39:31Z
fetched_at
2026-10-24T06:19:32Z
stats
{"timeout":0,"harmless":46,"malicious":11,"suspicious":3,"undetected":32}

Cloudflare Radar

Malicious

Not recorded
Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

8ad85c3e-c03e-4c55-b59c-f6d0d84dd747

Final URL

https://caznelo.shop/

HTTP response

200

Navigation history

  • URL
    https://caznelo.shop/
    Status
    200

DOM structure hash

a7fe83ec64bb23eb28090598db3d166ed98e52e39d1afbbfd74c579553f93e4e

Domain risk categories

  • New Domains
  • Security Risks
  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    caznelo.shop
    Type
    A
    Value
    45.151.91.66

DNSSEC valid

Yes

IP address

45.151.91.66

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware
Original source fields · JSON
Uuid
8ad85c3e-c03e-4c55-b59c-f6d0d84dd747
Final url
https://caznelo.shop/
Status
200
History
[
    {
        "url": "https://caznelo.shop/",
        "status": 200
    }
]
DOM structure hash
a7fe83ec64bb23eb28090598db3d166ed98e52e39d1afbbfd74c579553f93e4e
Domain risks
[
    "New Domains",
    "Security Risks",
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "caznelo.shop",
        "type": "A",
        "value": "45.151.91.66"
    }
]
Dnssec valid
true
Ip
45.151.91.66
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}

Spamhaus DBL

spam domain

URLScan

Malicious · engine verdict · score 97

Open report
URLScanOriginal source recordObserved: 17 fields

Observed: · Retrieved:

Report ID

01a139ed-59f9-7229-a09e-b29ebbbd9d46

Final URL

https://caznelo.shop/

HTTP response

200

Redirect type

https-only

IP address

45.151.91.66

Contacted IP addresses

  • 45.151.91.66

Autonomous systems (ASN)

  • 209101

Server countries

  • BG

Document hash

e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

TLS session and certificate

Subject alternative names
  • caznelo.shop
  • www.caznelo.shop
Cipher
AES_128_GCM
Issuer
YE1
Subject
caznelo.shop
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

4

Registered domain age, days

4

Certificate age, days

0

Certificate validity, days

89

Page requests

2

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
97
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
LiteSpeed
Content-type
text/html; charset=UTF-8
Strict-transport-security
max-age=63072000; includeSubDomains; preload
X-frame-options
SAMEORIGIN
X-content-type-options
nosniff
Referrer-policy
strict-origin-when-cross-origin
Original source fields · JSON
Uuid
01a139ed-59f9-7229-a09e-b29ebbbd9d46
Final url
https://caznelo.shop/
Status
200
Redirected
https-only
Ip
45.151.91.66
Contacted IP addresses
[
    "45.151.91.66"
]
Asns
[
    "209101"
]
Countries
[
    "BG"
]
Document hash
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Tls
{
    "san": [
        "caznelo.shop",
        "www.caznelo.shop"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "caznelo.shop",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-12T07:34:11Z",
    "valid_from": "2026-10-14T07:34:12Z"
}
Domain age days
4
Apex age days
4
Tls age days
0
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 97,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "LiteSpeed",
    "content-type": "text/html; charset=UTF-8",
    "strict-transport-security": "max-age=63072000; includeSubDomains; preload",
    "x-frame-options": "SAMEORIGIN",
    "x-content-type-options": "nosniff",
    "referrer-policy": "strict-origin-when-cross-origin"
}
Separate monitor record · 2026-10-24 19:23 UTC

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

record_source
domain_monitor.urlscan
uuid
01a139ed-59f9-7229-a09e-b29ebbbd9d46
score
0
malicious
false
result_at
2026-10-24T19:23:06Z
enriched_at
2026-10-25T09:15:35Z
source_timestamps
{"urlscan_result_at":"2026-10-24 21:23:06","urlscan_enriched_at":"2026-10-25 10:15:35"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

3 community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

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

ai_title
caznelo.shop — Suspicious Domain
ai_description
PhishDestroy flags caznelo.shop as a suspicious domain that redirects to mipzaro.shop, with multiple VirusTotal detections and a malicious Cloudflare Radar rating.
ai_generated_at
2026-10-24T06:20:52Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider observation dates.

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

Collected source details

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

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

Mail configuration

SPF lookups
0

CAA records

Domain
caznelo.shop

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
1
Archived days
3
Snapshots per day
0.16
Average page size, bytes
703

Trackers

Requests
1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
204
TLS
28
Waiting
83
Connection
16
Download
0
Response time, ms
331

TLS connection

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

Ports

Open ports
  • 22
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    162.159.26.38
    Host
    launch1.spaceship.net
  • IP address
    162.159.27.32
    Host
    launch2.spaceship.net
DNS zone
caznelo.shop

Location

IP address
45.151.91.66
ASN
209101
Organization
IP Vendetta Inc.
City
Victoria
Country
SC

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
caznelo.shop

DNS records

A
  • 45.151.91.66
NS
  • launch2.spaceship.net
  • launch1.spaceship.net
SOA
Primary nameserver
launch1.spaceship.net
Hostmaster
support.spaceship.com
Serial
1791966655
Refresh, seconds
43200
Retry, seconds
3600
Expiry, seconds
604800
Minimum TTL, seconds
3600

DNSSEC

DS record
Yes
RRSIG
Yes
DNSKEY
Yes

HSTS

Header value
max-age=63072000; includeSubDomains; preload
Observation
Site is compatible with the HSTS preload list!
Preload compatible
Yes

HTTP security policies

X-Frame-Options
SAMEORIGIN
Referrer-Policy
strict-origin-when-cross-origin
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
No
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
45.151.91.66
IP version
4

Redirects

Redirect chain
  • https://caznelo.shop

HTTP headers

Response headers
Server
LiteSpeed
Content-type
text/html; charset=UTF-8
Strict-transport-security
max-age=63072000; includeSubDomains; preload
X-frame-options
SAMEORIGIN
X-content-type-options
nosniff
Referrer-policy
strict-origin-when-cross-origin
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "caznelo.shop"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-24T05:16:57Z",
    "first": "2026-10-11T23:05:53Z",
    "changes": 1,
    "days_archived": 3,
    "scans_per_day": 0.16,
    "avg_page_bytes": 703
}
Trackers
{
    "requests": 1
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 204,
        "tls": 28,
        "wait": 83,
        "connect": 16,
        "download": 0
    },
    "response_ms": 331
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.26.38",
            "host": "launch1.spaceship.net"
        },
        {
            "ip": "162.159.27.32",
            "host": "launch2.spaceship.net"
        }
    ],
    "zone": "caznelo.shop"
}
Location
{
    "ip": "45.151.91.66",
    "asn": "209101",
    "org": "IP Vendetta Inc.",
    "city": "Victoria",
    "country": "SC"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "caznelo.shop"
}
DNS records
{
    "A": [
        "45.151.91.66"
    ],
    "NS": [
        "launch2.spaceship.net",
        "launch1.spaceship.net"
    ],
    "SOA": "{\"nsname\": \"launch1.spaceship.net\", \"hostmaster\": \"support.spaceship.com\", \"serial\": 1791966655, \"refresh\": 43200, \"retry\": 3600, \"expire\": 604800, \"minttl\": 3600}"
}
Dnssec
{
    "ds": true,
    "rrsig": true,
    "dnskey": true
}
Hsts
{
    "header": "max-age=63072000; includeSubDomains; preload",
    "message": "Site is compatible with the HSTS preload list!",
    "compatible": true
}
HTTP security policies
{
    "xFrameOptions": "SAMEORIGIN",
    "referrerPolicy": "strict-origin-when-cross-origin",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=63072000; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "45.151.91.66",
    "family": 4
}
Redirects
{
    "chain": [
        "https://caznelo.shop"
    ]
}
HTTP headers
{
    "headers": {
        "server": "LiteSpeed",
        "content-type": "text/html; charset=UTF-8",
        "strict-transport-security": "max-age=63072000; includeSubDomains; preload",
        "x-frame-options": "SAMEORIGIN",
        "x-content-type-options": "nosniff",
        "referrer-policy": "strict-origin-when-cross-origin"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Security threats Security Risks Malware Malware New Domains

Questions about caznelo.shop

Is caznelo.shop legit?

No. PhishDestroy classifies caznelo.shop as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-24. VirusTotal: 14/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is caznelo.shop safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on caznelo.shop. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used caznelo.shop?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 5 captures

All capture links and hashes (5)
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 78 days

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 24, 2026
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Spaceship US(US)
RegistrationCreated Oct 10, 2026 (16d · Very New!) — Expires Oct 10, 2027
HTTP Status302 Found (Temporary)
Technical detailsProvenance & timestamps
First DetectedOct 24, 2026
Submitted URLhttp://caznelo.shop/
Favicon Hash
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
45.151.91.66
Network ASN
AS209101
Organization
IP Vendetta Inc.
Observed location
Victoria, SC
Server header
LiteSpeed

Nameservers 2

  • launch2.spaceship.net
  • launch1.spaceship.net

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-14 07:34:12
Valid until
2027-01-12 07:34:11
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint47bbc403465c5a3588791b3f79e3a2b4e3239ca542e349fc434ddc91a701a664
Certificate names · 2 SANs
  • caznelo.shop
  • www.caznelo.shop

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

Latest Classified Outcome 2026-10-25 11:01:26 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-25 11:01:26 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-25 02:54:26 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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.caznelo.shopDomain record

The original observation time is not recorded for these hostnames.

Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

14 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 14 detections
alphaMountain.ai
BitDefender
CRDF
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Seclookup
SOCRadar
Sophos
VIPRE

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://caznelo.shop/
Final URL: https://mipzaro.shop/
Response
HTTP 200
HTML body
0 B
Compressed
20 B
Links
0 internal · 0 external
Selected response headers
Server: LiteSpeed
Cache-Control: no-transform
Content-Type: text/html; charset=UTF-8
Security headers present
Strict-Transport-SecurityX-Frame-OptionsX-Content-Type-OptionsReferrer-Policy
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 13
Cache-Control
no-transform
Connection
Keep-Alive
Content-Length
0
Content-Type
text/html; charset=UTF-8
Date
Sat, 24 Oct 2026 05:15:48 GMT
Keep-Alive
timeout=3, max=1000
Referrer-Policy
strict-origin-when-cross-origin
Server
LiteSpeed
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
Vary
Accept-Encoding
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN
X-turbo-charged-by
LiteSpeed

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

Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

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

Stored observation history2

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

  1. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

All retained availability observations9

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_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-25 12:01:26.000000
    Evidence SHA-256
    14373e35a295494bf96c108513f0b412ef7e0e7a06cac7cacebae3f3758d8ba2
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-25 12:01:26
    Evidence reason
    redirect
  2. 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-25 12:01:26.000000
    Evidence SHA-256
    14373e35a295494bf96c108513f0b412ef7e0e7a06cac7cacebae3f3758d8ba2
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-25 12:01:26
    Evidence reason
    redirect
  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-10-25 09:55:07.418941
    Evidence SHA-256
    f29421045a2f0d44850c6f52d6d8bbdf0829af36630a6ed5c83feca2dfe013b6
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 09:55:07.418941
    Evidence reason
  4. 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-25 03:54:26.000000
    Evidence SHA-256
    15ab6776b1771455c7ef828dadc849efe21b2c39709eeaa38832defe87032acf
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-25 03:54:26
    Evidence reason
    redirect
  5. 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-25 03:54:26.000000
    Evidence SHA-256
    15ab6776b1771455c7ef828dadc849efe21b2c39709eeaa38832defe87032acf
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-25 03:54:26
    Evidence reason
    redirect
  6. 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-24 12:00:24.000000
    Evidence SHA-256
    b9c6f5ae36068524cd8f6b9c29607b2ecb2fcb32b02ec9d1fbb37f3b3b83e906
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-24 12:00:24
    Evidence reason
    redirect
  7. 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-24 12:00:24.000000
    Evidence SHA-256
    b9c6f5ae36068524cd8f6b9c29607b2ecb2fcb32b02ec9d1fbb37f3b3b83e906
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-24 12:00:24
    Evidence reason
    redirect
  8. 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-24 10:55:03.666169
    Evidence SHA-256
    3db3280361d0b0da230e0746730e29bf48f3dcd3dc85a990b2931515e779b43a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-24 10:55:03.666169
    Evidence reason
  9. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 07:18:40.850403
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Recorded activity

5 entries
  1. AlienVault OTX

    3 community references

    View source
  2. VirusTotal

    14/92 engine detections

    View source
  3. Wayback Machine

    Page archived

    View source
  4. Added to PhishDestroy

    caznelo.shop

    View source
  5. URLScan

    Malicious · engine verdict · score 97

    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.

Check for cloaking

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

caznelo.shop

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked Last known active
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.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes

Report to Your Local Authorities

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

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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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 caznelo.shop)
  • Communications — emails, texts, phone numbers, usernames the scammer used

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

Where should I report the scam?

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

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

How do phishing scams typically work?

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

How can I protect myself in the future?

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

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

Stay Informed, Stay Safe

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

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

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

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/caznelo.shop"
  title="PhishDestroy threat report for caznelo.shop"
  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>