Skip to security report
Recorded security signals
Stored VirusTotal result: 4/92 engines flagged. Analysis time (as stored): 2026-10-31 11:21 UTC. Retrieved (as stored): 2026-10-31 23:05 UTC. Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
sup-binance.sbs favicon

sup-binance.sbs

In short

The captured page on sup-binance.sbs presents itself as a Binance fund recovery portal, headed "Get a Refund of Your Lost Funds" and describing a SAFU Reserve Framework for restitution. The main interaction is a claim submission flow: visitors are prompted to enter their details, specify the lost amount, and pass AML verification, with buttons to apply for a refund or track an existing case ID.

“Binance Fund Recovery | Get a Refund of Your Lost Funds (SAFU)”

Registrar
NetherlandsHosting Concepts
Resolved IP
United Kingdom188.114.96.3CloudFLARENET-EU · CDN
First observed
Oct 31, 2026
PhishDestroy assessment Critical
90/100
Evidence score
First observed Oct 31, 2026 22:33 UTC · PhishDestroy
VirusTotal detections: 4/92 Stored blocklist matches: 2
VirusTotal
engine detections ·
Blocklist matches
MetaMask, SEAL
OTX
community references
URLScan
Cloudflare Radar
Page captures
open gallery
OTX: 4 refs Oct 31, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded sup-binance.sbs on 2026-10-31. Stored VirusTotal result: 4/92 engines flagged. Analysis time (as stored): 2026-10-31 11:21 UTC. Retrieved (as stored): 2026-10-31 23:05 UTC. Listed by external blocklists: MetaMask, SEAL. Risk: critical (90/100). Registrar: Hosting Concepts. Hosting: CloudFLARENET-EU. Do not enter credentials or connect a wallet.

Critical
VirusTotal
4 / 92
Blocklist matches
2
Scam type (automated label)
Seed Phrase Theft
Hosting
United Kingdom188.114.96.3CloudFLARENET-EU · CDN
Registrar
NetherlandsHosting Concepts
OTX
4 community refs
Page captures
7

Capture recorded with this analysis · Cloudflare Radar · 2026-10-31T23:06:39Z
SHA-256: 1412f59b39c8aa9ca169557f24ba70d4adb619020c79d309cda9ee8dc61a0225

PhishDestroy analysis, reviewed version

The captured page on sup-binance.sbs presents itself as a Binance fund recovery portal, headed "Get a Refund of Your Lost Funds" and describing a SAFU Reserve Framework for restitution. The main interaction is a claim submission flow: visitors are prompted to enter their details, specify the lost amount, and pass AML verification, with buttons to apply for a refund or track an existing case ID.

The stored VirusTotal domain result reports 4 detections out of 92 engines. Ermes reported "phishing"; Webroot reported "malicious".

Source evidenceVirusTotal 4 / 92 · OTX 4 references 8 sources

VirusTotal

4 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 9 fields

Observed: · Retrieved:

Vendor result counts

Timeout: 0; Harmless: 55; Malicious: 4; Suspicious: 0; Undetected: 33

Vendor labels

Ermes: phishing; Webroot: malicious; Alphamountain ai: phishing; Forcepoint threatseeker: phishing

Reputation score

0

Categories

Alphamountain ai: Phishing (alphaMountain.ai)

First seen

DNS records

TTL: 300; Type: A; Value: 172.67.147.242, TTL: 21600; Type: NS; Value: sage.ns.cloudflare.com, TTL: 300; Type: A; Value: 104.21.79.207, TTL: 21600; Type: NS; Value: zainab.ns.cloudflare.com, TTL: 300; Type: AAAA; Value: 2606:4700:3031::6815:4fcf, TTL: 300; Type: AAAA; Value: 2606:4700:3037::ac43:93f2, TTL: 1800; Type: SOA; Rname: dns.cloudflare.com; Value: sage.ns.cloudflare.com

DNS at

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

San: *.sup-binance.sbs, sup-binance.sbs; Issuer: Let's Encrypt / YE2; Serial: 54e792cd0a19ce38a0602636f5a74646a39; SHA256: 2bfda0cdf332aa9931a1c19c24385eaead4d29e31a2151bac531f9f32cbae2a2; Subject: sup-binance.sbs; Valid to: 2027-01-28T10:02:07Z; Valid from: 2026-10-30T10:02:08Z
Original source fields · JSON
Vendor result counts
Timeout: 0; Harmless: 55; Malicious: 4; Suspicious: 0; Undetected: 33
Vendor labels
Ermes: phishing; Webroot: malicious; Alphamountain ai: phishing; Forcepoint threatseeker: phishing
Reputation
0
Categories
Alphamountain ai: Phishing (alphaMountain.ai)
First seen
2026-10-30T12:33:56Z
DNS records
TTL: 300; Type: A; Value: 172.67.147.242, TTL: 21600; Type: NS; Value: sage.ns.cloudflare.com, TTL: 300; Type: A; Value: 104.21.79.207, TTL: 21600; Type: NS; Value: zainab.ns.cloudflare.com, TTL: 300; Type: AAAA; Value: 2606:4700:3031::6815:4fcf, TTL: 300; Type: AAAA; Value: 2606:4700:3037::ac43:93f2, TTL: 1800; Type: SOA; Rname: dns.cloudflare.com; Value: sage.ns.cloudflare.com
DNS at
2026-10-31T11:33:01Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
San: *.sup-binance.sbs, sup-binance.sbs; Issuer: Let's Encrypt / YE2; Serial: 54e792cd0a19ce38a0602636f5a74646a39; SHA256: 2bfda0cdf332aa9931a1c19c24385eaead4d29e31a2151bac531f9f32cbae2a2; Subject: sup-binance.sbs; Valid to: 2027-01-28T10:02:07Z; Valid from: 2026-10-30T10:02:08Z
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
Result state
observed
Numerator
4
Denominator
92
Vendors
alphaMountain.ai, Ermes, Forcepoint ThreatSeeker, Webroot
Observed at
2026-10-31 11:21:50
Checked at
2026-11-01 00:05:48
Fetched at
2026-10-31 23:05:48

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields
Separate stored summary: suspicious

This summary differs from the dated scan above. It is retained for provenance and does not override the selected source observation.

Verdict
suspicious
Categories
Security Risks
Source path
phishdestroy.technologies.cf_radar
Scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

URLScan

Malicious

SHA-256 46bcbe79436d689ad8e539559e3346e9996d7da2343199416cfee3c314419340

Open report
URLScanOriginal source recordObserved: 21 fields
Separate monitor record · 2026-11-01 04:30 UTC

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

UUID
01a19417-9dbd-73ce-a3e5-57563e41bdf8
Score
100
Malicious
✓
Result at
2026-11-01T04:30:21Z
Enriched at
2026-11-01T09:14:34Z
Source timestamps
Urlscan result at: 2026-11-01 05:30:21; Urlscan enriched at: 2026-11-01 10:14:34

OTX

4 community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

90 / 100 · heuristic score · 3 brand references · 1 classification

Open report
Separate monitor score · 90 / 100 · 2026-10-31T23:13:00Z

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

Heuristic score
90
Analyzed at
2026-10-31T23:13:00Z
Source timestamp
2026-11-01 00:13:00

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

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

Ai title
sup-binance.sbs Binance Fund Recovery Refund Claim Page
Ai description
PhishDestroy records the sup-binance.sbs fund recovery page, which invites visitors to submit a refund claim for lost funds.
Ai summary
The captured page on sup-binance.sbs presents itself as a Binance fund recovery portal, headed "Get a Refund of Your Lost Funds" and describing a SAFU Reserve Framework for restitution. The main interaction is a claim submission flow: visitors are prompted to enter their details, specify the lost amount, and pass AML verification, with buttons to apply for a refund or track an existing case ID. The stored VirusTotal domain result reports 4 detections out of 92 engines. Ermes reported "phishing"; Webroot reported "malicious".
Ai generated by
threat-v6-mimo
Ai generated at
2026-11-01 00:08:25
Revision
e3359b666cf0e60c1f5cba616078f6d720b6561fa1e29a34fb35735bf52a922d
Mode
reviewed
Interpretation
Selected public package; text generation time is separate from source observation dates.

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

Collected source details

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

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

Mail configuration

Spf lookups: 0

CAA records

Domain: sup-binance.sbs

Protective DNS results

Resolvers: 12; Blocked count: 0

Web archive observations

Last: 2026-10-31T22:35:15Z; First: 2026-10-31T22:35:15Z; Changes: 0; Days archived: 1; Avg page bytes: 99991

Page title and metadata

Title: Binance Fund Recovery | Get a Refund of Your Lost Funds (SAFU); Description: Official Binance Fund Recovery Assistance Program. Submit your claim, enter the lost amount, pass AML verification, and recover your digital assets securely.

Trackers

Requests: 8; Trackers: (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://cdn.jsdelivr.net/npm/ethers@6.13.5/dist/ethers.umd.min.js; Third party scripts: 1

HTTP response

Up: ✓; Code: 200; Timings: DNS: 5; TLS: 113; Wait: 97; Connect: 33; Download: 172; Response ms: 420

TLS connection

Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓

Ports

Open: 80, 443, 8080

Carbon estimate

Bytes: 354893; Co2 grams: 0.013; Cleaner than: 1

DNS server

NS: (IP: 172.64.35.236; Host: sage.ns.cloudflare.com), (IP: 172.64.34.149; Host: zainab.ns.cloudflare.com); Zone: sup-binance.sbs

Location

IP: 2a06:98c1:3120::3; ASN: 13335; Org: CloudFLARENET-EU; City: London; Country: GB

SSL

Issuer: Let's Encrypt / YE2; Subject: sup-binance.sbs

DNS records

A: 188.114.96.3, 188.114.97.3; NS: zainab.ns.cloudflare.com, sage.ns.cloudflare.com; Soa: Nsname: sage.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2418848518; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2a06:98c1:3121::3, 2a06:98c1:3120::3

DNSSEC

Ds: ✗; Rrsig: ✗; Dnskey: ✗

HSTS

Message: Site does not serve any HSTS headers.

HTTP security policies

Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗

Web application firewall

Waf: Cloudflare; Has waf: ✓

Get IP

IP: 2a06:98c1:3121::3; Family: 6

Redirects

Chain: https://sup-binance.sbs

Registration record

Registrar: Hosting Concepts B.V. d/b/a Registrar.eu; Created: 2026-10-30T10:48:10Z; Updated: 2026-10-30T10:48:14Z; Expires: 2027-10-30T23:59:59Z; Status: serverTransferProhibited https://icann.org/epp, clientTransferProhibited https://icann.org/epp, addPeriod https://icann.org/epp; Nameservers: sage.ns.cloudflare.com, zainab.ns.cloudflare.com

HTTP headers

Headers: Server: cloudflare; Content type: text/html
Original source fields · JSON
Mail configuration
Spf lookups: 0
Caa records
Domain: sup-binance.sbs
Protective DNS results
Resolvers: 12; Blocked count: 0
Web archive observations
Last: 2026-10-31T22:35:15Z; First: 2026-10-31T22:35:15Z; Changes: 0; Days archived: 1; Avg page bytes: 99991
Page title and metadata
Title: Binance Fund Recovery | Get a Refund of Your Lost Funds (SAFU); Description: Official Binance Fund Recovery Assistance Program. Submit your claim, enter the lost amount, pass AML verification, and recover your digital assets securely.
Trackers
Requests: 8; Trackers: (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://cdn.jsdelivr.net/npm/ethers@6.13.5/dist/ethers.umd.min.js; Third party scripts: 1
Status
Up: ✓; Code: 200; Timings: DNS: 5; TLS: 113; Wait: 97; Connect: 33; Download: 172; Response ms: 420
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443, 8080
Carbon
Bytes: 354893; Co2 grams: 0.013; Cleaner than: 1
DNS server
NS: (IP: 172.64.35.236; Host: sage.ns.cloudflare.com), (IP: 172.64.34.149; Host: zainab.ns.cloudflare.com); Zone: sup-binance.sbs
Location
IP: 2a06:98c1:3120::3; ASN: 13335; Org: CloudFLARENET-EU; City: London; Country: GB
SSL
Issuer: Let's Encrypt / YE2; Subject: sup-binance.sbs
DNS records
A: 188.114.96.3, 188.114.97.3; NS: zainab.ns.cloudflare.com, sage.ns.cloudflare.com; Soa: Nsname: sage.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2418848518; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2a06:98c1:3121::3, 2a06:98c1:3120::3
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Firewall
Waf: Cloudflare; Has waf: ✓
Get IP
IP: 2a06:98c1:3121::3; Family: 6
Redirects
Chain: https://sup-binance.sbs
Registration record
Registrar: Hosting Concepts B.V. d/b/a Registrar.eu; Created: 2026-10-30T10:48:10Z; Updated: 2026-10-30T10:48:14Z; Expires: 2027-10-30T23:59:59Z; Status: serverTransferProhibited https://icann.org/epp, clientTransferProhibited https://icann.org/epp, addPeriod https://icann.org/epp; Nameservers: sage.ns.cloudflare.com, zainab.ns.cloudflare.com
HTTP headers
Headers: Server: cloudflare; Content type: text/html

Questions about sup-binance.sbs

Is sup-binance.sbs legit?

PhishDestroy rates sup-binance.sbs as critical risk (90/100) from the recorded evidence; it was first recorded on 2026-10-31. Stored VirusTotal result: 4/92 engines flagged. Analysis time (as stored): 2026-10-31 11:21 UTC. Retrieved (as stored): 2026-10-31 23:05 UTC. 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 sup-binance.sbs safe to connect a wallet?

This report does not record which wallet requests sup-binance.sbs 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 sup-binance.sbs?

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

Last checked

Stored Capture · 7 captures

All capture links and hashes (7)
Observed page title
Binance Fund Recovery | Get a Refund of Your Lost Funds (SAFU)
Automated brand references
Binance Telegram WhatsApp
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 72 days

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Binance report ↗
IP Context United Kingdom188.114.96.3 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Hosting Concepts NL(NL)
RegistrationExpires Oct 30, 2027
Elapsed Since First Report 24h
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Nov 1, 2026score 90/1003 brand signals
Submitted URLhttp://sup-binance.sbs/
SHORTDOT ZONE · PUBLIC EVIDENCE .sbs

ShortDot zone evidence

The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.

ShortDot SA · Luxembourg 7 zones · full-zone evidence updated daily Open the ShortDot evidence repository (GitLab)
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

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

Accreditation is a contract, not a safety certification.

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

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United Kingdom188.114.96.3
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
CloudFLARENET-EU
Observed location
United KingdomLondon, GB
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • sage.ns.cloudflare.com
  • zainab.ns.cloudflare.com

SOA

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

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-30 10:02:08
Valid until
2027-01-28 10:02:07
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-31 23:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint2bfda0cdf332aa9931a1c19c24385eaead4d29e31a2151bac531f9f32cbae2a2
Certificate names · 2 SANs
  • *.sup-binance.sbs
  • sup-binance.sbs

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

Latest Classified Outcome 2026-11-15 17:12:58 UTC

The domain no longer resolves in DNS.

Technical details
Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN
RDAP registration
Observed timeline last reachable: 2026-11-01 11:02:17 UTC last content: 2026-11-01 11:02:17 UTC current episode first observed: 2026-11-11 10:22:06 UTC observed RIP window: 2026-11-01 11:02:17 UTC → 2026-11-01 23:02:00 UTC · 12.00h midpoint estimate ≈ 2026-11-01 17:02:08 UTC · precision medium · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 5 identified
Open complete records
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

4 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
Ermes
Webroot
alphaMountain.ai
Forcepoint ThreatSeeker

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of sup-binance.sbs ·

98
Good
Performance
FCP
2.01 s
First Contentful Paint
LCP
2.01 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
32 ms
Total Blocking Time
SI
2.01 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 200
Requested URL: http://sup-binance.sbs/
Binance Fund Recovery | Get a Refund of Your Lost Funds (SAFU)
Official Binance Fund Recovery Assistance Program. Submit your claim, enter the lost amount, pass AML verification, and recover your digital assets securely.
Response
HTTP 200
HTML body
346.9 KB
Compressed
96.7 KB
Links
0 internal · 0 external
Detected technologies
reactcloudflare
Selected response headers
Content-Type: text/html
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 14
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a536204d7f9b36ff-YYZ
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Sat, 31 Oct 2026 22:34:16 GMT
Last-Modified
Sat, 31 Oct 2026 20:14:59 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=cKjUtlgnUIETLJPOJaSNhivIIseylPsXU23N%2FqbYTkr2v2Vd29Z7lNWVcQptDG823tl7%2FdbG8FnsGfYqIGAyCroaBIlkx5VRK0rIa%2FrF3emXCfnUNtDlIydGCZf56BuVZPs%3D"}]
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
Vary
accept-encoding

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

Registration & observation details9

Availability observations

Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
12
Estimate basis
Bounded by observations
Estimate precision
Medium

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

All stored data116
Open complete records

Captured network requests

Network requests: 11 SHA-256 hashes: 11 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-10-31 22:34 UTC.

Open this scan on URLScan 01a19417-9dbd-73ce-a3e5-57563e41bdf8 ↗

Stored observation history11

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

  1. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  5. Availability monitor · Recorded state

    blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

Earlier observations 6
  1. Availability monitor · Recorded state

    blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  2. Availability monitor · Recorded state

    blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  3. Availability monitor · Recorded state

    blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  4. Domain monitor · Recorded state

    Reachable→Unavailable

  5. Availability monitor · Recorded state

    live_content

    content_served

  6. Domain monitor · First collection record

    Reachable

All retained availability observations41
Open complete records

Threat Response Pipeline

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

Recorded events: 14. 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
    sup-binance.sbs detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Blocklist Detection · OTX Community References · Automated brand label: Binance · Forensic Evidence Collected · Technical Analysis Recorded · Content Observed Unavailable Recorded: 11 of 11
Publication & AvailabilityDestroyList Published · Time to First Unavailability Recorded: 2 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Time to First Unavailability
    Hours from detection to the first unavailable observation: 24

Recorded activity

6 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Cloudflare Radar

    Phishing

    View source
  3. Wayback Machine

    Page archived

    View source
  4. Added to PhishDestroy

    sup-binance.sbs

    View source
  5. URLScan

    Page captured

    View source
  6. VirusTotal

    4/92 engine detections

    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.

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

Lookalike domains

187 stored lookalike domains

Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.

Show all (88)
binabce.com Replaced character Variant of binance.com NS ns1.dnsowl.com binacne.com Swapped characters Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binan.ce.com Split into subdomain Variant of binance.com A 13.248.169.48NS ns1.afternic.com binancecom.com Variant Variant of binance.com A 46.175.135.11MX mail.radinko.comNS ns1.radinko.com binanci.com Vowel swap Variant of binance.com A 107.161.23.204NS ns1.dnsowl.com binanco.com Vowel swap Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com binancr.com Replaced character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binancs.com Replaced character Variant of binance.com A 34.111.46.214NS dora.ns.cloudflare.com binancw.com Replaced character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binande.com Replaced character Variant of binance.com NS melina.ns.cloudflare.com binanfe.com Replaced character Variant of binance.com A 34.111.46.214NS dora.ns.cloudflare.com binanve.com Replaced character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binanxe.com Replaced character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binnace.com Swapped characters Variant of binance.com A 207.246.78.75NS ns1.dnsowl.com binonce.com Vowel swap Variant of binance.com A 103.224.182.241MX park-mx.above.comNS ns1.abovedomains.com binsnce.com Replaced character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binunce.com Vowel swap Variant of binance.com A 103.224.212.251NS ns1.abovedomains.com binynce.com Replaced character Variant of binance.com A 94.75.193.73MX mail.h-email.netNS ns1.thednscloud.com binznce.com Replaced character Variant of binance.com NS dns1.registrar-servers.com bniance.com Swapped characters Variant of binance.com A 103.59.100.240NS carlos.ns.cloudflare.com bunance.com Replaced character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net ibnance.com Swapped characters Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com ninance.com Replaced character Variant of binance.com A 52.20.84.62NS ns1.atom.com b-inance.com Added hyphen Variant of binance.com A 198.16.35.91NS a.share-dns.com b8inance.com Inserted character Variant of binance.com A 46.8.8.220MX mail.parktons.comNS ns.parktons.com b8nance.com Replaced character Variant of binance.com A 103.224.182.238MX park-mx.above.comNS ns1.abovedomains.com b9nance.com Replaced character Variant of binance.com A 13.223.25.84NS nsg1.namebrightdns.com bbinance.com Repeated character Variant of binance.com A 47.52.200.94NS donald.ns.cloudflare.com bhinance.com Inserted character Variant of binance.com A 46.175.135.11MX mail.radinko.comNS ns1.radinko.com bi-nance.com Added hyphen Variant of binance.com A 34.133.74.21NS ns-cloud-d1.googledomains.com biance.com Missing character Variant of binance.com A 8.223.50.77MX route1.mx.cloudflare.netNS raphaela.ns.cloudflare.com bibance.com Replaced character Variant of binance.com A 107.161.23.204NS ns1.dnsowl.com bibnance.com Inserted character Variant of binance.com A 103.224.182.253MX park-mx.above.comNS ns1.abovedomains.com bihance.com Replaced character Variant of binance.com A 104.21.54.163NS dora.ns.cloudflare.com bihnance.com Inserted character Variant of binance.com A 188.114.96.3NS cass.ns.cloudflare.com biinance.com Repeated character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net bijnance.com Inserted character Variant of binance.com A 62.116.130.8MX redirect.domain-robot.orgNS a.ns14.net biknance.com Inserted character Variant of binance.com A 13.223.25.84NS nsg1.namebrightdns.com bimance.com Lookalike letters Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net bimnance.com Inserted character Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com bin-ance.com Added hyphen Variant of binance.com A 13.248.169.48NS ns1.afternic.com binaance.com Repeated character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binabnce.com Inserted character Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com binace.com Missing character Variant of binance.com A 104.21.80.13NS josephine.ns.cloudflare.com binahce.com Replaced character Variant of binance.com A 209.196.146.115NS ns3.epik.com binamnce.com Inserted character Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com binan-ce.com Added hyphen Variant of binance.com NS a.share-dns.com binanbce.com Inserted character Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com binanc-e.com Added hyphen Variant of binance.com A 188.114.96.3MX route1.mx.cloudflare.netNS melinda.ns.cloudflare.com binanc.com Missing character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binanc3.com Replaced character Variant of binance.com A 34.111.46.214NS dora.ns.cloudflare.com binancce.com Repeated character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binancve.com Inserted character Variant of binance.com A 104.21.19.3NS dora.ns.cloudflare.com binancxe.com Inserted character Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com binancz.com Replaced character Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com binandce.com Inserted character Variant of binance.com A 62.116.130.8MX redirect.domain-robot.orgNS a.ns14.net binane.com Missing character Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binanec.com Lookalike letters Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binanhce.com Inserted character Variant of binance.com NS a.ns14.net binanmce.com Inserted character Variant of binance.com A 104.21.5.88NS dante.ns.cloudflare.com binannce.com Lookalike letters Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binanvce.com Inserted character Variant of binance.com A 104.21.62.177NS dora.ns.cloudflare.com binanxce.com Inserted character Variant of binance.com A 188.114.96.3NS dora.ns.cloudflare.com binarnce.com Lookalike letters Variant of binance.com NS ns1.julydns.com binasnce.com Inserted character Variant of binance.com A 104.21.91.34NS dora.ns.cloudflare.com binawnce.com Inserted character Variant of binance.com A 46.8.8.220MX mail.parktons.comNS ns.parktons.com binbance.com Inserted character Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com binhance.com Inserted character Variant of binance.com A 13.223.25.84NS nsg1.namebrightdns.com binmance.com Inserted character Variant of binance.com A 103.224.212.244NS ns1.abovedomains.com binnance.com Lookalike letters Variant of binance.com A 54.215.31.113NS ns1.dyna-ns.net binnce.com Missing character Variant of binance.com A 34.212.97.116NS a.dnspod.com binqance.com Inserted character Variant of binance.com A 172.233.219.123MX mx156.hostedmxserver.comNS ns1.parklogic.com binsance.com Inserted character Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com binwnce.com Replaced character Variant of binance.com A 104.21.45.206NS dante.ns.cloudflare.com binyance.com Inserted character Variant of binance.com A 62.116.130.8MX redirect.domain-robot.orgNS a.ns14.net bionance.com Inserted character Variant of binance.com A 81.169.145.65MX smtpin.rzone.deNS docks10.rzone.de birnance.com Lookalike letters Variant of binance.com MX ALT1.ASPMX.L.GOOGLE.comNS 1-you.njalla.no biunance.com Inserted character Variant of binance.com A 188.114.96.3NS dante.ns.cloudflare.com bjnance.com Replaced character Variant of binance.com A 13.223.25.84NS nsg1.namebrightdns.com bnance.com Missing character Variant of binance.com A 13.248.169.48NS ns1.afternic.com bninance.com Inserted character Variant of binance.com A 104.21.36.233NS dante.ns.cloudflare.com boinance.com Inserted character Variant of binance.com A 94.75.193.70MX mail.h-email.netNS ns1.thednscloud.com bonance.com Replaced character Variant of binance.com A 198.185.159.145MX alt1.aspmx.l.google.comNS ns-cloud-b1.googledomains.com buinance.com Inserted character Variant of binance.com A 13.223.25.84NS nsg1.namebrightdns.com bvinance.com Inserted character Variant of binance.com A 13.248.169.48NS ns3.afternic.com clinance.com Lookalike letters Variant of binance.com A 52.44.244.98MX mail1.namebrightmail.comNS ns1.namebrightdns.com dinarce.com Lookalike letters Variant of binance.com A 44.227.65.245MX fwd1.porkbun.comNS curitiba.ns.porkbun.com ginance.com Replaced character Variant of binance.com A 13.248.158.7NS 1ns.yahoo.com

Showing 100 of 187

Check for cloaking

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

sup-binance.sbs

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

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

Official reporting routes

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.

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

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

Where should I report the scam?

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

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

How do phishing scams typically work?

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

How can I protect myself in the future?

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

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

Stay Informed, Stay Safe

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

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

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

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

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

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

Embed This Report

Share this threat intelligence on your website or blog

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