Skip to security report
Domain security and threat intelligence
jerry.casino favicon

jerry.casino

“Jerry: Most Popular Online Crypto Casino Based on Blockchain”

Registrar
Spaceship
Resolved IP
188.114.96.3
Threat verdict Critical
Availability Reachable · access restricted Reachable response; page content was not verified Observed
Source: HTTP probe
VirusTotal detections: 12/91 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 URLQuery threat systems: 4 alerts Brand impersonation: Genericcrypto Last known active
OTX: 1 ref Dec 25, 2025 Genericcrypto 14 Reports Sent CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 12. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . It contains 14 outgoing records; the latest is dated . The recorded recipient is abuse@spaceship.com. The latest stored availability evidence still shows the domain reachable; 9 months has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
9 months
Reports sent
14
Latest case ID
PD-1767733771-jerry.casino
Current status
HTTP 403 at latest stored check
Spamhaus DBL
DBL_PHISH
VirusTotal
VirusTotal
12 det.
URLQuery
URLQuery
4 threat alerts
OTX references
URLScan
URLScan
TLS Certificate
Expired or unverified -158d
Observed status
Reachable · access restricted 403
PhishDestroy
DestroyList
Listed
Reports Sent
14

Source evidence

8 sources

VirusTotal

12 / 91

Report

URLQuery

4 threat-system alerts

Report

URLScan verdict

malicious

Report

Spamhaus DBL

DBL_PHISH

OTX

1 community reference

Report

CF Radar

provider verdict: clean

Report

URLScan capture

stored report

Stored URLScan capture preview
Report

Google Safe Browsing

Checked; no threat flag recorded

Report
Network Security Intelligence
Threat Detection Systems 4 alerts
Detection System Indicator Verdict Alert
OpenDNS jerry.casino phishing Phishing Block
Hagezi Threat Feed jerry.casino malicious Sinkholed
DNS0 Zero jerry.casino malicious Sinkholed
DNS4EU jerry.casino malicious Sinkholed

Evidence Summary

Critical
VirusTotal
12/91
OTX
1 community ref
URLScan
Stored capture

The domain jerry.casino was flagged on 23 July 2026 as a high‑risk generic phishing site targeting cryptocurrency users. Infrastructure analysis shows the domain is registered through Spaceship, Inc. and resolves to the Cloudflare‑owned address 188.114.96.3, which belongs to ASN 13335 (Cloudflare, Inc.) and is geolocated in the United States. The authoritative name servers are elsa.ns.cloudflare.com and clint.ns.cloudflare.com, indicating the use of Cloudflare’s DNS service. The site presents an SSL certificate issued by Google Trust Services under the WE1 trust chain, confirming that TLS termination is performed by Cloudflare’s edge infrastructure.

HTTP probing returned a 403 status code, suggesting that the content is currently inaccessible, and the domain is listed as offline in the source feed. The page title that was captured before takedown reads “Jerry: Most Popular Online Crypto Casino Based on Blockchain,” which aligns with the reported scam type of a crypto‑related casino phishing campaign. The campaign has been associated with the publicly known “Gambler Scam” phishing kit.

Threat intelligence sources provide additional corroboration: AlienVault OTX includes the domain in one pulse, and three independent blocklists have added it to their deny lists. It is also blocked by the PhishDestroy, MetaMask, and SEAL filtering services. VirusTotal analysis shows that 14 of 93 scanned security vendors flagged the domain, reinforcing the malicious classification.

Given the convergence of registrar, hosting, TLS, and multiple independent detections, defenders should treat jerry.casino as a confirmed malicious actor. Recommended mitigations include adding the domain to network‑level deny lists, ensuring web‑proxy and DNS filtering solutions block it, and monitoring for any resurrection attempts. At present, no further content inspection is possible because the site returns HTTP 403 and is offline, leaving the exact phishing page layout unknown.

Detection-evasion analysis

Cloaking suspected: scanner and visitor titles differ

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan
Server header seen by scanner
cloudflare

Scanner note: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial

Provider response during scan: cloudflare_phishing_interstitial

Title shown to the security scannerSuspected Phishing | Cloudflare
Title shown to a browser visitorJerry: Most Popular Online Crypto Casino Based on Blockchain
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting

Stored Capture · 3 captures

Page Title
Jerry: Most Popular Online Crypto Casino Based on Blockchain
Impersonates
Genericcrypto
TLS Certificate
Hostname coverage not recorded · Issued by Google Trust Services / WE1

Domain details

Domain
URLScan Verdict Malicious score 100 Phishing report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar Spaceship US(US)
HTTP Status403 Forbidden
Elapsed Since First Report 66 days
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Reachable · access restricted.
Minimum notice count 14 is the number of stored outgoing report records for this domain. It does not by itself prove acknowledgement or action by a recipient.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
ICANN RAA §3.18 The history below lists stored escalation records and timestamps. It does not by itself establish receipt, acknowledgement, compliance, or enforcement by any recipient.
Technical detailsProvenance & timestamps
First DetectedDec 25, 2025
DOM Analysisanalyzed Jul 10, 2026score 90/1001 brand signal
Favicon Hash
Case ID
ICANN OVERSIGHT

Accreditation and RAA context

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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 1

  • clint.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-02-06 17:05:38
Valid until
2026-05-07 18:04:13
Hostname coverage
Hostname coverage not recorded
Validity
Stored certificate expired
Collection time
2026-03-12 01:32:35 UTC
Collection source
PhishDestroy collector
Certificate fingerprintb7f7bd283dfc4156296a37d6021cf9a3a296f853cb0e966f37181b29f41d0be5

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 188.114.96.3rapiddns.io

Latest Classified Outcome 2026-10-11 01:18:02 UTC

Primary outcome Provider block observed reason: Cloudflare anti-phishing block 95% confidence
Attribution Cloudflare mechanism: Phishing Interstitial source: Current Http Probe
Evidence layers Availability: Provider blocked Content: Provider blocked DNS: Resolved Registration: Unknown
Latest HTTP observation Provider block observed Cloudflare anti-phishing block Cloudflare Phishing Interstitial 95% provider marker verified 2026-10-11 01:18:02 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-09-15 22:18:00 UTC current episode first observed: 2026-10-01 01:43:39 UTC observed RIP window: 2026-09-15 22:18:00 UTC → 2026-10-01 01:43:39 UTC · 363.43h midpoint estimate ≈ 2026-09-23 12:00:49 UTC · precision 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.
Casino / Gambling License Verification
Unverified gambling license
This domain markets casino/gambling services. Scam casinos routinely display fake Curaçao, MGA, or Kahnawake license badges that don’t exist in the real registries. Always verify the license number against the official regulator database before depositing. If the site shows a seal but no clickable registry link — or the linked registry page doesn’t exist — treat it as fraudulent.
Curaçao eGaming (official) Malta Gaming Authority UK Gambling Commission PA Gaming Control Kahnawake Gaming Gibraltar Gambling
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

12 / 91 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 13 detections
ADMINUSLabs
alphaMountain.ai
BitDefender
Chong Lua Dao
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Sophos

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Abuse Report Escalation History · 14 reports over 87 days · click to expand
PhishDestroy does not flood registrars. Follow-up reports are sent only when one of the following is true: a user-initiated re-report was submitted via our public form, our monitoring detected the domain resurfacing in a search engine result or third-party feed, or our live-checker confirmed the domain remains technically active and still exhibits fraudulent behaviour. Each escalation below represents an independent trigger — not automated noise.
14 abuse reports filed over 252 days — domain still online
Spaceship, Inc. was notified 14 times and has not acted on the reports. ICANN Compliance was CC’d on at least one escalation — receipt of each complaint is therefore on the record.
14
reports
252
days
ICANN CC
  1. Report #1 Escalation 599h still active Jan 31, 2026 · 20:11 UTC
    ESCALATION #6 (599h active): Phishing - jerry[.]casino
    support@spaceship.com
  2. Report #2 Escalation 657h still active Feb 3, 2026 · 06:31 UTC
    ESCALATION #7 (657h active): Phishing - jerry[.]casino
    support@spaceship.com
  3. Report #3 Escalation 712h still active Feb 5, 2026 · 13:36 UTC
    ESCALATION #8 (712h active): Phishing - jerry[.]casino
    support@spaceship.com
  4. Report #4 Escalation 789h still active Feb 8, 2026 · 18:27 UTC
    ESCALATION #9 (789h active): Phishing - jerry[.]casino
    support@spaceship.com
  5. Report #5 ICANN CC 937h still active Feb 14, 2026 · 23:00 UTC
    ESCALATION #10 (937h active): Phishing - jerry[.]casino
    support@spaceship.com abuse@identitydigital.com compliance@icann.org
  6. Report #6 Escalation Feb 26, 2026 · 18:54 UTC
    Phishing Abuse Report: jerry[.]casino
    abuse@spaceship.com
  7. Report #7 ICANN CC 103h still active Mar 3, 2026 · 02:52 UTC
    ESCALATION #2 (103h active): Phishing - jerry[.]casino
    abuse@spaceship.com abuse@identitydigital.com compliance@icann.org
  8. Report #8 ICANN CC 140h still active Mar 4, 2026 · 15:09 UTC
    ESCALATION #3 (140h active): Phishing - jerry[.]casino
    abuse@spaceship.com abuse@identitydigital.com compliance@icann.org
  9. Report #9 ICANN CC 184h still active Mar 6, 2026 · 11:32 UTC
    ESCALATION #4 (184h active): Phishing - jerry[.]casino
    abuse@spaceship.com abuse@identitydigital.com compliance@icann.org
  10. Report #5 ICANN CC 891h still active Apr 5, 2026 · 01:32 UTC
    ESCALATION #5 (891h active): Phishing - jerry[.]casino
    abuse@spaceship.com abuse@identitydigital.com compliance@icann.org
  11. Report #6 ICANN CC 1265h still active Apr 20, 2026 · 15:09 UTC
    ESCALATION #6 (1265h active): Phishing - jerry[.]casino
    abuse@spaceship.com abuse@identitydigital.com compliance@icann.org
  12. Report #7 ICANN CC 1318h still active Apr 22, 2026 · 20:17 UTC
    ESCALATION #7 (1318h active): Phishing - jerry[.]casino
    abuse@spaceship.com abuse@identitydigital.com compliance@icann.org
  13. Report #8 ICANN CC 1411h still active Apr 26, 2026 · 17:14 UTC
    ESCALATION #8 (1411h active): Phishing - jerry[.]casino
    abuse@spaceship.com abuse@identitydigital.com compliance@icann.org
  14. Report #9 ICANN CC 1460h still active Apr 28, 2026 · 18:15 UTC
    ESCALATION #9 (1460h active): Phishing - jerry[.]casino
    abuse@spaceship.com abuse@identitydigital.com compliance@icann.org
ICANN RAA §3.18 requires accredited registrars to publish an abuse point-of-contact and take reasonable and prompt steps in response to reports of illegal activity. The timeline above documents delivered reports — registrar acknowledgement and takedown timing are independently verifiable via the archived email threads on request.

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
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.
  1. Domain Status Transition 2026-07-26 22:33:59 UTC
    Domain state transitioned from dead to alive.
  2. Cloudflare Radar Scan 2026-03-07 10:24:20 UTC
    Cloudflare Radar scan registered: View Radar report.
  3. Domain Status Transition 2026-03-01 04:32:54 UTC
    Domain state transitioned from alive to dead.

Threat Response Pipeline

Discovery
Analysis
Notifications
Monitoring

31 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
jerry.casino detected and queued for full analysis
Dec 25, 2025
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
Sep 13, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Feb 25, 2026
URLScan Verdict
URLScan returned a malicious verdict · score 100
Jul 29, 2026
Cloudflare Radar Report
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 Wayback Machine — historical evidence archived
Mar 14, 2026
VirusTotal
12/91 recorded on VirusTotal
Aug 28, 2026
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 11, 2026
OTX Community References
1 community publication reference on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Mar 1, 2026
Brand Impersonation
Impersonation of Genericcrypto
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Feb 25, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 11, 2026
Site Came Back Online
Domain is responding again — monitoring resumed
Jul 27, 2026
Cloudflare Radar Scan
Scanned with Cloudflare Radar; network analysis completed.
Mar 7, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 666); the cause was not independently established.
Mar 1, 2026
Initial Abuse Report (#1)
Sent to 1 abuse contact at Spaceship, Inc. with forensic evidence
support@spaceship.com
Jan 31, 2026
Follow-up Report #2
Escalation #2 sent to 1 recipient — follow-up record after a previous report
support@spaceship.com
Feb 3, 2026
Follow-up Report #3
Escalation #3 sent to 1 recipient — follow-up record after multiple previous reports
support@spaceship.com
Feb 5, 2026
Follow-up Report #4
Escalation #4 sent to 1 recipient — follow-up record after multiple previous reports
support@spaceship.com
Feb 8, 2026
ICANN Escalation #5
Escalation #5 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
support@spaceship.comabuse@identitydigital.comcompliance@icann.org
Feb 14, 2026
Follow-up Report #6
Escalation #6 sent to 1 recipient — follow-up record after multiple previous reports
abuse@spaceship.com
Feb 26, 2026
ICANN Escalation #7
Escalation #7 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse@spaceship.comabuse@identitydigital.comcompliance@icann.org
Mar 3, 2026
ICANN Escalation #8
Escalation #8 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse@spaceship.comabuse@identitydigital.comcompliance@icann.org
Mar 4, 2026
ICANN Escalation #9
Escalation #9 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse@spaceship.comabuse@identitydigital.comcompliance@icann.org
Mar 6, 2026
ICANN Escalation #5
Escalation #5 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse@spaceship.comabuse@identitydigital.comcompliance@icann.org
Apr 5, 2026
ICANN Escalation #6
Escalation #6 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse@spaceship.comabuse@identitydigital.comcompliance@icann.org
Apr 20, 2026
ICANN Escalation #7
Escalation #7 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse@spaceship.comabuse@identitydigital.comcompliance@icann.org
Apr 22, 2026
ICANN Escalation #8
Escalation #8 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse@spaceship.comabuse@identitydigital.comcompliance@icann.org
Apr 26, 2026
ICANN Escalation #9
Escalation #9 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse@spaceship.comabuse@identitydigital.comcompliance@icann.org
Apr 28, 2026
14 Reports Filed
14 report records were stored over 252 days; current observed status: Reachable · access restricted
DestroyList Published
Dec 25, 2025
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report

Public scans, evidence and abuse channels

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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

Public Blocklist Status

Community intelligence

1 community report

CategoryOTHER

Brand abuse: scam service, fake offer, promotion scam, gambling, impersonating PancakeSwap

Community reports

Reported by 1 community member, first seen Dec 6, 2025

Stored reports
1
Unique reported URLs
1
Accepted1

Evidence & External Reports

Third-Party Detection — ChainAbuse
1 report filed for jerry.casino · category: Other · source checked
Flagged by automated brand-abuse detection on Jul 20, 2026 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-1767733771-jerry.casino Recipient: abuse@spaceship.com
URLScan evidence VirusTotal evidence URLQuery evidence
PDF notice generated
Deep Analysis

Were You Affected by This Site?

6 evidence signal groups linked 14 reports recorded Reachable · access restricted
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Europol
Find the official reporting channel for your EU country
National police directory
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/jerry.casino"
  title="PhishDestroy threat report for jerry.casino"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>