Skip to security report
Analytics Dashboard
Domain security and threat intelligence
btc-belant17.pro favicon

btc-belant17.pro

In short

btc-belant17.pro is a phishing page detected by PhishDestroy on 2026-10-23. Risk: critical (100/100). Registrar: Spaceship. Status: Last known active. Hosting: CloudFLARENET-EU. VirusTotal: 18/92 engines flag it. Do not enter credentials or connect a wallet.

“btc-belant 17.2 | AI Trading Platform | Official Website”

Registrar
Spaceship
Resolved IP
188.114.96.3
Registered
Apr 23, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 18/92 Scam type: Fake Exchange
OTX: 5 refs Oct 23, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 18. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
18 / 92
engine detections
Google Safe Browsing
No threat flag
OTX
5
community references
Page captures
6
open gallery
Domain age
183 days
Source evidenceVirusTotal 18 / 92 · OTX 5 references 6 sources

VirusTotal

18 / 92 engine detections

Open report

OTX

5 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
18 / 92
OTX
5 community refs
Page captures
6
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy’s automated assessment labels btc-belant17.pro as a fake crypto exchange. The recorded page title reads “btc-belant 17.2 | AI Trading Platform | Official Website”. The domain was first seen by PhishDestroy on 2026-10-23 and returned an HTTP 200 response on that date. Intake accepted the report as a trusted entry because the domain was 183 days old at the time of detection.

How the scam works

Fake exchange sites typically promise high‑yield AI trading, lure users to deposit cryptocurrency, and then disappear with the funds or harvest wallet credentials. Victims may be asked to connect a wallet, approve transactions, or provide private keys, after which the operators can drain the assets.

Evidence

VirusTotal scanned the domain on 2026-10-22 and reported 18 detections out of 92 engines, with vendors such as BitDefender, ESET and Forcepoint ThreatSeeker flagging it as phishing or malicious. Google Safe Browsing checked on 2026-10-23 and did not flag the site. OTX listed five pulses referencing the domain as of 2026-10-23. URLScan captured the site on 2026-10-23; its engine score was 96 (malicious) but the overall verdict was non‑malicious, while Cloudflare Radar on the same day marked the domain malicious for malware and phishing.

Infrastructure

The domain was registered on 2026-04-23 through Spaceship, Inc., giving it an age of 183 days at first sighting. The recorded scan showed a Cloudflare Web Application Firewall header and that the domain resolved to IPv4 (188.114.96.3) and IPv6 (2a06:98c1:3121::3) addresses, and it used a TLS certificate issued by Google Trust Services on 2026-10-17, valid until 2027-01-15.

What to do

Do not enter credentials, private keys or approve wallet connections on this site; if you have already done so, revoke any approvals and move assets to a new, secure wallet. Organizations should block the exact domain btc-belant17.pro at the firewall and monitor outbound traffic for connections to the recorded Cloudflare IPs.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportURLQuery reportStored capture screenshotCloudflare Radar screenshot (2026-10-23T16:45:53Z)URLQuery screenshotURLScan screenshot (2026-10-23T14:51:24Z)URLScan capture reportURLScan screenshot (2026-10-23T15:09:04Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusRevoke token approvalsReport crypto fraud (Chainabuse)Report phishing to GoogleSite owner? Request a review

Collected source details

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

URLScan · 2026-10-23T16:12:02Z

Observed: · Retrieved:

Uuid
01a16988-4c8b-706c-94d0-99a3abf927ab
Final url
https://btc-belant17.pro/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://btc-belant17.pro/",
        "from": "http://btc-belant17.pro/",
        "status": 307
    }
]
Ip
104.21.78.202
Contacted domains
[
    "cdnjs.cloudflare.com",
    "challenges.cloudflare.com",
    "cdn.jsdelivr.net",
    "fonts.googleapis.com",
    "static.cloudflareinsights.com",
    "static.cloudflare.com"
]
Contacted IP addresses
[
    "104.18.94.41",
    "104.17.207.5",
    "142.251.179.95",
    "104.17.24.14",
    "104.21.78.202"
]
Asns
[
    "13335",
    "15169"
]
Countries
[
    "US"
]
Document hash
b258124290488462193d07cb32f3bac4b2030cf839683a4399b0f7f936bb84c6
Script hashes
[
    "ccf00d1923b0131a10e0c6d26f95e5dee6ebf8621a27e83c5a2f68a2e0093142"
]
Globals
[
    "LANG_MSGS",
    "ClientJS",
    "_cjc1k",
    "toggleTermsPopup",
    "__tsGet",
    "__tsNeedsClick",
    "__tsShow",
    "__tsReset",
    "__lgBS",
    "__cfQR",
    "turnstile",
    "__cfRLUnblockHandlers",
    "__lgT0"
]
Cookies
[
    "entry_url"
]
Tls
{
    "san": [
        "btc-belant17.pro"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "btc-belant17.pro",
    "protocol": "QUIC",
    "valid_to": "2027-01-15T10:47:07Z",
    "valid_from": "2026-10-17T09:47:09Z"
}
Domain age days
183
Apex age days
183
Tls age days
6
Tls valid days
90
Requests
21
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 96,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=63072000; includeSubDomains; preload",
    "content-security-policy": "default-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdnjs.cloudflare.com; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://static.cloudflare.com https://cd",
    "x-frame-options": "SAMEORIGIN",
    "x-content-type-options": "nosniff",
    "referrer-policy": "strict-origin-when-cross-origin",
    "permissions-policy": "camera=(), microphone=(), geolocation=()",
    "cross-origin-opener-policy": "same-origin"
}
Cloudflare Radar · 2026-10-23T16:45:53Z

Observed: · Retrieved:

Uuid
12c5a541-a3f5-4f37-83ac-f3942be00e08
Final url
https://btc-belant17.pro/
Status
200
History
[
    {
        "url": "https://btc-belant17.pro/",
        "status": 200
    }
]
DOM structure hash
69bcc7c4f1c9c3608f2ba0793cf413662b50f6566ce0e5f188dd29b3139d41e1
Document hash
7bb3a845dc8fd8fd120b621c3d2c5cc5f9e6b64e873b8c161ae8b52eea1093a4
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "btc-belant17.pro",
        "type": "A",
        "value": "188.114.96.0"
    },
    {
        "name": "btc-belant17.pro",
        "type": "A",
        "value": "188.114.97.0"
    },
    {
        "name": "btc-belant17.pro",
        "type": "AAAA",
        "value": "2a06:98c1:3120::"
    },
    {
        "name": "btc-belant17.pro",
        "type": "AAAA",
        "value": "2a06:98c1:3121::"
    }
]
Dnssec valid
false
Ip
188.114.96.0
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
VirusTotal · 2026-10-22T18:11:39Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 42,
    "malicious": 15,
    "suspicious": 3,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Created
2026-04-23T00:00:00Z
Updated
2026-04-23T00:00:00Z
First seen
2026-04-23T09:05:03Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.137.113"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.78.202"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3035::6815:4eca"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3030::ac43:8971"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "thomas.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "indie.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "indie.ns.cloudflare.com"
    }
]
Dns at
2026-10-22T18:17:03Z
Jarm
27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6
Certificate
{
    "san": [
        "btc-belant17.pro"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "5bf423746f32568713f6bb1433a18614",
    "sha256": "86b36cacce8805349a4ce46556dc91dd76262c01e23a3a477b628e4bb3f9e15a",
    "subject": "btc-belant17.pro",
    "valid_to": "2027-01-15T10:47:07Z",
    "valid_from": "2026-10-17T09:47:09Z"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "last changed": "2026-08-21T01:47:34Z",
        "registration": "2026-04-23T07:26:42Z",
        "registrar expiration": "2027-04-23T07:26:42Z",
        "last update of RDAP database": "2026-10-18T16:42:39Z"
    },
    "registrar": "Spaceship, Inc.",
    "registrar_iana_id": "3862"
}
Website checks · 2026-10-23T16:46:30Z
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "btc-belant17.pro"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-23T16:14:51Z",
    "first": "2026-10-16T03:17:54Z",
    "changes": 1,
    "days_archived": 2,
    "scans_per_day": 0.13,
    "avg_page_bytes": 42027
}
Crawler rules
{
    "agents": [
        "*",
        "Amazonbot",
        "Applebot-Extended",
        "Bytespider",
        "CCBot"
    ],
    "present": true,
    "sitemaps": [
        "https://btc-belant17.pro/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 140
}
Page title and metadata
{
    "title": "btc-belant 17.2 | AI Trading Platform | Official Website",
    "robots": "index, follow",
    "themeColor": "#0d0d12",
    "description": "btc-belant 17.2 showcases AI-driven automated trading capabilities, optimized execution flow, and risk controls for informed decision-making.",
    "canonicalUrl": "https://btc-belant17.pro/"
}
Trackers
{
    "requests": 21,
    "trackers": [
        {
            "name": "Cloudflare",
            "company": "Cloudflare",
            "country": "US",
            "category": "Hosting",
            "requests": 9
        },
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "jsDelivr",
            "company": "jsDelivr",
            "category": "Hosting",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://static.cloudflare.com/beacon.min.js",
        "https://challenges.cloudflare.com/turnstile/v0/api.js",
        "https://cdn.jsdelivr.net/npm/clientjs@0.2.1/dist/client.min.js"
    ],
    "third_party_scripts": 3
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 23,
        "wait": 144,
        "connect": 6,
        "download": 12
    },
    "response_ms": 187
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 145173,
    "co2_grams": 0.0053,
    "cleaner_than": 14
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.38.163",
            "host": "indie.ns.cloudflare.com"
        },
        {
            "ip": "172.64.33.238",
            "host": "thomas.ns.cloudflare.com"
        }
    ],
    "zone": "btc-belant17.pro"
}
Cookies
{
    "cookies": [
        {
            "name": "entry_url",
            "secure": true,
            "same_site": "Lax"
        }
    ]
}
Location
{
    "ip": "2a06:98c1:3121::3",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Google Trust Services / WE1",
    "subject": "btc-belant17.pro"
}
DNS records
{
    "A": [
        "188.114.96.3",
        "188.114.97.3"
    ],
    "NS": [
        "thomas.ns.cloudflare.com",
        "indie.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"indie.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418084957, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2a06:98c1:3121::3",
        "2a06:98c1:3120::3"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=63072000; includeSubDomains; preload",
    "message": "Site is compatible with the HSTS preload list!",
    "compatible": true
}
HTTP security policies
{
    "xFrameOptions": "SAMEORIGIN",
    "referrerPolicy": "strict-origin-when-cross-origin",
    "xXSSProtection": false,
    "permissionsPolicy": "camera=(), microphone=(), geolocation=()",
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": "default-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdnjs.cloudflare.com; script-s",
    "strictTransportPolicy": "max-age=63072000; includeSubDomains; preload",
    "crossOriginOpenerPolicy": "same-origin",
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2a06:98c1:3121::3",
    "family": 6
}
Redirects
{
    "chain": [
        "https://btc-belant17.pro"
    ]
}
Page links
{
    "internal_count": 43
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=63072000; includeSubDomains; preload",
        "content-security-policy": "default-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdnjs.cloudflare.com; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://static.cloudflare.com https://cdn.jsdelivr.net https://challenges.cloudflare.com; font-src 'self' https://fonts.gstatic.com https://",
        "x-frame-options": "SAMEORIGIN",
        "x-content-type-options": "nosniff",
        "referrer-policy": "strict-origin-when-cross-origin",
        "permissions-policy": "camera=(), microphone=(), geolocation=()",
        "cross-origin-opener-policy": "same-origin"
    }
}

Questions about btc-belant17.pro

Is btc-belant17.pro legit?

No. PhishDestroy classifies btc-belant17.pro as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-23. VirusTotal: 18/92 engines flag it. Treat the site as unsafe.

Is btc-belant17.pro safe to connect a wallet?

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

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

Primary capture 1 / 6
SourcePrimary capture
Recorded2026-10-23 16:13 UTC
StateStored capture
Position1 / 6
Open capture Wayback Download

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Spaceship US(US)
Abuse contactabuse@spaceship.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for btc-belant17.pro →
RegistrationCreated Apr 23, 2026 (183d) — Expires Apr 23, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 40/1001 brand signal
Submitted URLhttp://btc-belant17.pro/
Favicon Hash
Case ID
Observed page title
btc-belant 17.2 | AI Trading Platform | Official Website
Automated brand references
Across
TLS Certificate
Issued by WE1 · stored validity ends in 83 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
CloudFLARENET-EU
Observed location
London, GB
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • indie.ns.cloudflare.com
  • thomas.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
WE1
Valid from
2026-10-17 09:47:09
Valid until
2027-01-15 10:47:07
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint86b36cacce8805349a4ce46556dc91dd76262c01e23a3a477b628e4bb3f9e15a
Certificate names · 1 SAN
  • btc-belant17.pro

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

viewdns.info · 188.114.96.3rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

18 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 2 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of btc-belant17.pro · checked Oct 23, 2026

87
Needs Work
Performance
FCP
2.25s
First Contentful Paint
LCP
3s
Largest Contentful Paint
CLS
0.141
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.25s
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 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

    2→18

  2. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. AlienVault OTX

    5 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    18/92 engine detections

    View source
  4. Added to PhishDestroy

    btc-belant17.pro

    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.

btc-belant17.pro

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 18 det. ChainPatrol URLQuery Report stored SSL Labs Stored certificate dates valid CF Radar Open report OTX 5 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?

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.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 btc-belant17.pro)
  • 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

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.

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/btc-belant17.pro"
  title="PhishDestroy threat report for btc-belant17.pro"
  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>