Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 2/92 engines flagged. malicious: 1. suspicious: 1. Analysis time (as stored): 2026-11-04T20:16:23Z. Retrieved (as stored): 2026-11-04T23:12:32Z. Listed by external blocklists: MetaMask, SEAL. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
crypto-page.com favicon

crypto-page.com

In short

PhishDestroy first recorded crypto-page.com on 2026-11-04. Stored VirusTotal result: 2/92 engines flagged. malicious: 1. suspicious: 1. Analysis time (as stored): 2026-11-04T20:16:23Z. Retrieved (as stored): 2026-11-04T23:12:32Z. Listed by external blocklists: MetaMask, SEAL.

Review the evidence
Registrar
Hong Kong SAR ChinaDominet (HK)
Resolved IP
Canada104.21.2.98Cloudflare, Inc. · CDN
Registered
Sep 12, 2026
First observed
Nov 4, 2026
PhishDestroy assessment High
66/100
Evidence score
Availability Reachable · access restricted Reachable response; page content was not verified Observed HTTP probe
Risk signals
VirusTotal detections: 2/92 Stored blocklist matches: 2 Last known active
VirusTotal
2 / 92
engine detections ·
Blocklist matches
2
MetaMask, SEAL
OTX
4
community references
URLScan
Malicious
engine verdict · score 71
Page captures
2
open gallery
Domain age
53 days
registered 2026-09-12 according to WHOIS · source data differ
OTX: 4 refs Nov 4, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded crypto-page.com on 2026-11-04. Stored VirusTotal result: 2/92 engines flagged. malicious: 1. suspicious: 1. Analysis time (as stored): 2026-11-04T20:16:23Z. Retrieved (as stored): 2026-11-04T23:12:32Z. Listed by external blocklists: MetaMask, SEAL. Risk: high (66/100). Registrar: Dominet (HK). Status: Reachable · access restricted. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.

High
Status
Reachable · access restricted
VirusTotal
2 / 92
Blocklist matches
2
Hosting
Canada104.21.2.98Cloudflare, Inc. · CDN
Registrar
Hong Kong SAR ChinaDominet (HK)
Registered
Sep 12, 2026
OTX
4 community refs
Page captures
2
Page captures Source results Registration record

Recorded source summary

PhishDestroy stores a record for crypto-page.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 2 / 92 · OTX 4 references 7 sources

VirusTotal

2 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
1
Suspicious
1
Undetected
37

Vendor labels

SOCRadar
phishing
Gridinsoft
suspicious

Reputation score

0

Categories

Dr.Web
not recommended site
Google
technology

Registrar

Dominet (HK) Limited

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    104.21.2.98
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3035::6815:262
  • TTL, seconds
    21600
    Type
    NS
    Value
    huxley.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3031::ac43:810f
  • TTL, seconds
    21600
    Type
    NS
    Value
    fatima.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.129.15
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    fatima.ns.cloudflare.com

DNS records observed

JARM fingerprint

27d40d40d00040d1dc27d40d27d40d5fb4c89fe3813d172ffb53f84a68f750

Certificate

Subject alternative names
  • *.crypto-page.com
  • crypto-page.com
Issuer
Let's Encrypt / YE1
Serial
6e5756627f012732716745ad51316698fc
SHA-256
b36aa0958cc1b4de65b316dcee338879ffb1ce29c7785a36ca4eeddc4a6cee6c
Subject
crypto-page.com
Valid until
Valid from

Registration record

Registrar
Dominet (HK) Limited
Registrar IANA ID
3775
Registrar URL
http://www.alibabacloud.com
Registered
Updated
Expires
Status
  • ok
Nameservers
  • cleo.ns.cloudflare.com
  • nelly.ns.cloudflare.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • active
Registry events
Expiration
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 1,
    "suspicious": 1,
    "undetected": 37
}
Vendor labels
{
    "SOCRadar": "phishing",
    "Gridinsoft": "suspicious"
}
Reputation
0
Categories
{
    "Dr.Web": "not recommended site",
    "Google": "technology"
}
Registrar
Dominet (HK) Limited
Created
2026-09-12T15:05:06Z
Expires
2027-09-12T15:05:06Z
Updated
2026-09-12T15:05:06Z
First seen
2026-06-20T01:40:58Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.2.98"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3035::6815:262"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "huxley.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3031::ac43:810f"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "fatima.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.129.15"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "fatima.ns.cloudflare.com"
    }
]
Dns at
2026-11-04T20:16:33Z
Jarm
27d40d40d00040d1dc27d40d27d40d5fb4c89fe3813d172ffb53f84a68f750
Certificate
{
    "san": [
        "*.crypto-page.com",
        "crypto-page.com"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "6e5756627f012732716745ad51316698fc",
    "sha256": "b36aa0958cc1b4de65b316dcee338879ffb1ce29c7785a36ca4eeddc4a6cee6c",
    "subject": "crypto-page.com",
    "valid_to": "2027-01-26T12:33:57Z",
    "valid_from": "2026-10-28T12:33:58Z"
}
Registration record
{
    "registrar": "Dominet (HK) Limited",
    "registrar_iana_id": "3775",
    "registrar_url": "http://www.alibabacloud.com",
    "created": "2026-09-12T15:05:06Z",
    "updated": "2026-09-12T15:05:06Z",
    "expires": "2027-09-12T15:05:06Z",
    "status": [
        "ok"
    ],
    "nameservers": [
        "cleo.ns.cloudflare.com",
        "nelly.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "active"
    ],
    "events": {
        "expiration": "2027-09-12T15:05:06Z",
        "registration": "2026-09-12T15:05:06Z",
        "registrar expiration": "2027-09-12T15:05:06Z",
        "last update of RDAP database": "2026-09-12T15:05:07Z"
    }
}
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
2
denominator
92
malicious
null
suspicious
null
vendors
["Gridinsoft","SOCRadar"]
observed_at
2026-11-04 20:16:23
checked_at
2026-11-05 00:12:32
fetched_at
2026-11-04 23:12:33
time_basis
as stored; legacy timezone not established

URLScan

Malicious · engine verdict · score 71

SHA-256 753329aef81fbbf8b9066f8e46c9375c0a7e8aa5882b9c9ff939ca17b70d9402

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a0b47a-e963-7707-9761-36ac1b7b2837

Final URL

https://crypto-page.com/

HTTP response

403

Redirects

  • To
    https://crypto-page.com/
    From
    https://crypto-page.com/
    Status
    307

IP address

188.114.97.3

Contacted domains

  • challenges.cloudflare.com

Contacted IP addresses

  • 104.18.94.41
  • 188.114.97.3

Autonomous systems (ASN)

  • 13335

Linked domains

  • www.cloudflare.com

Document hash

753329aef81fbbf8b9066f8e46c9375c0a7e8aa5882b9c9ff939ca17b70d9402

Script hashes

  • 5c7655205503d4b10d2d972b2b52ab7c257e370b618aa95b3593e3c9285870ae
  • 98c8670e62ebbc27f51a571cde667e26502f64397b630097f2f473be0b264758

JavaScript globals

  • _cf_chl_opt
  • qxIW9
  • NIsa2
  • nWvl2
  • khCN8
  • xJewX4
  • yLUi5
  • BCkZA9
  • BQIZT4
  • FZAoA8
  • eehKK5
  • XuSuX4
  • HZGAc5
  • ohAU5
  • xVQL7
  • UrPw0
  • mABIy1
  • ERdgw3
  • GfYw9
  • lNFng6
  • xJzHv6
  • MxFzg4
  • dwHkH1
  • runProgram
  • gIBpo1
  • LgNW7
  • QBLZ6
  • jTwa7
  • cyUJp9
  • cPYs6
  • angular
  • maNnU6
  • RJpH8
  • cmjTH9
  • turnstile
  • zOTXS6

Cookies

  • cf_clearance
  • cf_chl_rc_ni

TLS session and certificate

Subject alternative names
  • crypto-page.com
  • *.crypto-page.com
Cipher
AES_128_GCM
Issuer
WE1
Subject
crypto-page.com
Protocol
QUIC
Valid until
Valid from

Domain age, days

1311

Differs from the registration date in WHOIS (2026-09-12), which gives 5 days on the scan date 2026-09-18. The two sources disagree; both values are kept as recorded.

Registered domain age, days

1311

Differs from the registration date in WHOIS (2026-09-12), which gives 5 days on the scan date 2026-09-18. The two sources disagree; both values are kept as recorded.

Certificate age, days

5

Certificate validity, days

90

Page requests

16

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html; charset=UTF-8
Content-security-policy
default-src 'none'; script-src 'nonce-96hBUVeFM1oIEzfEswT2eI' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.clou
X-frame-options
SAMEORIGIN
X-content-type-options
nosniff
Referrer-policy
same-origin
Permissions-policy
accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),s
Cross-origin-opener-policy
same-origin
Cross-origin-resource-policy
same-origin
Cross-origin-embedder-policy
require-corp
Priority
u=0,i
Original source fields · JSON
Uuid
01a0b47a-e963-7707-9761-36ac1b7b2837
Final url
https://crypto-page.com/
Status
403
Redirects
[
    {
        "to": "https://crypto-page.com/",
        "from": "https://crypto-page.com/",
        "status": 307
    }
]
Ip
188.114.97.3
Contacted domains
[
    "challenges.cloudflare.com"
]
Contacted IP addresses
[
    "104.18.94.41",
    "188.114.97.3"
]
Asns
[
    "13335"
]
Linked domains
[
    "www.cloudflare.com"
]
Document hash
753329aef81fbbf8b9066f8e46c9375c0a7e8aa5882b9c9ff939ca17b70d9402
Script hashes
[
    "5c7655205503d4b10d2d972b2b52ab7c257e370b618aa95b3593e3c9285870ae",
    "98c8670e62ebbc27f51a571cde667e26502f64397b630097f2f473be0b264758"
]
Globals
[
    "_cf_chl_opt",
    "qxIW9",
    "NIsa2",
    "nWvl2",
    "khCN8",
    "xJewX4",
    "yLUi5",
    "BCkZA9",
    "BQIZT4",
    "FZAoA8",
    "eehKK5",
    "XuSuX4",
    "HZGAc5",
    "ohAU5",
    "xVQL7",
    "UrPw0",
    "mABIy1",
    "ERdgw3",
    "GfYw9",
    "lNFng6",
    "xJzHv6",
    "MxFzg4",
    "dwHkH1",
    "runProgram",
    "gIBpo1",
    "LgNW7",
    "QBLZ6",
    "jTwa7",
    "cyUJp9",
    "cPYs6",
    "angular",
    "maNnU6",
    "RJpH8",
    "cmjTH9",
    "turnstile",
    "zOTXS6"
]
Cookies
[
    "cf_clearance",
    "cf_chl_rc_ni"
]
Tls
{
    "san": [
        "crypto-page.com",
        "*.crypto-page.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "crypto-page.com",
    "protocol": "QUIC",
    "valid_to": "2026-12-11T15:06:08Z",
    "valid_from": "2026-09-12T14:08:38Z"
}
Domain age days
1311

Differs from the registration date in WHOIS (2026-09-12), which gives 5 days on the scan date 2026-09-18. The two sources disagree; both values are kept as recorded.

Apex age days
1311

Differs from the registration date in WHOIS (2026-09-12), which gives 5 days on the scan date 2026-09-18. The two sources disagree; both values are kept as recorded.

Tls age days
5
Tls valid days
90
Requests
16
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 71,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8",
    "content-security-policy": "default-src 'none'; script-src 'nonce-96hBUVeFM1oIEzfEswT2eI' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.clou",
    "x-frame-options": "SAMEORIGIN",
    "x-content-type-options": "nosniff",
    "referrer-policy": "same-origin",
    "permissions-policy": "accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),s",
    "cross-origin-opener-policy": "same-origin",
    "cross-origin-resource-policy": "same-origin",
    "cross-origin-embedder-policy": "require-corp",
    "priority": "u=0,i"
}
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
01a0b47a-e963-7707-9761-36ac1b7b2837
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

4 community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

30fd65bc-92f0-49ac-8154-2d1f7f7d545a

Final URL

https://crypto-page.com/

HTTP response

403

Navigation history

  • URL
    https://crypto-page.com/
    Status
    403

DOM structure hash

aeabdd5e39fcc8f49c076cbdaa926cffbea283eb2930e5da3e6b4439e131ac5b

Document hash

4f75dcec887c5688e91e5acb98cef1820a8d9c59fc15634921be4ff186a374a5

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    crypto-page.com
    Type
    A
    Value
    104.21.2.98
  • Name
    crypto-page.com
    Type
    A
    Value
    172.67.129.15
  • Name
    crypto-page.com
    Type
    AAAA
    Value
    2606:4700:3031::ac43:810f
  • Name
    crypto-page.com
    Type
    AAAA
    Value
    2606:4700:3035::6815:262

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.

Registration record

Registrar
Dominet (HK) Limited
Registered
Updated
Expires
Nameservers
  • fatima.ns.cloudflare.com
  • huxley.ns.cloudflare.com
Original source fields · JSON
Uuid
30fd65bc-92f0-49ac-8154-2d1f7f7d545a
Final url
https://crypto-page.com/
Status
403
History
[
    {
        "url": "https://crypto-page.com/",
        "status": 403
    }
]
DOM structure hash
aeabdd5e39fcc8f49c076cbdaa926cffbea283eb2930e5da3e6b4439e131ac5b
Document hash
4f75dcec887c5688e91e5acb98cef1820a8d9c59fc15634921be4ff186a374a5
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "crypto-page.com",
        "type": "A",
        "value": "104.21.2.98"
    },
    {
        "name": "crypto-page.com",
        "type": "A",
        "value": "172.67.129.15"
    },
    {
        "name": "crypto-page.com",
        "type": "AAAA",
        "value": "2606:4700:3031::ac43:810f"
    },
    {
        "name": "crypto-page.com",
        "type": "AAAA",
        "value": "2606:4700:3035::6815:262"
    }
]
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.

Registration record
{
    "registrar": "Dominet (HK) Limited",
    "created": "2026-09-12T15:05:06Z",
    "updated": "2026-10-28T13:27:52Z",
    "expires": "2027-09-12T15:05:06Z",
    "nameservers": [
        "fatima.ns.cloudflare.com",
        "huxley.ns.cloudflare.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

15 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 15 / 100 · 2026-11-04T23:20:34Z

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

record_source
domain_monitor.dom_analysis
heuristic_score
15
analyzed_at
2026-11-04T23:20:34Z
source_timestamp
2026-11-05 00:20:34
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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

Collected source details

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

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

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
3569

TLS connection

ALPN
h2
Cipher
ECDHE-ECDSA-AES128-GCM-SHA256
Protocol
TLSv1.2
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

DNS servers

Nameservers
  • IP address
    172.64.35.188
    Host
    huxley.ns.cloudflare.com
  • IP address
    172.64.34.188
    Host
    fatima.ns.cloudflare.com
DNS zone
crypto-page.com

Location

IP address
2606:4700:3035::6815:262
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
crypto-page.com

DNS records

A
  • 172.67.129.15
  • 104.21.2.98
NS
  • huxley.ns.cloudflare.com
  • fatima.ns.cloudflare.com
SOA
Primary nameserver
fatima.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418693371
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2606:4700:3031::ac43:810f
  • 2606:4700:3035::6815:262

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2606:4700:3035::6815:262
IP version
6

Technology stack

Technologies
  • AngularJS
  • Cloudflare Turnstile
  • Cloudflare
  • HTTP/3

Registration record

Registrar
Dominet (HK) Limited
Registered
Updated
Expires
Status
  • ok https://icann.org/epp
Nameservers
  • fatima.ns.cloudflare.com
  • huxley.ns.cloudflare.com

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=UTF-8
Content-security-policy
default-src 'none'; script-src 'nonce-mUw7nNjWm2R0tdRjlLysVl' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenge
X-frame-options
SAMEORIGIN
X-content-type-options
nosniff
Referrer-policy
same-origin
Permissions-policy
accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*
Cross-origin-opener-policy
same-origin
Cross-origin-resource-policy
same-origin
Cross-origin-embedder-policy
require-corp
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2021-11-30T21:47:55Z",
    "first": "2021-11-30T21:47:55Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 3569
}
TLS connection
{
    "alpn": "h2",
    "cipher": "ECDHE-ECDSA-AES128-GCM-SHA256",
    "protocol": "TLSv1.2",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.35.188",
            "host": "huxley.ns.cloudflare.com"
        },
        {
            "ip": "172.64.34.188",
            "host": "fatima.ns.cloudflare.com"
        }
    ],
    "zone": "crypto-page.com"
}
Location
{
    "ip": "2606:4700:3035::6815:262",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "crypto-page.com"
}
DNS records
{
    "A": [
        "172.67.129.15",
        "104.21.2.98"
    ],
    "NS": [
        "huxley.ns.cloudflare.com",
        "fatima.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"fatima.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418693371, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2606:4700:3031::ac43:810f",
        "2606:4700:3035::6815:262"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2606:4700:3035::6815:262",
    "family": 6
}
Tech stack
{
    "technologies": [
        "AngularJS",
        "Cloudflare Turnstile",
        "Cloudflare",
        "HTTP/3"
    ]
}
Registration record
{
    "registrar": "Dominet (HK) Limited",
    "created": "2026-09-12T15:05:06Z",
    "updated": "2026-10-28T13:27:52Z",
    "expires": "2027-09-12T15:05:06Z",
    "status": [
        "ok https://icann.org/epp"
    ],
    "nameservers": [
        "fatima.ns.cloudflare.com",
        "huxley.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=UTF-8",
        "content-security-policy": "default-src 'none'; script-src 'nonce-mUw7nNjWm2R0tdRjlLysVl' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenge",
        "x-frame-options": "SAMEORIGIN",
        "x-content-type-options": "nosniff",
        "referrer-policy": "same-origin",
        "permissions-policy": "accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*",
        "cross-origin-opener-policy": "same-origin",
        "cross-origin-resource-policy": "same-origin",
        "cross-origin-embedder-policy": "require-corp"
    }
}

Questions about crypto-page.com

Is crypto-page.com legit?

PhishDestroy rates crypto-page.com as high risk (66/100) from the recorded evidence; it was first recorded on 2026-11-04. Stored VirusTotal result: 2/92 engines flagged. malicious: 1. suspicious: 1. Analysis time (as stored): 2026-11-04T20:16:23Z. Retrieved (as stored): 2026-11-04T23:12:32Z. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is crypto-page.com safe to connect a wallet?

This report does not record which wallet requests crypto-page.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 crypto-page.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 matchesMetaMask · PhishDestroy · SEAL · no match in the other 9 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Checked, no match

Last checked

Stored Capture · 2 captures

URLScan · 2026-09-18 1 / 2
SourceURLScan · 2026-09-18
Recorded
StateStored capture
HTTP status403
Final URLhttps://crypto-page.com/
Position1 / 2
Open capture Source Report Wayback Download
All capture links and hashes (2)

Domain details

Domain
IP Context Canada104.21.2.98 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-11activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Dominet (HK) HK(HK)
Abuse contact["domainabuse@service.aliyun.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for crypto-page.com →
RegistrationCreated Sep 12, 2026 (53d · New) — Expires Sep 12, 2027
WHOIS statusok
HTTP Status403 Forbidden
Technical detailsProvenance & timestamps
First DetectedNov 4, 2026
DOM Analysisanalyzed Nov 5, 2026score 15/100
Submitted URLhttps://crypto-page.com/
Favicon Hash
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 82 days

Network & certificates

Stored technical evidence

Network & DNS

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

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • cleo.ns.cloudflare.com
  • nelly.ns.cloudflare.com

SOA

  • nsname: fatima.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2418693371
  • 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-28 12:33:58
Valid until
2027-01-26 12:33:57
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintb36aa0958cc1b4de65b316dcee338879ffb1ce29c7785a36ca4eeddc4a6cee6c
Certificate names · 2 SANs
  • *.crypto-page.com
  • crypto-page.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 · 104.21.2.98rapiddns.io
Recorded subdomains1

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

  • www.crypto-page.comDomain record
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

2 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 2 detections
SOCRadar
Gridinsoft
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of crypto-page.com · checked Nov 4, 2026

91
Good
Performance
FCP
0.77 s
First Contentful Paint
LCP
0.77 s
Largest Contentful Paint
CLS
0.004
Cumulative Layout Shift
TBT
369 ms
Total Blocking Time
SI
1.49 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 403
Requested URL: https://crypto-page.com/
Just a moment...
Response
HTTP 403
HTML body
5.5 KB
Compressed
3.3 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
CF-Mitigated: challenge
Server: cloudflare
Content-Encoding: gzip
Security headers present
Content-Security-PolicyX-Frame-OptionsX-Content-Type-OptionsReferrer-PolicyPermissions-PolicyCross-Origin-Opener-PolicyCross-Origin-Resource-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 23
Accept-Ch
Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model,
alt-svc
h3=":443"; ma=86400
Cf-Mitigated
challenge
CF-RAY
a556ec9a8fcb6108-IAD
Connection
close
Content-Encoding
gzip
Content-Security-Policy
default-src 'none'; script-src 'nonce-ujYxw97BV1JkIisbmfW5Tq' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blo
Content-Type
text/html; charset=UTF-8
Critical-Ch
Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model,
Cross-Origin-Embedder-Policy
require-corp
Cross-Origin-Opener-Policy
same-origin
Cross-Origin-Resource-Policy
same-origin
Date
Wed, 04 Nov 2026 22:06:09 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Origin-Agent-Cluster
?1
Permissions-Policy
accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*
Referrer-Policy
same-origin
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=%2Fb5MBzFClxmcIeHqihIhC%2FrnXNSYkJP%2F7pr810bmO9E4%2BNUs4zucBNd1BWJwfaitDNgkey4hPLt%2BNnqe%2FWUhp5f5ZJDgbkUK7SaYa7q3jeHfrvKmOKxeNGwpaSI6TyG9nzA
Server
cloudflare
Server-Timing
chlray;desc="a556ec9a8fcb6108"
Transfer-Encoding
chunked
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN

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

Archived
Registration & observation details1

Availability observations

Last reachable observation

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: 16 SHA-256 hashes: 12 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-04 22:08 UTC.

Open this scan on URLScan 01a0b47a-e963-7707-9761-36ac1b7b2837 ↗

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. VirusTotal · Detection count

    1→2

    Engines added
    SOCRadar
    Engines removed
    None recorded
    Recorded vendor total
    2
  2. Domain monitor · First collection record

    Reachable

All retained availability observations2

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. http_observationunknown
    Observation source
    http_observation
    Cause
    legacy_alive_unverified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    15
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 23:06:28.000000
    Evidence SHA-256
    0ea7ae54511be199c57f3aaea7d1adbccb43024ed01da46ba05dbfe202209654
    Evidence timestamp as recorded
    2026-11-04 23:06:28
  2. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    403
    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-04 23:06:28.000000
    Evidence SHA-256
    b44cdfedd45034a13e778b1cfc48b54057eabf2acb61b67f0b9212d0e4250045
    Evidence timestamp as recorded
    2026-11-04 23:06:28
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    false

Threat Response Pipeline

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

Recorded events: 11. 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
    crypto-page.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Blocklist Detection · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded · VirusTotal detections +1 Recorded: 9 of 9
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 71
  • 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: 2/92
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • OTX Community References
    Community publication references on AlienVault OTX: 4. References are not vendor verdicts and are excluded from the evidence score.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
  • VirusTotal detections +1
    New detections: +1 (1 → 2): SOCRadar
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Added to PhishDestroy

    crypto-page.com

    View source
  3. VirusTotal

    2/92 engine detections

    View source
  4. URLScan

    Malicious · engine verdict · score 71

    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

Check for cloaking

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

crypto-page.com

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 2 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report OTX 4 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 Reachable · access restricted
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 crypto-page.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/crypto-page.com"
  title="PhishDestroy threat report for crypto-page.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>