Security engines reporting a detection: 11. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
The domain binanceintelligence-binance.com was observed with a VirusTotal detection record on 2026-10-08, documenting its presence in multiple security sources. Additionally, the domain was first observed on 2026-10-09 and has entries on external blocklists.
Recorded Evidence
VirusTotal checked binanceintelligence-binance.com on 2026-10-08, recording 11 detections out of 92 total scanners. On 2026-10-09, the domain was listed on the MetaMask and SEAL external blocklists. OTX registered three pulses referencing this domain as of 2026-10-09. The domain was registered with GoDaddy.com, LLC on 2026-09-30 and was internally listed by PhishDestroy on 2026-10-09.
Interpretation
PhishDestroy provides an internal listing of binanceintelligence-binance.com, which documents its inclusion in a curated database of security observations. VirusTotal's record contains detection counts from a broad range of scanners, offering a quantitative measure of how many sources flagged the domain. The presence of the domain on MetaMask and SEAL blocklists, along with OTX pulse references, expands the scope of external monitoring and highlights its visibility across multiple security platforms.
Recommended Actions
For binanceintelligence-binance.com, retain the VirusTotal detection record and blocklist entries as reference points for ongoing review. Compare the OTX pulse data and PhishDestroy listing with future observations to track any changes in security context. Use these dated records to inform any further technical or procedural assessments involving this domain.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-09 16:28:48 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-09 16:28:48 UTC
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.
Google PageSpeed Insights — mobile performance audit of binanceintelligence-binance.com· checked Oct 9, 2026
100
Good
Performance
FCP
1.11s
First Contentful Paint
LCP
1.11s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.11s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-10-09 16:28:48 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 75.2.60.5.
Threat Response Pipeline
Discovery
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
binanceintelligence-binance.com detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
5 evidence signal groups linked0 reports recordedUnverified
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.
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 →
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(US)
