The site syncflrslinks.online is a fraudulent cryptocurrency platform that impersonated the Ethereum brand. Its page title, "Flare - EVM Hub for Web 3.0," was used to present a fake Web3 infrastructure service designed to deceive users into connecting their cryptocurrency wallets or providing credentials. The primary threat is credential theft or cryptocurrency asset loss through a phishing scheme masquerading as a legitimate blockchain hub.
Technical analysis confirms the site is malicious. VirusTotal flagged it with 11 detections out of 95 security vendors. It was specifically flagged by alphaMountain.ai, BitDefender, CyRadar, Fortinet, and G-Data, and appeared on 5 blocklists. The domain was registered on 2026-02-21, hosted at IP address 195.20.18.201, which is associated with AS48753 AVA HOST SRL in Moldova (MD). The site used an R11 SSL certificate.
The domain is currently offline and down. Its DOM risk score is 80, indicating a high-risk profile. Based on the provided data, the threat is neutralized while the site is inactive, but the domain remains a potential risk if reactivated.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='syncflrslinks.online', port=80): Max retries exceeded with url: / (Caused by NewConnection
DOM Analysisanalyzed 2026年3月24日score 80/1001 brand signal
页面标题
Flare - EVM Hub for Web 3.0
Impersonates
Ethereum
TLS 证书
Hostname coverage not recorded·
颁发者 R11
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
195.20.18.201
Network ASN
AS48753
Organization
AVA HOST SRL
Observed location
Chisinau, MD
Server header
nginx
Location describes the IP network.
TLS 证书
Issuer
R11
Hostname coverage
Hostname coverage not recorded
Collection source
PhishDestroy collector
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:11:29 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-04-08 03:16:41 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-08 03:16:41 UTC → 2026-09-30 16:14:55 UTC · 4,212.97hmidpoint estimate ≈ 2026-07-04 21:45:48 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.
11 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.
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.
