The domain www.idxsolana.io was registered on March 28, 2026 through HOSTINGER operations, UAB. It resolves to the IPv4 address 34.160.37.117, which is hosted in the United States on Google Cloud. The authoritative nameservers are ns2.wixdns.net and ns3.wixdns.net, and the site presents a valid SSL certificate issued by Google Trust Services under the WR1 identifier. The HTTP response code is 200 and the page title returned is “idx | solana blockchain”, indicating an explicit reference to the Solana brand. Intelligence classifies the site as a crypto drainer using a Solana drainer kit, and the risk level is marked critical. The domain is currently listed on one security blocklist and has been blocked by PhishDestroy. A Gridinsoft trust score of 0 out of 100 further confirms its malicious nature. No public detections from external scanning services are available, so the absence of flags should not be interpreted as safety. Defenders should continue to block the domain at network perimeter, update endpoint and DNS filtering policies, and monitor for any traffic to the associated IP address. Incident response teams should treat any Solana‑related transactions originating from this host as potentially compromised and advise users to refrain from interacting with the site.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
Telegram
https://t.me/IDX_Crypto_NewsStored page reference
Telegram
https://t.me/IDX_SolanaStored page reference
IoC extraction recorded 2026-07-29 02:08:19 UTC
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-185045.invalid', port=80): Max retries exceeded with url: / (Caused by
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
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.
Technical detailsProvenance & timestamps
First DetectedMar 28, 2026
IoC Extractionscanned Jul 29, 20260 wallet · 2 Telegram IoCs
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
Resolved IP
34.160.37.117
Network ASN
AS396982
Organization
Google Cloud
Observed location
Kansas City, US
Server header
Pepyaka
Nameservers 2
ns2.wixdns.net
ns3.wixdns.net
Location describes the IP network.
TLS certificate
Issuer
Google Trust Services / WR1
Valid from
2026-02-12 08:24:59
Valid until
2026-05-13 08:24:58
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-03-28 13:50:48 UTC
Collection source
PhishDestroy collector
Certificate fingerprint61dcd3173256166df6a725bed5213e557beb89dc0357106066398f65ee06a621Certificate names · 1 SANs
idxsolana.io
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:30:57 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-23 02:12:22 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 duplicate-disabled-185045.invalid· checked Mar 28, 2026
42
Poor
Performance
FCP
3s
First Contentful Paint
LCP
8.33s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
962ms
Total Blocking Time
SI
7.03s
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.
Domain Status Transition2026-09-25 01:31:10 UTC
Domain state transitioned from alive to dead.
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
duplicate-disabled-185045.invalid detected and queued for full analysis
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 25, 2026
Time to First Unavailability
618 hours elapsed from detection to the first unavailable observation.
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+
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 recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If a wallet, seed phrase, or account was exposed, report the incident immediately. Revoke approvals and move remaining assets to a new wallet created on a trusted device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Guaranteed crypto recovery is a fraud indicator. 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.
Content matches1
Same favicon hash or the same page title as this host.
Chainabuse — flag scam wallets across exchanges & platforms
Your crypto exchange — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
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 crypto scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Malicious approvals — "connect wallet" prompts that grant unlimited token spending to attackers
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
Fake ads & airdrops — Google/social media ads and "free token" offers leading to wallet drainers
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Use a hardware wallet (Ledger, Trezor). Never store large amounts in browser wallets
Bookmark official sites — never click links from emails, DMs, or ads
Read every approval — verify permissions before signing. Reject unlimited approvals
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
HTML · IFRAME
Embed This Report
Share this threat intelligence on your website or blog
READ-ONLY
embed.html
<iframesrc="https://phishdestroy.io/embed/domain/duplicate-disabled-185045.invalid"title="PhishDestroy threat report for duplicate-disabled-185045.invalid"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>
(LT)
