Skip to security report
helpteam-binance.com favicon
Domain security and threat intelligence

helpteam-binance.com

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

PhishDestroy first recorded helpteam-binance.com on 2026-11-22. Listed by external blocklists: MetaMask, SEAL.

More about the sources
Recorded security signals

Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.

Stored blocklist matches: 2 Young domain: 2 days old
Registrar
One.com A/S
Resolved IP
Denmark46.30.211.38One.com A/S
Registered
2026-11-20
First seen by PhishDestroy
2026-11-22
Page captures
open gallery
Reports sent
view timeline
2026-11-22 1 Report Sent

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded helpteam-binance.com on 2026-11-22. Listed by external blocklists: MetaMask, SEAL. Risk: high (evidence score 66/100). Registrar: One.com A/S. Hosting: One.com A/S. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

High
Blocklist matches
2 external + PhishDestroy list
Hosting
Denmark46.30.211.38One.com A/S
Registrar
One.com A/S
Registered
2026-11-20
Page captures
3

Recorded source summary

PhishDestroy first observed helpteam-binance.com on Nov 22, 2026. The hostname explicitly references Binance; stored content metadata identifies the same apparent target. Current evidence score: 66/100 (high).

Positive findings are stored from 2 sources: MetaMask and SEAL. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Nov 22, 2026 at 15:20 UTC. Additional recorded evidence: VirusTotal recorded 0 detections among 92 engines on Nov 22, 2026 at 01:23 UTC.

The collector marked the hostname reachable on Nov 22, 2026 at 15:34 UTC, but did not retain the HTTP response code. Registration records for the domain list One.com A/S as the registrar and Nov 20, 2026 as the creation date. Registration preceded first observation by 2 days. At collection time, the hostname resolved to 46.30.211.38 on AS51468 (One.com A/S). The recorded endpoint location is Copenhagen, DK. The stored server header is nginx/1.18.0 (Ubuntu). The evidence archive retains 3 visual captures from PhishDestroy, URLScan, and Cloudflare Radar; the captures preserve the landing-page appearance.

The content indicators and 2 positive source findings support the current Binance impersonation and phishing classification. The target field identifies Binance.

Source evidence 2 sources

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
VirusTotalOriginal source recordObserved: 13 fields
Open complete records
Website checksOriginal source recordRetrieved: 13 fields

Mail configuration

MX records
  • mx3.mailpod16-cph3.g1i.one.com
  • mx2.mailpod16-cph3.g1i.one.com
  • mx1.mailpod16-cph3.g1i.one.com
  • mx4.mailpod16-cph3.g1i.one.com
SPF record
v=spf1 include:_custspf.one.com ~all
DANE
Yes
DMARC
Yes
SPF lookups
1

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

TLS connection

ALPN
http/1.1
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
No
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    195.206.121.10
    Host
    ns01.one.com
  • IP address
    185.10.11.10
    Host
    ns02.one.com
DNS zone
helpteam-binance.com

Location

IP address
46.30.211.38
ASN
51468
Organization
One.com A/S
City
Copenhagen
Country
DK

TLS certificate

Subject alternative names
  • *.one.com
  • one.com
Key size, bits
4096
Certificate chain
  • *.one.com
  • YR1
  • Root YR
  • ISRG Root X1
Issuer
Let's Encrypt / YR1
Serial
058DB78939139C536698D0DE76138CE89643
SHA-256
59a3b6168e7faf13fb00bbfca4abbbc1b3fbefda43633638e8f3e735da296aa0
Subject
*.one.com
Valid until
Valid from

DNS records

A
  • 46.30.211.38
MX
  • Mail server
    mx4.mailpod16-cph3.g1i.one.com
    Priority
    10
  • Mail server
    mx2.mailpod16-cph3.g1i.one.com
    Priority
    10
  • Mail server
    mx1.mailpod16-cph3.g1i.one.com
    Priority
    10
  • Mail server
    mx3.mailpod16-cph3.g1i.one.com
    Priority
    10
NS
  • ns01.one.com
  • ns02.one.com
SOA
Primary nameserver
ns01.one.com
Hostmaster
hostmaster.one.com
Serial
2026112101
Refresh, seconds
14400
Retry, seconds
3600
Expiry, seconds
1209600
Minimum TTL, seconds
600
TXT
  • v=spf1 include:_custspf.one.com ~all

DNSSEC

DS record
Yes
RRSIG
Yes
DNSKEY
Yes

IP lookup

IP address
46.30.211.38
IP version
4

TXT records

Records
  • v=spf1 include:_custspf.one.com ~all

Technology stack

Technologies
  • Ubuntu
  • Nginx 1.18.0

Registration record

Registrar
One.com A/S
Registrar IANA ID
1462
Registrar URL
http://www.one.com
Registered
Updated
Expires
Status
  • ok https://icann.org/epp
Nameservers
  • ns01.one.com
  • ns02.one.com
DNSSEC
signedDelegation
Original source fields · JSON
Mail configuration
MX: mx3.mailpod16-cph3.g1i.one.com, mx2.mailpod16-cph3.g1i.one.com, mx1.mailpod16-cph3.g1i.one.com, mx4.mailpod16-cph3.g1i.one.com; Spf: v=spf1 include:_custspf.one.com ~all; Dane: ✓; Dmarc: ✓; Spf lookups: 1
Protective DNS results
Resolvers: 12; Blocked count: 0
TLS connection
Alpn: http/1.1; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✗; Forward secrecy: ✓
Ports
Open: 80, 443
DNS server
NS: (IP: 195.206.121.10; Host: ns01.one.com), (IP: 185.10.11.10; Host: ns02.one.com); Zone: helpteam-binance.com
Location
IP: 46.30.211.38; ASN: 51468; Org: One.com A/S; City: Copenhagen; Country: DK
SSL
San: *.one.com, one.com; Bits: 4096; Chain: *.one.com, YR1, Root YR, ISRG Root X1; Issuer: Let's Encrypt / YR1; Serial: 058DB78939139C536698D0DE76138CE89643; SHA256: 59a3b6168e7faf13fb00bbfca4abbbc1b3fbefda43633638e8f3e735da296aa0; Subject: *.one.com; Valid to: 2026-12-23T03:39:20Z; Valid from: 2026-09-24T03:39:21Z
DNS records
A: 46.30.211.38; MX: Exchange: mx4.mailpod16-cph3.g1i.one.com; Priority: 10, Exchange: mx2.mailpod16-cph3.g1i.one.com; Priority: 10, Exchange: mx1.mailpod16-cph3.g1i.one.com; Priority: 10, Exchange: mx3.mailpod16-cph3.g1i.one.com; Priority: 10; NS: ns01.one.com, ns02.one.com; Soa: Nsname: ns01.one.com; Hostmaster: hostmaster.one.com; Serial: 2026112101; Refresh: 14400; Retry: 3600; Expire: 1209600; Minttl: 600; Txt: v=spf1 include:_custspf.one.com ~all
Dnssec
Ds: ✓; Rrsig: ✓; Dnskey: ✓
Get IP
IP: 46.30.211.38; Family: 4
Txt records
Records: v=spf1 include:_custspf.one.com ~all
Tech stack
Technologies: Ubuntu, Nginx 1.18.0
Registration record
Registrar: One.com A/S; Registrar iana ID: 1462; Registrar URL: http://www.one.com; Created: 2026-11-20T10:40:27Z; Updated: 2026-11-21T03:33:34Z; Expires: 2027-11-20T10:40:27Z; Status: ok https://icann.org/epp; Nameservers: ns01.one.com, ns02.one.com; Dnssec: signedDelegation

Questions about helpteam-binance.com

Is helpteam-binance.com legit?

PhishDestroy rates helpteam-binance.com as high risk (evidence score 66/100) from the recorded evidence; it was first recorded on 2026-11-22. 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 helpteam-binance.com safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on helpteam-binance.com. A confirmed blockchain transaction cannot be reversed.

What should I do if I used helpteam-binance.com?

  • 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
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • 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 matches2 external + PhishDestroy list · MetaMask · PhishDestroy · SEAL 2
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Page captures (3)

All capture links and hashes (3)

Domain details

Domain
Registrar One.com A/S
Hosting abuse contact abuse@one.com One.com A/S · AS51468
RegistrationCreated 2026-11-20 (2d · Brand New!) — Expires 2027-11-20
WHOIS statusNo restrictions
Technical detailsProvenance & timestamps
First Detected2026-11-22
Submitted URLhttp://helpteam-binance.com/
Case ID

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Denmark46.30.211.38
Network ASN
AS51468
Organization
One.com A/S
Observed location
DenmarkCopenhagen, DK
Server header
nginx/1.18.0 (Ubuntu)

Nameservers 2

  • ns01.one.com
  • ns02.one.com

SOA

  • nsname: ns01.one.com
  • hostmaster: hostmaster.one.com
  • serial: 2026112101
  • refresh: 14400
  • retry: 3600
  • expire: 1209600
  • minttl: 600

Mail routing 4 MX records

  • mx4.mailpod16-cph3.g1i.one.compriority 10
  • mx2.mailpod16-cph3.g1i.one.compriority 10
  • mx1.mailpod16-cph3.g1i.one.compriority 10
  • mx3.mailpod16-cph3.g1i.one.compriority 10

Location describes the IP network.

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://helpteam-binance.com/
Hosted by one.com
Response
HTTP 200
HTML body
192.5 KB
Compressed
132.7 KB
Links
0 internal · 4 external
Detected technologies
vuenginxwordpress
Selected response headers
Server: nginx/1.18.0 (Ubuntu)
Content-Type: text/html; charset=UTF-8
Cache-Control: max-age=315360000
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 13
Access-Control-Allow-Origin
*
Cache-Control
max-age=315360000
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Sun, 22 Nov 2026 15:36:35 GMT
Etag
W/"671b13b4-3021c"
Expires
Thu, 31 Dec 2037 23:55:55 GMT
Last-Modified
Fri, 25 Oct 2024 03:42:44 GMT
Server
nginx/1.18.0 (Ubuntu)
Transfer-Encoding
chunked
Vary
Accept-Encoding
X-node
webproxy2.cst.cdnpod2-cph3.one.com

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

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.

All stored data69
Open complete records

Captured network requests

Network requests: 2 SHA-256 hashes: 2 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-22 15:35 UTC.

Open this scan on URLScan 01a203e3-abac-703b-b3e8-c747992145da ↗

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. Domain monitor · First collection record

    Reachable

All retained availability observations0

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

No retained observations are recorded.

Threat Response Pipeline

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

Recorded events: 9. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    helpteam-binance.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Blocklist Detection · Automated brand label: Binance · Forensic Evidence Collected recorded
Notification RecordsSent Report Recorded recorded
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: One.com A/S. Abuse contacts: 1.
    • abuse@one.com
Publication & AvailabilityDestroyList Published recorded

Recorded activity

3 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+52 h 53 min
  3. First abuse report sent+12 min

Reported 53 h 6 min after registration

  1. Abuse report sent

    PD-3C204928280497016C04 · Receipt 85601

    abuse@one.com
    +12 min
  2. Added to PhishDestroy

    helpteam-binance.com

    same minute
  3. URLScan

    Page captured

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.

Showing 12 of 187

Show 88 more
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.

helpteam-binance.com

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-3C204928280497016C04 Recipient: abuse@one.com
Page title stored with report: Hosted by one.com
PDF notice generated Notice text archived (336 characters)
Abuse notice text as sent to the provider
Registrar policy. Per One.com A/S's published terms: ““AUP bans phishing, online fraud, malware hosting and deceptive activities; One.com may suspend domain names and terminate services involved in abuse.””
Applicable law. Domestic legal framework (Denmark / EU): Danish Penal Code IT offences; EU Directive 2013/40/EU; ICANN DNS Abuse.
Deep Analysis

Were You Affected by This Site?

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. Secure your accounts and funds first, then report. 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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

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.

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.

  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
  • 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
  • Downloaded a file — do not open it and scan the device with security software

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 helpteam-binance.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

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

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

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

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/helpteam-binance.com"
  title="PhishDestroy threat report for helpteam-binance.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>