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

cryptospinly.io

In short

PhishDestroy records that the captured cryptospinly.io page returned blank content with no visible elements to inspect.

Review the evidence
Registrar
RussiaNiceNIC
Resolved IP
Canada172.67.196.203Cloudflare, Inc. · CDN
Registered
Oct 27, 2026
First observed
Nov 1, 2026
PhishDestroy assessment High
55/100
Evidence score
First observed Nov 1, 2026 06:37 UTC · PhishDestroy
Risk signals
VirusTotal detections: 1/92 Young domain: 4 days old
VirusTotal
1 / 92
engine detections ·
OTX
2
community references
URLScan
Malicious
engine verdict · score 8
Page captures
2
open gallery
Domain age
4 days
registered 2026-10-27 according to WHOIS
OTX: 2 refs Nov 1, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy records that the captured cryptospinly.io page returned blank content with no visible elements to inspect.

High
VirusTotal
1 / 92
Hosting
Canada172.67.196.203Cloudflare, Inc. · CDN
Registrar
RussiaNiceNIC
Registered
Oct 27, 2026
OTX
2 community refs
Page captures
2
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The stored capture of cryptospinly.io shows a completely blank white surface with no logo, text, form field, control or other visible element, so no page purpose or main interaction can be identified from the screenshot. The capture content status is recorded as blank, and the page title metadata describes this empty result rather than any hidden layout, leaving nothing on the image to inspect or interact with.

The stored VirusTotal domain result reports 1 detection out of 92 engines. Fortinet reported "spam".

Source evidenceVirusTotal 1 / 92 · OTX 2 references 6 sources

VirusTotal

1 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
0
Suspicious
1
Undetected
38

Vendor labels

Fortinet
spam

Reputation score

0

Registrar

NICENIC INTERNATIONAL GROUP CO., LIMITED

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    mack.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.21.63
  • TTL, seconds
    21600
    Type
    NS
    Value
    mack.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    sloan.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.196.203

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.cryptospinly.io
  • cryptospinly.io
Issuer
Let's Encrypt / YE1
Serial
5e9e12ce57cf1211a859146663aacefd49c
SHA-256
94019bb427a263976fd74983c7a384f08410ff9cf4f5d2eef6e7eb529c58ba23
Subject
cryptospinly.io
Valid until
Valid from

Registration record

Registrar
NICENIC INTERNATIONAL GROUP CO., LIMITED
Registrar IANA ID
3765
Registrar URL
http://www.nicenic.net
Registered
Updated
Expires
Status
  • addPeriod
  • clientDeleteProhibited
  • clientTransferProhibited
Nameservers
  • mack.ns.cloudflare.com
  • sloan.ns.cloudflare.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • client delete prohibited
  • client transfer prohibited
Registry events
Expiration
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 0,
    "suspicious": 1,
    "undetected": 38
}
Vendor labels
{
    "Fortinet": "spam"
}
Reputation
0
Registrar
NICENIC INTERNATIONAL GROUP CO., LIMITED
Created
2026-10-27T09:15:37Z
Expires
2027-10-27T09:15:37Z
Updated
2026-10-27T09:15:37Z
First seen
2026-10-27T09:36:21Z
DNS records
[
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "mack.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.21.63"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "mack.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "sloan.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.196.203"
    }
]
Dns at
2026-11-01T06:29:34Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.cryptospinly.io",
        "cryptospinly.io"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "5e9e12ce57cf1211a859146663aacefd49c",
    "sha256": "94019bb427a263976fd74983c7a384f08410ff9cf4f5d2eef6e7eb529c58ba23",
    "subject": "cryptospinly.io",
    "valid_to": "2027-01-25T08:26:38Z",
    "valid_from": "2026-10-27T08:26:39Z"
}
Registration record
{
    "registrar": "NICENIC INTERNATIONAL GROUP CO., LIMITED",
    "registrar_iana_id": "3765",
    "registrar_url": "http://www.nicenic.net",
    "created": "2026-10-26T16:00:00Z",
    "updated": "2026-10-26T16:00:00Z",
    "expires": "2027-10-26T16:00:00Z",
    "status": [
        "addPeriod",
        "clientDeleteProhibited",
        "clientTransferProhibited"
    ],
    "nameservers": [
        "mack.ns.cloudflare.com",
        "sloan.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client delete prohibited",
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-26T16:00:00Z",
        "registration": "2026-10-26T16:00:00Z",
        "registrar expiration": "2027-10-26T16:00:00Z",
        "last update of RDAP database": "2026-10-27T09:36:10Z"
    }
}
Separate source record · 0 malicious + 1 suspicious / 92 · 2026-11-01 06:29:03 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-11-01T06:29:03Z
fetched_at
2026-11-01T07:11:36Z
stats
{"timeout":0,"harmless":53,"malicious":0,"suspicious":1,"undetected":38}

URLScan

Malicious · engine verdict · score 8

SHA-256 c396babd7f49262f18a3a2ec34542c8e314cb4d869875152bb9675a6bb6066ea

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a18c83-1d0f-70a1-a696-0d997077a0ea

Final URL

https://cryptospinly.io/

HTTP response

666

Redirect type

https-only

Redirects

  • To
    https://cryptospinly.io/
    From
    http://cryptospinly.io/
    Status
    307

IP address

172.67.196.203

Contacted domains

  • www.google.com

Contacted IP addresses

  • 142.251.156.119
  • 104.21.21.63

Autonomous systems (ASN)

  • 15169
  • 13335

Server countries

  • US

Document hash

c396babd7f49262f18a3a2ec34542c8e314cb4d869875152bb9675a6bb6066ea

Script hashes

  • 0bf32f6f5e0db7af1e5c2bf8701b0dda03b6b9fc7f09c66755a85200506b3a0b

TLS session and certificate

Subject alternative names
  • *.cryptospinly.io
  • cryptospinly.io
Cipher
AES_128_GCM
Issuer
YE1
Subject
cryptospinly.io
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

0

Registered domain age, days

0

Certificate age, days

3

Certificate validity, days

89

Page requests

4

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
01a18c83-1d0f-70a1-a696-0d997077a0ea
Final url
https://cryptospinly.io/
Status
666
Redirected
https-only
Redirects
[
    {
        "to": "https://cryptospinly.io/",
        "from": "http://cryptospinly.io/",
        "status": 307
    }
]
Ip
172.67.196.203
Contacted domains
[
    "www.google.com"
]
Contacted IP addresses
[
    "142.251.156.119",
    "104.21.21.63"
]
Asns
[
    "15169",
    "13335"
]
Countries
[
    "US"
]
Document hash
c396babd7f49262f18a3a2ec34542c8e314cb4d869875152bb9675a6bb6066ea
Script hashes
[
    "0bf32f6f5e0db7af1e5c2bf8701b0dda03b6b9fc7f09c66755a85200506b3a0b"
]
Tls
{
    "san": [
        "*.cryptospinly.io",
        "cryptospinly.io"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "cryptospinly.io",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-25T08:26:38Z",
    "valid_from": "2026-10-27T08:26:39Z"
}
Domain age days
0
Apex age days
0
Tls age days
3
Tls valid days
89
Requests
4
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 8,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8"
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a18c83-1d0f-70a1-a696-0d997077a0ea
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

2 community references

Open report

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Report ID

e80db38a-b914-4200-86ec-1ad82bd969f6

Final URL

https://cryptospinly.io/

HTTP response

666

Navigation history

  • URL
    https://cryptospinly.io/
    Status
    666

DOM structure hash

4a06835d00d712ec4c568b1f0ccf643fb099dec477093d1e3c35bff8ea5ca969

Document hash

b90534bd0cb5f2803375c5582fd5fc9a72a7a3bacb578b83595d76365d8d301b

Domain risk categories

  • Newly Seen Domains
  • Security Risks

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    cryptospinly.io
    Type
    A
    Value
    104.21.21.63
  • Name
    cryptospinly.io
    Type
    A
    Value
    172.67.196.203

DNSSEC valid

No

IP address

127.0.1.12

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

Registration record

Registrar
NICENIC INTERNATIONAL GROUP CO., LIMITED
Registered
Updated
Expires
Nameservers
  • mack.ns.cloudflare.com
  • sloan.ns.cloudflare.com
Original source fields · JSON
Uuid
e80db38a-b914-4200-86ec-1ad82bd969f6
Final url
https://cryptospinly.io/
Status
666
History
[
    {
        "url": "https://cryptospinly.io/",
        "status": 666
    }
]
DOM structure hash
4a06835d00d712ec4c568b1f0ccf643fb099dec477093d1e3c35bff8ea5ca969
Document hash
b90534bd0cb5f2803375c5582fd5fc9a72a7a3bacb578b83595d76365d8d301b
Domain risks
[
    "Newly Seen Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "cryptospinly.io",
        "type": "A",
        "value": "104.21.21.63"
    },
    {
        "name": "cryptospinly.io",
        "type": "A",
        "value": "172.67.196.203"
    }
]
Dnssec valid
false
Ip
127.0.1.12

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

Registration record
{
    "registrar": "NICENIC INTERNATIONAL GROUP CO., LIMITED",
    "created": "2026-10-27T09:15:37Z",
    "updated": "2026-10-27T09:15:37Z",
    "expires": "2027-10-27T09:15:37Z",
    "nameservers": [
        "mack.ns.cloudflare.com",
        "sloan.ns.cloudflare.com"
    ]
}

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
cryptospinly.io blank capture with no visible page content
ai_description
PhishDestroy records that the captured cryptospinly.io page returned blank content with no visible elements to inspect.
ai_summary
The stored capture of cryptospinly.io shows a completely blank white surface with no logo, text, form field, control or other visible element, so no page purpose or main interaction can be identified from the screenshot. The capture content status is recorded as blank, and the page title metadata describes this empty result rather than any hidden layout, leaving nothing on the image to inspect or interact with. The stored VirusTotal domain result reports 1 detection out of 92 engines. Fortinet reported "spam".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 08:13:27
revision
ed99891995b97e7b4154bd2cfb618bdf5a6e0a7fa2237fa09a1afafcdc6e4cf4
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

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

Collected source details

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

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

Mail configuration

SPF lookups
0

CAA records

Domain
cryptospinly.io

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

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
  • 8080

DNS servers

Nameservers
  • IP address
    108.162.194.52
    Host
    sloan.ns.cloudflare.com
  • IP address
    172.64.35.37
    Host
    mack.ns.cloudflare.com
DNS zone
cryptospinly.io

Location

IP address
104.21.21.63
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
cryptospinly.io

DNS records

A
  • 172.67.196.203
  • 104.21.21.63
NS
  • sloan.ns.cloudflare.com
  • mack.ns.cloudflare.com
SOA
Primary nameserver
mack.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418932143
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
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

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
104.21.21.63
IP version
4

Registration record

Registrar
NICENIC INTERNATIONAL GROUP CO., LIMITED
Registered
Updated
Expires
Status
  • clientDeleteProhibited https://icann.org/epp
  • clientTransferProhibited https://icann.org/epp
  • addPeriod https://icann.org/epp
Nameservers
  • mack.ns.cloudflare.com
  • sloan.ns.cloudflare.com
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "cryptospinly.io"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
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,
        8080
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.194.52",
            "host": "sloan.ns.cloudflare.com"
        },
        {
            "ip": "172.64.35.37",
            "host": "mack.ns.cloudflare.com"
        }
    ],
    "zone": "cryptospinly.io"
}
Location
{
    "ip": "104.21.21.63",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "cryptospinly.io"
}
DNS records
{
    "A": [
        "172.67.196.203",
        "104.21.21.63"
    ],
    "NS": [
        "sloan.ns.cloudflare.com",
        "mack.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"mack.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418932143, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "104.21.21.63",
    "family": 4
}
Registration record
{
    "registrar": "NICENIC INTERNATIONAL GROUP CO., LIMITED",
    "created": "2026-10-27T09:15:37Z",
    "updated": "2026-10-27T09:15:37Z",
    "expires": "2027-10-27T09:15:37Z",
    "status": [
        "clientDeleteProhibited https://icann.org/epp",
        "clientTransferProhibited https://icann.org/epp",
        "addPeriod https://icann.org/epp"
    ],
    "nameservers": [
        "mack.ns.cloudflare.com",
        "sloan.ns.cloudflare.com"
    ]
}
Network Security Intelligence Registrar context
Registrar context NiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
NiceNIC Verdict Full Investigation

Questions about cryptospinly.io

Is cryptospinly.io legit?

PhishDestroy records that the captured cryptospinly.io page returned blank content with no visible elements to inspect.

Is cryptospinly.io safe to connect a wallet?

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

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 · 2 captures

Cloudflare Radar 1 / 2 Used in the analysis Source file SHA-256: e474a175f992442a69e502e42d7748076f7b37bd4715cf7c03ed2b7ff55231c3 SHA-256 of the prepared copy given to the model: cbd7964afd4f4fe91d257f62cb637efc6d375d5ecf52307768f6bc30d044a66e
SourceCloudflare Radar
Recorded
StateStored capture
Final URLhttps://cryptospinly.io/
Position1 / 2
Open capture Source Report Wayback Download
All capture links and hashes (2)

Domain details

Domain
IP Context Canada172.67.196.203 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-11all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar NiceNIC RU(RU) PhishDestroy Investigation
Abuse contact["abuse@nicenic.net", "6eb609d996e182a6s@"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for cryptospinly.io →
RegistrationCreated Oct 27, 2026 (4d · Brand New!) — Expires Oct 27, 2027
Registrant countryHong Kong SAR China VirusTotal WHOIS
Registrant3495bcf1839c63746eb609d996e182a6s@ VirusTotal WHOIS
WHOIS statusclientDeleteProhibitedclientTransferProhibitedaddPeriod
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 1, 2026
Submitted URLhttp://cryptospinly.io/
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 85 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.67.196.203
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • mack.ns.cloudflare.com
  • sloan.ns.cloudflare.com

SOA

  • nsname: mack.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2418932143
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-27 08:26:39
Valid until
2027-01-25 08:26:38
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint94019bb427a263976fd74983c7a384f08410ff9cf4f5d2eef6e7eb529c58ba23
Certificate names · 2 SANs
  • *.cryptospinly.io
  • cryptospinly.io

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.67.196.203rapiddns.io
Casino / Gambling License Verification
Unverified gambling license
This domain markets casino/gambling services. Scam casinos routinely display fake Curaçao, MGA, or Kahnawake license badges that don’t exist in the real registries. Always verify the license number against the official regulator database before depositing. If the site shows a seal but no clickable registry link — or the linked registry page doesn’t exist — treat it as fraudulent.
Curaçao eGaming (official) Malta Gaming Authority UK Gambling Commission PA Gaming Control Kahnawake Gaming Gibraltar Gambling
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

1 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 1 detection
Fortinet
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
Requested URL: http://cryptospinly.io/
Final URL: https://cryptospinly.io/
HTML body
5.3 KB
Compressed
2.7 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Server: cloudflare
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
CF-Cache-Status: DYNAMIC
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 13
Cache-Control
no-store, no-cache, must-revalidate, max-age=0
CasT-Mode
default
cf-cache-status
DYNAMIC
CF-RAY
a538e4055d86f344-IAD
Connection
keep-alive
Content-Type
text/html; charset=utf-8
Date
Sun, 01 Nov 2026 06:37:24 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Pragma
no-cache
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=jtZo2PPl4z10IuY78HbfdKpTAmY3ibfAUvn6e1bCx%2F6ShH%2BnPXKZvPkLOzWhOjPnDcz%2Be8guT8Objnpv0WYqYEA9foX%2FWrdDMNBDB5P86tt%2Fu5JoGCyV9B0VsAzVdjKleU4%3
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked

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

Archived

Captured network requests

Network requests: 4 SHA-256 hashes: 3 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-01 06:41 UTC.

Open this scan on URLScan 01a18c83-1d0f-70a1-a696-0d997077a0ea ↗

All retained availability observations1

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_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    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-11-01 08:01:04.835385
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 9. 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
    cryptospinly.io detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Registrar Context: NiceNIC · Forensic Evidence Collected Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 8
  • 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: 1/92
  • OTX Community References
    Community publication references on AlienVault OTX: 2. References are not vendor verdicts and are excluded from the evidence score.
  • Registrar Context: NiceNIC
    Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

4 entries
  1. AlienVault OTX

    2 community references

    View source
  2. Added to PhishDestroy

    cryptospinly.io

    View source
  3. VirusTotal

    1/92 engine detections

    View source
  4. URLScan

    Malicious · engine verdict · score 8

    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

Check for cloaking

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

cryptospinly.io

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 1 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report OTX 2 refs 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 Unverified
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 cryptospinly.io)
  • 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.

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.

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/cryptospinly.io"
  title="PhishDestroy threat report for cryptospinly.io"
  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>