https://zodiaccasino1.ca/en-ca/
104.21.66.180 · Cloudflare, Inc.
Toronto, Canada
966 days
200 · 19.6s
Valid· E8, Let's Encrypt, US
COMPLETED
Linked Phishing Report
This scan is attached to a vendor submission report
Brand
zodiaccasino1.ca
Vendors
27/31
Status
partial
No KB/IOK detections were recorded for this scan.
gaming | technology · 6/3/2026
The page at zodiaccasino1.ca/en-ca/ presents a casino-themed domain that appears to be proxied behind Cloudflare. The screenshot shows a generic “This site can’t be reached” error page, but scan data reveals SPA-like behavior with a dynamic POST to /cdn-cgi/rum? and a beacon script loaded from Cloudflare, plus an IPIP API call. There is no static login form in HTML, yet the SPA pattern suggests credential collection could be rendered client-side. The domain age is older than two years with a recent DV SSL certificate from Let’s Encrypt, but the SSL certificate is very new (valid for a short period). Given the visual evidence in the screenshot and the SPA indicators, there is potential impersonation risk if branding on the page mimics a legitimate casino site, but the captured evidence primarily shows a misconfigured or blocked page rather than definitive credential harvesting. The data does not conclusively prove phishing; therefore, the判断 remains inconclusive for credential theft, with a warning to monitor for impersonation indicators.
Capture
Stages: 2
Canonical: Settled Render
Changed: No
Credential Signals
Forms: 0
Password fields: 0
Late-stage login UI: No
Resource Signals
Resources: 4
Hosts: 2
Domains: 2
No suspicious indicators identified
The site is hosted behind Cloudflare and uses a recently issued Let's Encrypt certificate. The visual evidence in the screenshot indicates a potential impersonation of a casino brand, given the domain name and URL structure, but the HTML static content shows no login form. The dynamic SPA behavior and the beacon script imply potential credential collection capabilities, but there is no explicit form or API endpoint observed in static HTML. The overall signals suggest possible phishing risk due to branding concerns and SPA-based credential capture risk; continue with monitoring and further verification of the page rendering and form activity. The presence of a POST to /cdn-cgi/rum? and the external beacon script strengthens suspicion of data collection behavior.
Monitor