PhishDestroy identified flareclaim.online as a malicious crypto drainer domain that impersonated the legitimate Flare blockchain platform, which is known for its data-focused blockchain technology. This domain was designed to trick users into connecting their cryptocurrency wallets, after which it would drain funds using a crypto drainer kit. The site's page title, "Flare: The blockchain for data," was a direct copy used to lend credibility and deceive visitors.
Technical analysis reveals several red flags. VirusTotal flagged 6 out of 95 security vendors as malicious, and the domain appeared on three security blocklists. It was registered through HOSTINGER operations, UAB, on May 06, 2026, and resolved to the IP address 198.54.114.243. The SSL certificate was issued by Sectigo Limited via their Sectigo Public Server Authentication CA DV R36, which is commonly used by legitimate sites but here only added a false sense of security. The domain was not listed on Google Safe Browsing at the time of analysis.
Currently, flareclaim.online has been taken offline, neutralizing the immediate threat. However, the risk remains that similar domains may pop up or that users who previously interacted with the site may have already lost funds. PhishDestroy recommends that anyone who visited this site or connected their wallet immediately revoke permissions and transfer assets to a new wallet. Users should always verify domain legitimacy before connecting wallets, as crypto drainers are increasingly sophisticated.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='flareclaim.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
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.
Certificate fingerprint75f45acdf92a938a48735a74ae332b260a8e4e7e585f569a81b479e43f1b90e0Certificate names · 1 SANs
www.flareclaim.online
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-13 01:09:34 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-17 22:12:48 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-17 22:12:48 UTC → 2026-09-30 16:14:55 UTC · 2,514.04hmidpoint estimate ≈ 2026-08-09 07:13:51 UTC · precision very 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.
Google PageSpeed Insights — mobile performance audit of flareclaim.online· checked May 6, 2026
98
Good
Performance
FCP
1.65s
First Contentful Paint
LCP
2.04s
Largest Contentful Paint
CLS
0.015
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.85s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
威胁响应 Pipeline
发现
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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.
(LT)
