VirusTotal
15 / 91 engine detections
Open reporttradingview.is is a Tradingview impersonation page detected by PhishDestroy on 2026-09-19. Risk: critical (100/100). Status: Last known active. Hosting: ALEXHOST SRL. PhishDestroy sent 1 abuse report. VirusTotal: 15/91 engines flag it. Do not enter credentials or connect a wallet.
“Download TradingView: Charts, Alerts and Market Analysis”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@alexhost.com.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
15 / 91 engine detections
Open report3 threat-system alerts
Open reportMalicious
Open report4 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
tradingview.is is an impersonation phishing site built to look like an official TradingView download portal, titled "Download TradingView: Charts, Alerts and Market Analysis." It targets stock and crypto traders who rely on TradingView for charts and alerts and expect a desktop client from the brand. PhishDestroy first flagged it on 2026-09-19. As of 2026-10-19 the site was still online and serving its content.
The page copies TradingView's look and promises a download of its charting software. That lure is aimed at users who would normally install the app from the vendor itself. Fake download pages of this kind typically hand out a trojanized installer or route visitors to a login or wallet prompt. Victims then lose account credentials, saved browser data or access to crypto wallets on the infected machine. TradingView's real software is not distributed through this domain.
Fifteen of 91 VirusTotal engines marked the domain as malicious on 2026-09-29. The flagging vendors include BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, alphaMountain.ai, CRDF, CyRadar and Chong Lua Dao. urlscan.io returned a malicious verdict and identified TradingView branding on the page, which confirms the impersonation. Besides PhishDestroy, the domain sits on the MetaMask and SEAL blocklists, so wallet-focused defenders treat it as a crypto threat. It also appears in four AlienVault OTX threat pulses.
The domain was registered on 2026-07-28, about seven weeks before PhishDestroy detected it. That gap left room to build and test the fake page before promoting it. The site resolves to 94.103.188.99 on the ALEXHOST SRL network in Moldova. Its Let's Encrypt certificate gives the browser padlock, but that only means the connection is encrypted, not that the site is genuine.
If you downloaded and ran anything from this site, treat that computer as compromised. Disconnect it, run a full scan with a reputable security tool, and consider a clean reinstall. From a separate, clean device, change your TradingView, email and exchange passwords and turn on app-based 2FA. If a crypto wallet or seed phrase was stored on the affected machine, move the funds to a new wallet created on a clean device. Defenders should block the domain and its IP and search endpoint and proxy logs for downloads from it.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a0b8be-e77c-72b8-9a48-d5dce5f7c7ba |
|---|---|
| Final url | https://tradingview.is/en/ |
| Status | 200 |
| Redirected | same-domain |
| Redirects | [
{
"to": "https://tradingview.is/",
"from": "http://tradingview.is/",
"status": 307
},
{
"to": "https://tradingview.is/en/",
"from": "https://tradingview.is/"
}
] |
| Ip | 94.103.188.99 |
| Ptr | mo2.mo.com |
| Contacted domains | [
"cloudflareinsights.com",
"a.dffg524.cn",
"collect-v6.51.la",
"static.cloudflareinsights.com",
"sdk.51.la"
] |
| Contacted IP addresses | [
"43.159.107.113",
"104.16.79.73",
"104.21.8.138",
"120.52.95.244",
"94.103.188.99"
] |
| Asns | [
"139341",
"13335",
"133119",
"200019"
] |
| Countries | [
"SG",
"CN",
"MD"
] |
| Linked domains | [
"www.tradingview.com",
"dl.wzjdessae.com",
"itunes.apple.com",
"play.google.com",
"status.tradingview.com"
] |
| Document hash | 6bc0f8e184da939ee99e5e9d4704469c41e538b83f5011caf2b20cb6b14d4927 |
| Script hashes | [
"00091485e63c7f0366c65607d74e4d942db985a7a5bd4afaaed5650631b2353b"
] |
| Globals | [
"LA",
"laWaitTime",
"SiteTongji",
"__cfBeacon"
] |
| Cookies | [
"__vtins__3QATeHgZyB5nfEbC",
"__51uvsct__3QATeHgZyB5nfEbC",
"__51vcke__3QATeHgZyB5nfEbC",
"__51vuft__3QATeHgZyB5nfEbC"
] |
| Tls | {
"san": [
"tradingview.is"
],
"cipher": "AES_256_GCM",
"issuer": "YR1",
"subject": "tradingview.is",
"protocol": "TLS 1.3",
"valid_to": "2026-10-26T15:05:50Z",
"valid_from": "2026-07-28T15:05:51Z"
} |
| Domain age days | 52 |
| Apex age days | 52 |
| Tls age days | 52 |
| Tls valid days | 89 |
| Requests | 20 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 95,
"malicious": true
},
"overall": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"tradingview"
],
"malicious": true,
"categories": [
"phishing"
]
},
"urlscan": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"TradingView"
],
"malicious": true,
"categories": [
"phishing"
]
}
} |
| HTTP headers | {
"server": "nginx",
"content-type": "text/html",
"strict-transport-security": "max-age=31536000"
} |
Observed: · Retrieved:
| Uuid | 63ab8dda-5701-425a-ae3d-315771357603 |
|---|---|
| Final url | https://tradingview.is/en/ |
| Status | 200 |
| History | [
{
"url": "https://tradingview.is/",
"status": 200
},
{
"url": "https://tradingview.is/en/",
"status": 200
}
] |
| DOM structure hash | 61fa2925674f197770a4f778f7f5226b9b5c49ab7065ddaaf6094b2e114ef234 |
| Document hash | 6bc0f8e184da939ee99e5e9d4704469c41e538b83f5011caf2b20cb6b14d4927 |
| Domain risks | [
"Brokerage & Investing",
"Business & Economy"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "tradingview.is",
"type": "A",
"value": "94.103.188.99"
}
] |
| Dnssec valid | false |
| Ip | 94.103.188.99 |
| Registration record | {
"created": "2026-07-28T13:20:01Z",
"updated": "2026-07-28T16:02:00Z",
"nameservers": [
"forwarding00.isnic.is",
"forwarding01.isnic.is"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 43,
"malicious": 13,
"suspicious": 2,
"undetected": 34
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"ESET": "suspicious",
"VIPRE": "malware",
"G-Data": "phishing",
"Lionic": "phishing",
"Sophos": "phishing",
"CyRadar": "phishing",
"Fortinet": "phishing",
"SOCRadar": "phishing",
"Kaspersky": "phishing",
"Gridinsoft": "suspicious",
"BitDefender": "phishing",
"Chong Lua Dao": "malicious",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Expires | 2027-07-28T00:00:00Z |
| First seen | 2026-07-28T22:19:37Z |
| DNS records | [
{
"ttl": 21600,
"type": "SOA",
"rname": "forwadm.isnic.is",
"value": "forwarding00.isnic.is"
},
{
"ttl": 21600,
"type": "NS",
"value": "forwarding00.isnic.is"
},
{
"ttl": 3600,
"type": "TXT",
"value": "google-site-verification=nYCTSZ0fKI5osoU60l2thNpIMd_tT6Tez4QpqrzZq10"
},
{
"ttl": 21600,
"type": "NS",
"value": "forwarding01.isnic.is"
},
{
"ttl": 3600,
"type": "A",
"value": "94.103.188.99"
}
] |
| Dns at | 2026-10-21T10:51:27Z |
| Jarm | 3fd3fd0003fd3fd00042d42d0000002059a3b916699461c5923779b77cf06b |
| Certificate | {
"san": [
"tradingview.is"
],
"issuer": "Let's Encrypt / YR2",
"serial": "67e2f84d52eec8e045118418d61dbc387e9",
"sha256": "05bf52b9115208b76a487975574f5a2c7515efe251365919767cdad40b33269a",
"subject": "tradingview.is",
"valid_to": "2026-12-24T10:05:46Z",
"valid_from": "2026-09-25T10:05:47Z"
} |
| Registration record | {
"dnssec": "unsigned delegation"
} |
| Registry data | {
"status": [
"active"
],
"events": {
"last changed": "2026-07-28T16:02:00Z",
"registration": "2026-07-28T13:20:01Z",
"soft expiration": "2027-07-28T13:17:06Z"
}
} |
No. PhishDestroy classifies tradingview.is as a Tradingview impersonation page (risk: critical, 100/100); it was first detected on 2026-09-19. VirusTotal: 15/91 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on tradingview.is. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
Last checked
forwarding00.isnic.isforwarding01.isnic.isLocation describes the IP network.
05bf52b9115208b76a487975574f5a2c7515efe251365919767cdad40b33269atradingview.isSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of tradingview.is · checked Sep 19, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
alive_content: raw=ok; http=200; via=https_proxy; server=nginx
tradingview.is
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
live_content
content_served
7→8
6→7
4→6
0→4
Reachable
4 community references
View sourceNo threat flag
View source15/91 engine detections
View sourcePD-20260919-354A07
tradingview.is
View sourcePage captured
View sourcePD-20260919-354A07 Recipient: abuse@alexhost.com If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
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 ↗
tradingview.is)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.