Analysis of premiumcore.online indicates a confirmed crypto scam domain operating as a fraudulent blockchain-based online casino. The domain was registered on February 21, 2026, through NameCheap, Inc., and currently resolves to IP address 188.114.96.3, hosted on Cloudflare's network (AS13335). Infrastructure analysis reveals Cloudflare nameservers (adi.ns.cloudflare.com and steven.ns.cloudflare.com) and an absence of SSL certification, increasing exposure to interception risks. The page title, 'Premiumcore: Most Popular Online Crypto Casino Based on Blockchain,' directly signals its fraudulent intent, aligning with the 'Gambler Scam' phishing kit classification.
Security vendor detections confirm elevated risk: 13 of 93 engines on VirusTotal flagged the domain at the time of assessment. The domain appears on one security blocklist and is blocked by PhishDestroy. Gridinsoft assigns a trust score of 0/100, reinforcing its malicious classification.
While the domain is currently offline, defenders should treat any reactivation as high-risk. Network administrators are advised to block the domain and its resolving IP (188.114.96.3) at the perimeter, monitor for related domains registered through NameCheap with similar naming patterns, and alert users to the specific threat of crypto-based gambling scams. No evidence suggests legitimate user traffic or business operations associated with this domain.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='premiumcore.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
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:10:48 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-15 16:44:37 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-15 16:44:37 UTC → 2026-09-30 16:14:55 UTC · 2,567.51hmidpoint estimate ≈ 2026-08-08 04:29:46 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.
10 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.
(US)
