VirusTotal
5 / 91
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@radix.email.
The latest stored availability evidence still shows the domain reachable; 1 month 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.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | ctbet.website |
malicious | Sinkholed |
On 2026-10-01, ctbet.website returned HTTP status 403 in the recorded HTTP check, and the domain was first observed on 2026-08-24. A separate PhishDestroy internal listing is also recorded for this domain, which gives the page a second, independently dated source to compare against the HTTP response.
The HTTP check on 2026-10-01 recorded status 403 for ctbet.website. The domain was first observed on 2026-08-24, the same date as the PageSpeed check, which recorded a performance score of 76. VirusTotal, checked on 2026-09-04, reported 6 detections across 90 scanners. OTX, checked on 2026-08-28, showed 4 pulses. The registration date is 2026-08-20 with registrar NICENIC INTERNATIONAL GROUP CO., LIMITED, and the SSL scan on 2026-08-24 named Google Trust Services / WE1 as issuer.
The recorded sources describe different things: an HTTP response, a publisher-owned catalogue listing, scanner detections, OTX pulses, and a performance score. Because these observations carry different dates, they should be read as separate snapshots rather than a single combined measurement. The chronology from first observation to the later HTTP check is short, and the records do not establish what the domain served at any point.
Preserve the PhishDestroy internal listing and the VirusTotal record for ctbet.website as separate source records. Compare the HTTP response record with the first-observation record to see whether the recorded status changes over time. Keep the OTX pulses and the performance score as distinct references, and re-check each source independently rather than treating one as confirmation of another.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: cloudflare_challenge: raw=cf_challenge; http=403; via=https_proxy; server=cloudflare
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.
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.
Edge-IP reputation is not attributed to this domain.
javier.ns.cloudflare.commeiling.ns.cloudflare.comLocation describes the IP network.
9a7141bdf7fec6beecabb4ce706f6481bd230ffbba172be2d19b46a261980293Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of ctbet.website · checked Aug 24, 2026
104.21.33.113. 15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
PD-20260824-7AA392 Recipient: abuse@radix.email Registrar: NICENIC International Group Co., Limited (Hong Kong (China)) Policy Violations: “Services may be used only for lawful purposes… fraud, abuse and illegal activity prohibited. Violations may result in immediate suspension.” + dedicated abuse handling and takedown Applicable Laws: Crimes Ordinance Cap.200 (Fraud), Theft Ordinance Cap.210 §16A (fraud by deception), Personal Data (Privacy) Ordinance Cap.486
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive