VirusTotal
6 / 91 engine detections
Open reportnear-demo.solvador.com is a MetaMask impersonation page detected by PhishDestroy on 2026-09-27. Risk: critical (90/100). Registrar: Nics Telekomunikasyon …. Status: Last known active. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. VirusTotal: 6/91 engines flag it. Do not enter credentials or connect a wallet.
“Paywall — Solvador”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@nicproxy.com.
The latest stored availability evidence still shows the domain reachable; 25 days 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.
6 / 91 engine detections
Open report2 det.
Open reportno community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
near-demo.solvador.com is an impersonation phishing page that presents itself as a Solvador paywall and sits on a subdomain whose "near-demo" label echoes a crypto project name. Its listing on the MetaMask and SEAL blocklists places it in the crypto ecosystem, so the people at risk are wallet holders. PhishDestroy first saw it on 2026-09-27. On 2026-10-19 the site was still alive and its content now redirects to another destination.
The page title, "Paywall — Solvador," shows a gated-access screen, while we classify the site as impersonation phishing. Pages like this borrow a familiar name and a plausible gate, such as unlocking a demo, premium content or early access. The victim is then pushed to pay, enter credentials or connect a wallet to get past the gate. Whatever is handed over goes to the operators. A wallet connection can also be used to request signatures or token approvals that let them move funds later. Because the content now redirects, a visitor may land on a different page from the one originally flagged.
The strongest signal comes from crypto-specific defenses. MetaMask and SEAL both list the domain alongside PhishDestroy, so wallet users may already see warnings. On VirusTotal, 6 of 91 engines flagged it as of 2026-10-03: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and URLQuery. That broad-engine count is modest. A clean result from most scanners should not be read as a sign the page is safe.
The domain was registered on 2026-06-15 through Nics Telekomunikasyon A.S., about 104 days before PhishDestroy detected the subdomain. That gap fits a parent domain set up in advance and later used to host purpose-named subdomains like this one. Traffic is fronted by Cloudflare, with the address geolocated to Canada. This hides the origin server and lets the operators change redirect targets without touching DNS.
If you paid anything through this paywall, contact your card issuer or payment provider right away and dispute the charge. If you typed a password or email login, change it everywhere you reused it and turn on two-factor authentication. If you connected a wallet or signed anything, revoke the approvals granted during that session with a token-approval checker. Move remaining assets to a fresh wallet if you approved unlimited spending or exposed a seed phrase. Defenders should block the full solvador.com domain, not just this subdomain, and watch for sibling subdomains on the same parent.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a0e11e-17f2-71f3-86cf-58eae2083af0 |
|---|---|
| Final url | https://near-demo.solvador.com/premium |
| Status | 402 |
| Redirected | same-domain |
| Redirects | [
{
"to": "https://near-demo.solvador.com/",
"from": "http://near-demo.solvador.com/",
"status": 307
},
{
"to": "https://near-demo.solvador.com/premium",
"from": "https://near-demo.solvador.com/",
"status": 302
}
] |
| Ip | 104.21.12.21 |
| Contacted domains | [
"fonts.gstatic.com",
"fonts.googleapis.com",
"static.cloudflareinsights.com"
] |
| Contacted IP addresses | [
"173.194.114.94",
"172.217.197.95",
"104.16.79.73",
"104.21.12.21"
] |
| Asns | [
"15169",
"13335"
] |
| Countries | [
"US"
] |
| Document hash | 9a91244b5c6be3756ea992a5c4301fc6e333f92a6de686fbfa8a2e7a3800a18a |
| Script hashes | [
"11ca2d6a8962a99fcf98b5a129dc1dedf97581ee4e9488aaa670e4983f470cf6"
] |
| Globals | [
"requestResize",
"__X402_PAYMENT_REQUIRED__",
"__cfBeacon"
] |
| Tls | {
"san": [
"solvador.com",
"*.solvador.com"
],
"cipher": "AES_128_GCM",
"issuer": "WE1",
"subject": "solvador.com",
"protocol": "QUIC",
"valid_to": "2026-11-15T20:52:00Z",
"valid_from": "2026-08-17T19:52:18Z"
} |
| Domain age days | 71 |
| Apex age days | 1320 |
| Tls age days | 40 |
| Tls valid days | 90 |
| Requests | 9 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 71,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "cloudflare",
"content-type": "text/html; charset=utf-8",
"x-powered-by": "Express"
} |
Observed: · Retrieved:
| Uuid | 3e8b1614-fff5-4214-b978-74b9fb376a16 |
|---|---|
| Final url | https://near-demo.solvador.com/premium |
| Status | 402 |
| Redirected | same-domain |
| History | [
{
"url": "https://near-demo.solvador.com/",
"status": 302
},
{
"url": "https://near-demo.solvador.com/premium",
"status": 402
}
] |
| DOM structure hash | f6d3c67b90801e8a02b1b4b1a1ca39ec3f5353ac68847fc8c9cf595a3b6b88f6 |
| Document hash | 9a91244b5c6be3756ea992a5c4301fc6e333f92a6de686fbfa8a2e7a3800a18a |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "near-demo.solvador.com",
"type": "A",
"value": "188.114.97.0"
},
{
"name": "near-demo.solvador.com",
"type": "A",
"value": "188.114.96.0"
},
{
"name": "near-demo.solvador.com",
"type": "AAAA",
"value": "2a06:98c1:3120::"
},
{
"name": "near-demo.solvador.com",
"type": "AAAA",
"value": "2a06:98c1:3121::"
}
] |
| Dnssec valid | true |
| Ip | 188.114.97.0 |
| Registration record | {
"registrar": "Nics Telekomunikasyon A.S.",
"created": "2026-06-15T23:24:03Z",
"updated": "2026-06-24T15:49:55Z",
"expires": "2027-06-15T23:24:03Z",
"nameservers": [
"collins.ns.cloudflare.com",
"logan.ns.cloudflare.com"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 54,
"malicious": 3,
"suspicious": 2,
"undetected": 33
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"URLQuery": "suspicious",
"Gridinsoft": "suspicious",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Categories | {
"alphaMountain.ai": "Phishing (alphaMountain.ai)"
} |
| Registrar | NICS Telekomunikasyon A.S. |
| Created | 2026-06-15T23:24:03Z |
| Expires | 2027-06-15T23:24:03Z |
| Updated | 2026-06-24T15:49:55Z |
| First seen | 2026-07-17T19:04:14Z |
| DNS records | [
{
"ttl": 300,
"type": "A",
"value": "172.67.151.77"
},
{
"ttl": 300,
"type": "A",
"value": "104.21.12.21"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3037::ac43:974d"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3030::6815:c15"
}
] |
| Dns at | 2026-10-03T02:00:31Z |
| Jarm | 27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c |
| Certificate | {
"san": [
"solvador.com",
"*.solvador.com"
],
"issuer": "Google Trust Services / WE1",
"serial": "87ce3d1bc9a2989f0ec15b0f563a9b0d",
"sha256": "74f8e07c1a29a8050c84a048c0ce31b1f3304f56a94033dc6b7ddfe3f82a54e3",
"subject": "solvador.com",
"valid_to": "2026-11-15T20:52:00Z",
"valid_from": "2026-08-17T19:52:18Z"
} |
| Registration record | {
"registrar": "NICS Telekomunikasyon A.S.",
"registrar_iana_id": "1454",
"registrar_url": "https://nicproxy.com/",
"created": "2026-06-15T23:24:03Z",
"updated": "2026-06-24T15:49:55Z",
"expires": "2027-06-15T23:24:03Z",
"status": [
"ok"
],
"nameservers": [
"collins.ns.cloudflare.com",
"logan.ns.cloudflare.com"
],
"dnssec": "signedDelegation"
} |
No. PhishDestroy classifies near-demo.solvador.com as a MetaMask impersonation page (risk: critical, 90/100); it was first detected on 2026-09-27. VirusTotal: 6/91 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on near-demo.solvador.com. 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.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0x833589fcd6edb6e08f4c7c32d4f71b54bda02913Format validated · Domain analysisIoC extraction recorded 2026-09-28 04:00:12 UTC
Last checked
Edge-IP reputation is not attributed to this domain.
collins.ns.cloudflare.comlogan.ns.cloudflare.comLocation describes the IP network.
74f8e07c1a29a8050c84a048c0ce31b1f3304f56a94033dc6b7ddfe3f82a54e3solvador.comSaved 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 near-demo.solvador.com · checked Sep 27, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
3→4
Reachable
No threat flag
View source6/91 engine detections
View sourcePD-20260927-3F944D
near-demo.solvador.com
View sourcePage captured
View source79 stored lookalike domains
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
near-demo.solvador.com
PD-20260927-3F944D Recipient: abuse@nicproxy.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 ↗
near-demo.solvador.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.