Skip to security report
⚠️
This domain has been flagged as malicious
Security engines reporting a detection: 12. 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 2 outgoing records; the latest is dated . The recorded recipient is abuse@domain.me. The latest stored availability evidence still shows the domain reachable; 3 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
3 months
Reports sent
2
Latest case ID
PD-1780429887-spacexbet.me
Current status
HTTP 301 at latest stored check
Domain security and threat intelligence
spacexbet.me favicon

spacexbet[.]me

Threat verdict Critical 96/100 evidence score
Availability Last known active Latest stored reachability observation
VirusTotal detections: 12/89 Last known active
OTX: 2 refs Sep 9, 2026 2 Reports Sent

Evidence Summary

CRITICAL
Score
96/100

PhishDestroy first observed spacexbet.me on Sep 8, 2026. Current evidence score: 96/100 (critical).

One source contains a positive finding: VirusTotal. VirusTotal recorded 12 detections among 89 engines: alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar, ESET, Fortinet, G-Data, Gridinsoft, Kaspersky, Lionic, Sophos, VIPRE on Sep 9, 2026 at 00:58 UTC. Non-positive and contextual checks: AlienVault OTX listed 2 community pulse references (not vendor detections) on Sep 9, 2026 at 00:59 UTC. The separate external-blocklist snapshot contained no matches on Sep 8, 2026 at 22:20 UTC. Google Safe Browsing returned no flag on Sep 9, 2026 at 00:58 UTC. URLScan completed without a malicious verdict (score 0) on Sep 8, 2026 at 23:09 UTC.

HTTP 301 was recorded on Sep 9, 2026 at 01:00 UTC. Registration records for the domain list TLD Registry (.me) as the registrar. At collection time, the hostname resolved to 66.198.225.39. The recorded endpoint location is Edinburg, US. The stored server header is cast-sec. The evidence archive retains 1 visual capture from PhishDestroy; no page title was retained, so the captures preserve the landing-page appearance. TLS metadata lists YE2 as the certificate issuer.

Only one source contains a positive finding; no second positive source is stored. The stored fields do not identify an impersonated brand or victim interaction.

VirusTotal
VirusTotal
12 det.
OTX references
URLScan
URLScan
TLS Certificate
Expired or unverified
Observed status
Last known active 301
PhishDestroy
DestroyList
Listed
Reports Sent
2
Data coverage VirusTotal 12 / 89 URLQuery not checked PhishStats not checked OTX 2 community references CF Radar scan completed URLScan capture stored report URLScan verdict Analysis completed DNS blocks not checked TLS Expired or unverified WHOIS not parsed Screenshot external capture Redirect chain not probed

Threat Response Pipeline

Discovery
Checks
Reports
Availability
13/14
Initial Abuse Report (#1)
Sent to 3 abuse contacts at TLD Registry (.me) with forensic evidence
abuse@trustname.comabuse@domain.mecompliance@icann.org
Jun 2, 2026
ICANN Escalation #2
Escalation #2 sent to 2 recipients including ICANN Compliance — follow-up record after a previous report
abuse@domain.mecompliance@icann.org
Sep 9, 2026
2 Reports Filed
2 report records were stored over 98 days; current observed status: Last known active

Public Blocklist Status

Submitted Evidence Snapshot

Sent
Ledger records
1
Case ID
PD-1780429887-spacexbet.me
Report history 2
  1. Report 1 ⚠️ ESCALATION #1 (0h active): Phishing - spacexbet[.]me
  2. Report 2 ⚠️ ESCALATION #2 (2352h active): Phishing - spacexbet[.]me

Blocklist coverage

stage4.blocklist.scope_plural

stage4.blocklist.scope_plural No match

Stored Capture

Domain Intelligence

Domain
URLScan Verdict Analysis completed score 0 report ↗
Server / ASN cast-sec
IP Reputation abuse score 0/100 0 reports checked Sep 9, 2026
Registrar TLD Registry (.me)
IP Address 66.198.225.39 US
GeoUS Edinburg, US
HTTP Status301 Moved Permanently
Technical detailsDNS, SSL SANs, timestamps
First DetectedSep 9, 2026
Favicon Hash
Case ID
TLS Certificate
Expired or unverified · Issued by YE2
Abuse Report History · 2 stored reports over 99 days · click to expand
This timeline is built from stored outgoing report records. It documents timestamps and listed recipients, but does not by itself prove delivery, acknowledgement, or recipient action.
2 abuse reports filed over 98 days — latest observed status: Last known active
The records name TLD Registry (.me) as a recipient or subject. ICANN Compliance appears in the recipient field for at least one record.
2
reports
98
days
ICANN CC
  1. Report #1 ICANN CC Jun 2, 2026 · 22:51 UTC
    ESCALATION #1 (0h active): Phishing - spacexbet[.]me
    abuse@trustname.com abuse@domain.me compliance@icann.org
  2. Report #2 ICANN CC 2352h still active Sep 9, 2026 · 00:52 UTC
    ESCALATION #2 (2352h active): Phishing - spacexbet[.]me
    abuse@domain.me compliance@icann.org
Record scope: the timeline documents outgoing records stored by PhishDestroy. Delivery, acknowledgement, and subsequent action require separate recipient or infrastructure evidence.
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 / 89 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 12 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
ESET
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Sophos
VIPRE

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-1780429887-spacexbet.me Recipient: abuse@domain.me
URLScan evidence VirusTotal evidence

Were You Affected by This Site?

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 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/spacexbet.me"
  title="PhishDestroy threat report for spacexbet.me"
  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>