Skip to main content
Sandfish

Jackpot City South Africa | Official Licensed Site | Play in ZAR

https://www.jackpotcity.co.za/

Group73113787-86a5-4b8e-8346-e9f55e49a08csubmitted urlMember 1

Case summary

The target, observed result, and important findings.

Rules engine

AI review

Not available
Processing statusEvidence coverage

Findings

2 signalsHighest severityInformational

Analyzed page

Language
Detecting...

Infrastructure

Domain registration
jackpotcity.co.zaunsupported
Hosting
Loading...

Capture activity

Interaction
11 actions · 2 submissions · stopped: repeated state · download stage: click limit
  1. 1. clicksucceededLogin [dispatched]
  2. 2. fillsucceededtel | username | username | Enter Mobile Number
  3. 3. fillsucceededpassword | password | password |
  4. 4. submitsucceededLogin [dispatched]
  5. 5. fillsucceededtel | username | username |
  6. 6. fillsucceededpassword | password | password |
  7. 7. submitsucceededLogin [dispatched]
  8. 8. validationobservedValidation (ariaInvalid) | tel | username | username
  9. 9. validationobservedValidation (ariaInvalid) | password | password | password
  10. 10. download control presssucceededDownload for App Gallery [dispatched]
  11. 11. download control presssucceededDownload for Android [dispatched]

A successful press does not prove that a file arrived. Check the Payloads tab for recorded files.

Kit source work

Loading related source work…

Discover or upload kit source

Analysis metadata

How and when the analysis ran.

Input kind
url
Execution kind
capture
Duration
2.5m
Navigation
3 navigations
Engine version
0.4.2
Created
2026-11-18 00:01:15Z
Started
2026-11-18 00:01:20Z
Finished
2026-11-18 00:03:52Z
Archive
12.2 MB
Favicon source
html_link / favicon-v7
Analysis ID
5f87447f-4f83...

Document-source diagnostics

These records identify rejected document reads. A current epoch does not prove that a replacement read succeeded. Later success does not erase an earlier evidence limit.

No rejected document reads were recorded.

Browser-observed navigation status

The browser status can differ from the normalized origin response, including during a proxy failure. Inspect the recorded document request for origin response evidence.

NavigationBrowser-observed HTTP statusRecorded requests
0307Inspect navigation 0 requests
1301Inspect navigation 1 requests
2200Inspect navigation 2 requests
Showing 0–0 of 0

Signals by severity

Detected findings grouped by risk

Request activity

Network requests grouped by resource type

Behavior

Recorded actions grouped by type

Network contacts

Requests to the most active hosts

Request ownership

First-party and third-party requests

Response MIME types

Network responses grouped by MIME type