Security engines reporting a detection: 6. 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 .
The recorded recipient is abuse@publicdomainregistry.com.
The latest stored availability evidence still shows the domain reachable; 7 days 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.
coinex.bet was observed on 2026-10-06 with a PageSpeed performance score of 72 and a listing in the PhishDestroy internal catalogue. The domain was also checked by OTX and VirusTotal, providing additional insights into its recorded activity.
Recorded Evidence
VirusTotal checked coinex.bet on 2026-10-01, reporting 6 detections out of 92 scanners. OTX pulses included coinex.bet as of 2026-10-06. The domain was registered with PDR Ltd. d/b/a PublicDomainRegistry.com on 2026-04-23, and its SSL certificate was issued by Let's Encrypt / YE1, scanned on 2026-10-07. PageSpeed measured a performance score of 72 on 2026-10-06.
Interpretation
The evidence from VirusTotal, OTX, and PageSpeed provides a multi-faceted view of coinex.bet, with each source offering distinct information about its observed status and technical performance. The inclusion in the PhishDestroy internal listing and the dated SSL scan further expand the scope of available records for this domain.
Recommended Actions
To evaluate coinex.bet, review the VirusTotal detections and OTX pulse records for comparison with future scans. Preserve the PageSpeed performance score and PhishDestroy internal listing as reference points. Use these documented observations to inform ongoing monitoring and assessment of coinex.bet.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo 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
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='coinex.bet', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SOC
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 22:07:34 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-06 23:14:49 UTClast content: 2026-10-06 23:14:49 UTCcurrent episode first observed: 2026-10-08 20:20:32 UTCobserved RIP window: 2026-10-06 23:14:49 UTC → 2026-10-08 20:20:32 UTC · 45.10hmidpoint estimate ≈ 2026-10-07 21:47:40 UTC · precision medium · 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.
Last analyzed Previous stored snapshot: 6 detections
alphaMountain.ai
BitDefender
ESET
Fortinet
G-Data
LevelBlue
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of coinex.bet· checked Oct 6, 2026
72
Needs Work
Performance
FCP
4.52s
First Contentful Paint
LCP
4.56s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
16ms
Total Blocking Time
SI
4.56s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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.
Threat First Observed2026-10-06 21:23:18 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 46.29.26.38.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
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.
6 evidence signal groups linked1 reports recordedUnverified
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.
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 →
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
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · coinex.bet
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
(US)
