Analysis of the domain sol-incineralor.digital shows that it was used to impersonate Discord in a wallet/seed phishing campaign. The site was registered through Cloudflare, Inc., and its DNS resolves to IP 104.21.20.27, which belongs to Cloudflare’s AS13335 network located in the United States. The domain employed Cloudflare’s edge services, including HTTP/3, and presented a valid SSL certificate issued by Google Trust Services under the WE1 intermediate. The page title returned by the server was “Sol Incinerator,” which does not directly reference the targeted brand, indicating that the visual content was not captured during analysis.
HTTP responses returned a 523 status, suggesting a Cloudflare origin error, and the domain is currently taken offline. Security telemetry indicates that the site was blocked by PhishDestroy and appears on one external blocklist. Reputation services gave the domain a Gridinsoft trust score of 0 / 100, and two of ninety‑five VirusTotal scanners flagged it as malicious. Nameserver records list george.ns.cloudflare.com and ophelia.ns.cloudflare.com.
The evidence confirms a targeted Discord wallet/seed phishing operation, but the exact delivery vector (email, social media, or direct link) and the content of the phishing page remain unknown because the site is no longer reachable. Defenders should add sol-incineralor.digital and its resolving IP 104.21.20.27 to network deny lists, monitor for new Cloudflare‑registered domains that mimic Discord branding, and enforce strict verification of any Discord credential or seed requests. Continuous observation of Cloudflare‑associated blocklists and rapid sharing of indicators of compromise with threat‑share platforms are recommended to limit the lifespan of similar impersonation campaigns.
DOM Analysisanalyzed 2026年4月23日score 71/1002 brand signals
Submitted URLhttp://sol-incineralor.digital/
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-21 01:16:03 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.
使用技術 · 2 identified
Cloudflare
CDN
Web infrastructure and security company providing CDN, DDoS mitigation, and DNS services.
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='sol-incineralor.digital', port=80): Max retries exceeded with url: / (Caused by NewConnect
sol-incineralor.digital
保存済みの結果
到達不能
Stored observation history14
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)
