Skip to security report
Domain security and threat intelligence
btcprotocolz960.com favicon

btcprotocolz960.com

In short

btcprotocolz960.com is a Celer impersonation page detected by PhishDestroy on 2026-10-23. Risk: critical (100/100). Registrar: Dynadot. Status: Last known active. Hosting: Omegatech LTD. VirusTotal: 16/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

“BTC-Protocol-Z 960 — Algorithmic Trading Platform for Enterprise Investors”

Registrar
Dynadot
Resolved IP
158.94.210.119
Registered
May 20, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 16/92 Spamhaus DBL: DBL_SPAM Automated brand label: Celer
OTX: 4 refs Oct 23, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 16. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Source evidenceVirusTotal 16 / 92 · OTX 4 references 7 sources

VirusTotal

16 / 92 engine detections

Open report

Spamhaus DBL

DBL_SPAM

OTX

4 community references

Open report

Google Safe Browsing

No threat flag

Open report

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

Analysis

Critical
VirusTotal
16 / 92
OTX
4 community refs
Page captures
7

PhishDestroy threat report

Overview

PhishDestroy added btcprotocolz960.com to its internal blocklist on 2026-10-23, citing a trusted report based on the domain’s age of 156 days. The recorded page title advertises an "Algorithmic Trading Platform for Enterprise Investors," but no malicious behavior was directly observed. An HTTP 200 response was recorded on the same date, confirming the site was reachable at that time.

How the scam works

While no specific malicious mechanism was observed on this page, domains with similar fake‑trading claims often aim to lure visitors into providing personal or financial information, or to convince them to deposit cryptocurrency under false pretenses. The risk category therefore aligns with typical fraudulent investment or phishing schemes that exploit trust in professional‑sounding branding.

Evidence

VirusTotal scanned the domain on 2026-10-14 and reported 16 detections across 92 engines, including 13 malicious and 3 suspicious labels from vendors such as BitDefender, ESET, and Forcepoint ThreatSeeker. Google Safe Browsing checked on 2026-10-23 did not flag the site. OTX listed four pulses as of 2026-10-23. Cloudflare Radar flagged the URL as phishing and malware on 2026-10-23. urlscan.io recorded a malicious engine score of 99 on 2026-10-23, though its overall verdict was non‑malicious. No external blocklists reported the domain, but PhishDestroy’s internal list marks it as suspicious.

Infrastructure

The domain was registered with Dynadot Inc on 2026-05-20 and resolves to IP 158.94.210.119, hosted by Omegatech LTD in the Netherlands. TLS was provided by Let’s Encrypt, valid from 2026-09-01 to 2026-11-30. DNS records include an A record to the same IP and NS records at ns1.dyna-ns.net and ns2.dyna-ns.net, without DNSSEC signatures. Open ports observed were 22, 80, and 443.

What to do

Visitors should avoid entering credentials, personal data, or cryptocurrency on this site; if any information was submitted, change related passwords and monitor accounts for unauthorized activity. Security teams should block btcprotocolz960.com at the network perimeter, review logs for any connections to 158.94.210.119, and apply standard phishing response procedures for any compromised accounts.

Collected source details

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

URLScan · 2026-10-23T17:17:04Z

Observed: · Retrieved:

Uuid
01a169c3-fda5-76a9-b2c2-089a4771cf06
Final url
https://btcprotocolz960.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://btcprotocolz960.com/",
        "from": "http://btcprotocolz960.com/",
        "status": 307
    }
]
Ip
158.94.210.119
Contacted IP addresses
[
    "158.94.210.119"
]
Asns
[
    "202412"
]
Countries
[
    "NL"
]
Document hash
0ca36a59d83d99ceec449e009cae4b51beca87c4dbc9a2ed95a334be9410053b
Script hashes
[
    "8aa5f8f647356dcd4fc5dbbe0efd5bc0e8da74026bc61e24636e2e1f5749b0ce"
]
Globals
[
    "__dclq",
    "__dclOrig",
    "__dclFlush",
    "__smsCheckBeforeSubmit",
    "__isSmsEnabled",
    "__isSmsVerified",
    "intlTelInput",
    "toggle",
    "navWrapper"
]
Cookies
[
    "connect.sid"
]
Tls
{
    "san": [
        "btcprotocolz960.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "btcprotocolz960.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-30T02:50:10Z",
    "valid_from": "2026-09-01T02:50:11Z"
}
Domain age days
156
Apex age days
156
Tls age days
52
Tls valid days
89
Requests
5
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8",
    "x-content-type-options": "nosniff",
    "referrer-policy": "same-origin"
}
Cloudflare Radar · 2026-10-23T17:53:23Z

Observed: · Retrieved:

Uuid
7d462330-36e2-4e40-8fe8-f6a79fefda5f
Final url
https://btcprotocolz960.com/
Status
200
History
[
    {
        "url": "https://btcprotocolz960.com/",
        "status": 200
    }
]
DOM structure hash
a2f98133f42cce269e264076e4bdefd62057384c3fa40690ae908e2e79d0c52b
Document hash
a08bb85250c8f1c2a3514d269c281a1ce19619361ac3b4366c6ce8579e4a8401
Phishing v2
[
    "phishing"
]
Url risks
[
    "Scam"
]
Domain risks
[
    "Malware",
    "Security threats",
    "Scam",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "btcprotocolz960.com",
        "type": "A",
        "value": "158.94.210.119"
    }
]
Dnssec valid
false
Ip
158.94.210.119
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-05-20T16:45:27Z",
    "updated": "2026-08-13T11:29:59Z",
    "expires": "2027-05-20T16:45:27Z",
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ]
}
VirusTotal · 2026-10-14T17:24:11Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 13,
    "suspicious": 3,
    "undetected": 31
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Registrar
Dynadot Inc
Created
2026-05-20T16:45:27Z
Expires
2027-05-20T16:45:27Z
Updated
2026-08-13T11:29:59Z
First seen
2026-05-20T17:19:32Z
DNS records
[
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "hostmaster.btcprotocolz960.com",
        "value": "ns1.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "158.94.210.119"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.dyna-ns.net"
    }
]
Dns at
2026-10-14T17:29:28Z
Jarm
40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319
Certificate
{
    "san": [
        "btcprotocolz960.com"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "69cfa47b1d8334576331826200990f9ced3",
    "sha256": "c5a34ebc2f848dfcd911d057e8ee67eb74d0ac0e76b660e4f877b3982cba8e82",
    "subject": "btcprotocolz960.com",
    "valid_to": "2026-11-30T02:50:10Z",
    "valid_from": "2026-09-01T02:50:11Z"
}
Registration record
{
    "registrar": "Dynadot Inc",
    "registrar_iana_id": "472",
    "registrar_url": "http://www.dynadot.com",
    "created": "2026-05-20T16:45:27Z",
    "updated": "2026-08-13T11:29:59Z",
    "expires": "2027-05-20T16:45:27Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-05-20T16:45:27Z",
        "last changed": "2026-09-01T02:24:50Z",
        "registration": "2026-05-20T16:45:27Z",
        "registrar expiration": "2027-05-20T16:45:27Z",
        "last update of RDAP database": "2026-10-14T00:05:39Z"
    }
}
Website checks · 2026-10-23T17:55:33Z
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "btcprotocolz960.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-23T17:19:11Z",
    "first": "2026-10-12T06:45:32Z",
    "changes": 1,
    "days_archived": 2,
    "scans_per_day": 0.09,
    "avg_page_bytes": 24051
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://btcprotocolz960.com/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 5
}
Page title and metadata
{
    "title": "BTC-Protocol-Z 960 — Algorithmic Trading Platform for Enterprise Investors",
    "robots": "index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1",
    "description": "AI-Powered Trading Platform built on quantitative machine learning. BTC-Protocol-Z 960 gives enterprise investors the capability to execute high-frequency trades across 180+ territories.",
    "canonicalUrl": "https://btcprotocolz960.com/"
}
Trackers
{
    "requests": 28,
    "trackers": [
        {
            "name": "Cloudflare",
            "company": "Cloudflare",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "jsDelivr",
            "company": "jsDelivr",
            "category": "Hosting",
            "requests": 4
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 94,
        "tls": 84,
        "wait": 131,
        "connect": 72,
        "download": 147
    },
    "response_ms": 528
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Carbon
{
    "bytes": 98576,
    "co2_grams": 0.0036,
    "cleaner_than": 22
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.27.158",
            "host": "ns1.dyna-ns.net"
        },
        {
            "ip": "162.159.25.5",
            "host": "ns2.dyna-ns.net"
        }
    ],
    "zone": "btcprotocolz960.com"
}
Cookies
{
    "cookies": [
        {
            "name": "connect.sid",
            "secure": true,
            "http_only": true,
            "same_site": "Lax"
        }
    ]
}
Location
{
    "ip": "158.94.210.119",
    "asn": "202412",
    "org": "Omegatech LTD",
    "city": "Amsterdam",
    "country": "NL"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "btcprotocolz960.com"
}
DNS records
{
    "A": [
        "158.94.210.119"
    ],
    "NS": [
        "ns2.dyna-ns.net",
        "ns1.dyna-ns.net"
    ],
    "SOA": "{\"nsname\": \"ns1.dyna-ns.net\", \"hostmaster\": \"hostmaster.btcprotocolz960.com\", \"serial\": 2026083101, \"refresh\": 16384, \"retry\": 2048, \"expire\": 1209600, \"minttl\": 300}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": "same-origin",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "158.94.210.119",
    "family": 4
}
Redirects
{
    "chain": [
        "https://btcprotocolz960.com"
    ]
}
Page links
{
    "internal_count": 30
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-05-20T16:45:27Z",
    "updated": "2026-08-13T11:29:59Z",
    "expires": "2027-05-20T16:45:27Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ]
}
HTTP headers
{
    "headers": {
        "content-type": "text/html; charset=utf-8",
        "x-content-type-options": "nosniff",
        "referrer-policy": "same-origin"
    }
}

Questions about btcprotocolz960.com

Is btcprotocolz960.com legit?

No. PhishDestroy classifies btcprotocolz960.com as a Celer impersonation page (risk: critical, 100/100); it was first detected on 2026-10-23. VirusTotal: 16/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is btcprotocolz960.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on btcprotocolz960.com. 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 btcprotocolz960.com?

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

Domain details

Domain
IP Reputation abuse score 10/100 12 reports PhishingOpen ProxyBad Web Bot checked Oct 23, 2026
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
RegistrationCreated May 20, 2026 (156d) — Expires May 20, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 10/1003 brand signals
Submitted URLhttp://btcprotocolz960.com/
Favicon Hash
Case ID
Observed page title
BTC-Protocol-Z 960 — Algorithmic Trading Platform for Enterprise Investors
Automated brand references
Across Celer Compound
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 37 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
158.94.210.119
Network ASN
AS202412
Organization
Omegatech LTD
Observed location
Amsterdam, NL

Nameservers 2

  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-09-01 02:50:11
Valid until
2026-11-30 02:50:10
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintc5a34ebc2f848dfcd911d057e8ee67eb74d0ac0e76b660e4f877b3982cba8e82
Certificate names · 1 SAN
  • btcprotocolz960.com

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

Report This Domain Submit evidence & help protect others

VirusTotal Analysis

16 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
alphaMountain.ai
BitDefender
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Netcraft
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of btcprotocolz960.com · checked Oct 23, 2026

99
Good
Performance
FCP
0.99s
First Contentful Paint
LCP
0.99s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.54s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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.

Stored observation history1

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

  1. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    16/92 engine detections

    View source
  4. Added to PhishDestroy

    btcprotocolz960.com

    View source
  5. URLScan

    Page captured

    View source

Check for cloaking

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

btcprotocolz960.com

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 0 stored notification records Last known active

Listed domains receive at least one abuse report; this entry has no retained notification history.

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

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 →

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

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 btcprotocolz960.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

Stay Informed, Stay Safe

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

Live Threat Feed Appeal This Listing
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/btcprotocolz960.com"
  title="PhishDestroy threat report for btcprotocolz960.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>