VirusTotal
1 / 95
“loginPage_login”
Analysis of www.solflarer.vip indicates a dedicated brand‑impersonation campaign targeting Solflare users. The domain was registered on March 13 2025 through NameSilo, LLC and has remained active for roughly 16 months before being taken offline as of the report date. DNS resolution points to the single IPv4 address 108.138.106.33, which belongs to Amazon.com, Inc. (AS16509) and is geolocated to the United States. The hosting provider is therefore the Amazon AWS infrastructure, a common choice for transient malicious sites because of rapid provisioning and flexible billing. The authoritative name servers are ns1.dnsowl.com, ns2.dnsowl.com and ns3.dnsowl.com, suggesting use of a third‑party DNS service rather than the registrar’s default.
No TLS certificate is presented; HTTPS connections are unavailable, which may be a deliberate choice to reduce overhead or to avoid certificate‑based reputation checks. Content‑level indicators are limited to the page title “loginPage_login”, consistent with a credential‑collection front end, and the explicit classification of the scam type as “Brand Impersonation” with Solflare identified as the victim brand. No additional page content has been captured, and the site’s visual elements remain unverified. Reputation data show the domain appears on a single security blocklist and has been flagged by one of ninety‑five VirusTotal scanners, reflecting a low but non‑zero detection rate. The Gridinsoft trust score of 0 / 100 further reinforces the malicious nature of the site.
PhishDestroy has already blocked the domain, and the current HTTP status is offline, indicating that the operator has likely withdrawn the site after a brief campaign window. For defenders, the primary mitigation steps are to add the IP address 108.138.106.33 and the domain www.solflarer.vip to network‑level deny lists, monitor for any resurgence of the same infrastructure, and enforce strict verification of Solflare‑related communications.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-5057.invalid', port=80): Max retries exceeded with url: / (Caused by Ne
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.
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.
ns1.dnsowl.comns2.dnsowl.comns3.dnsowl.comLocation describes the IP network.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
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.
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
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