solmeme.online was registered on August 17 2025 through NameCheap, Inc. and resolves to the IP address 18.208.88.157, which belongs to the Amazon.com, Inc. network (AS14618) located in the United States. The domain is served over HTTPS using a Let’s Encrypt certificate (issuer E8) and returns HTTP status 200 for the root URL. DNS resolution is provided by four nsone.net name servers (dns1.p05.nsone.net through dns4.p05.nsone.net). The web application is built with Vue.js and is hosted on Netlify, with HTTP Strict Transport Security (HSTS) enabled. The page title presented by the site reads “solmeme.online - Create Solana Tokens & Memecoins Instantly”, explicitly referencing the Solana brand and positioning the service as a token‑creation platform. No additional content has been captured, so visual or functional details remain unknown. Analysis classifies the site as a cryptocurrency‑focused brand‑impersonation campaign targeting users of the Solana ecosystem. The presence of the Solana brand in the title, combined with the promise of instant token creation, aligns with known crypto‑scam patterns that lure investors into fraudulent token sales or credential harvesting. The domain is listed on one public blocklist, has a Gridinsoft trust score of 0 / 100, and one of ninety‑five VirusTotal scanners flagged it as malicious, reinforcing the high‑risk assessment. Defenders should block the domain at network perimeter and add the associated IP address 18.208.88.157 to deny lists. Email filters should be updated to flag any messages containing the domain or referencing Solana token creation. Continuous monitoring of DNS queries for the nsone.net name servers can reveal additional infrastructure reuse. Organizations with Solana‑related assets should educate users about unsolicited token‑generation services and enforce multi‑factor authentication for wallet access.
Extracted from stored page analysis
Observed indicators
0 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
DOM Analysisanalyzed 2026年3月11日score 78/1001 brand signal
IoC Extractionscanned 2026年7月29日0 wallet · 1 Telegram IoC
Submitted URLhttp://solmeme.online/
Favicon Hash
ICANN OVERSIGHT
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 01:14:53 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-15 22:18:10 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-15 22:18:10 UTC → 2026-09-30 16:14:55 UTC · 353.95hmidpoint estimate ≈ 2026-09-23 07:16:32 UTC · precision low · basis bounded
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.
使用技術 · 3 identified
V
Vue.js
JavaScript frameworks
Progressive JavaScript framework for building user interfaces.
N
Netlify
PaaSCDN
Platform for deploying and hosting modern web applications.
H
HSTS
セキュリティ
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
Google PageSpeed Insights — mobile performance audit of solmeme.online· checked Mar 2, 2026
91
Good
Performance
FCP
2.6s
First Contentful Paint
LCP
2.6s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
86ms
Total Blocking Time
SI
4.03s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
353.95
Estimate basis
Bounded by observations
Estimate precision
Low
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='solmeme.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
solmeme.online
保存済みの結果
Cloaked / Filtered
Stored observation history15
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
(US)
