VirusTotal
11 / 91 engine detections
The captured page presents a Binance-branded account creation screen titled "Create a free account | Binance." Visitors are prompted to enter an email address or phone number, accept the platform's terms, and continue to the next step, with alternative sign-in options through Google, Apple, and Telegram. The record shows that binanceu.com redirected to accounts.binance.com before this screen was captured.
“Create a free account | Binance”
Capture recorded with this analysis · Stored capture · Exact capture time not retained
SHA-256: 1e2d0e9724a5feb463d14f77764ac0606dfc531da9756cf68dc1056e8a553101
PhishDestroy analysis, reviewed version
The captured page presents a Binance-branded account creation screen titled "Create a free account | Binance." Visitors are prompted to enter an email address or phone number, accept the platform's terms, and continue to the next step, with alternative sign-in options through Google, Apple, and Telegram. The record shows that binanceu.com redirected to accounts.binance.com before this screen was captured.
VirusTotal analysis flagged binanceu.com with 11 detections out of 91 engines. Among the reporting vendors, alphaMountain.ai and BitDefender both flagged the target. The scan scope was not preserved in the record, so this result cannot be attributed specifically to a domain-level scan.
11 / 91 engine detections
checked — no detections recorded
Open report23 community references
Open reportprovider verdict: clean
Open reportObserved: · Retrieved:
| UUID | d11c1735-f554-4c51-bf72-143fb863542c |
|---|---|
| Final URL | https://accounts.binance.com/register |
| Status | 202 |
| History | URL: https://binanceu.com/; Status: 200, URL: https://accounts.binance.com/register; Status: 202 |
| DOM structure hash | 7378f40d12a9b793c8ab7ebb109d01c878b78c674830841ee61c7ec0a3d023c5 |
| Document hash | b014150f3d2210c02244b881d07d3d7d33d426f0d9764a66947276e873bc65aa |
| Radar rank | Bucket: >200000 |
| DNS records | Name: accounts.binance.com; Type: CNAME; Value: d2dbdn71e1vorj.cloudfront.net, Name: accounts.binance.com; Type: CNAME; Value: d2dbdn71e1vorj.cloudfront.net |
| Dnssec valid | ✗ |
| IP | 18.65.39.44 |
| Registration record | Registrar: MarkMonitor Inc.; Created: 2017-04-01T16:48:33Z; Updated: 2025-03-01T10:32:07Z; Expires: 2027-04-01T16:48:33Z; Nameservers: ns-1319.awsdns-36.org, ns-1701.awsdns-20.co.uk, ns-234.awsdns-29.com, ns-735.awsdns-27.net |
No threat flag
Open reportNo malicious flag
Open reportSeparate stored monitor snapshot; does not replace the primary report record or establish current availability.
Check recorded; verdict not retained
Open reportNo report found
Open reportA missing report is not a trust verdict. Legacy zeroes remain in the stored record; the measured trust score is unavailable.
98 / 100 · heuristic score · 1 brand reference · 1 classification
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Narrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
PhishDestroy rates binanceu.com as critical risk (98/100) from the recorded evidence; it was first recorded on 2026-02-26. Stored VirusTotal result: 11/91 engines flagged. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
This report does not record which wallet requests binanceu.com makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.
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.
Checked, no match
Last checked
Edge-IP reputation is not attributed to this domain.
elinore.ns.cloudflare.comLocation describes the IP network.
f60104baf7679310971dd97b54275c722994350be98a5c37bb705ea1ed385f1cbinanceu.com*.binanceu.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The site was serving its pages at the latest check.
Google PageSpeed Insights — mobile performance audit of binanceu.com ·
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 106 SHA-256 hashes: 106 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-29 05:43 UTC.
Open this scan on URLScan 0198f49d-4470-763d-b6af-c29091f696c7 ↗
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
binanceu.com Source: domain_monitor. This stored snapshot does not establish current availability.
Recorded events: 10. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
23 community references
View source11/91 engine detections
View sourcePage captured
View sourcebinanceu.com
View sourceWe 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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
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| ID | Stored data |
|---|
186 stored lookalike domains
Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.
binance.com. Variant of binance.com · first seen 2026-03-17 Showing 100 of 186
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.
IC3 does not accept attachments. Keep original evidence for investigators. IC3 guidance
Federal tips line1-800-CALL-FBICurrent service: Report Fraud. England, Wales and Northern Ireland. Scotland: 101.
Contact centre0300 123 2040Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Select 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.
Template-based draft • optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
binanceu.com)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.