This domain, coresystemsjs.online, is flagged for brand impersonation targeting the online crypto casino and gambling sector. Analysis indicates the infrastructure mimics legitimate blockchain-based gambling platforms, presenting itself under the page title 'Coresystemsjs: Most Popular Online Crypto Casino Based on Blockchain.' The threat type aligns with fraudulent schemes designed to deceive users into engaging with counterfeit services, potentially leading to financial loss or credential theft. Infrastructure analysis reveals the following technical indicators: the domain was registered through NameCheap, Inc. on March 07, 2026, and resolves to the IP address 188.114.96.3. VirusTotal detection metrics show 12 out of 95 security vendors flagging the domain as malicious. The domain appears on one security blocklist and was actively blocked by at least one threat intelligence feed. No evidence of Google Safe Browsing (GSB) classification was observed at the time of analysis. The domain is currently offline, reducing immediate exposure risk. However, historical infrastructure and registration patterns suggest potential for re-emergence under similar or altered domains. Users and organizations are advised to monitor for related indicators of compromise, including the IP address and registrar details. Proactive measures, such as updating blocklists and educating users about brand impersonation tactics in the crypto gambling sector, are recommended to mitigate residual risk.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='coresystemsjs.online', port=80): Max retries exceeded with url: / (Caused by NewConnection
DOM Analysisanalyzed 2026年7月29日score 73/1001 brand signal
Submitted URLhttps://coresystemsjs.online/
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.
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:17 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-03-23 22:18:27 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-03-23 22:18:27 UTC → 2026-09-30 16:14:55 UTC · 4,577.94hmidpoint estimate ≈ 2026-06-27 07:16:41 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.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
VirusTotal Detections Update2026-06-26 15:02:58 UTC
VirusTotal scanner detections updated from 8 to 12. Added scanner alerts: BitDefender, Chong Lua Dao, Forcepoint ThreatSeeker, Lionic.
威胁响应 Pipeline
发现
Analysis
Monitoring
13 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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
(US)
