VirusTotal
2 / 89
“註冊免實名不限IP、USDT領導品牌|優幣娛樂城 Ub.Bet”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@godaddy.com.
The latest stored availability evidence still shows the domain reachable; 8 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.
The domain ubbet.casino is currently active and resolves to the Amazon‑owned address 52.76.9.100 located in Singapore (AS16509). The site presents a Chinese page title that translates to “Register without real‑name verification, unlimited IP, USDT leading brand – Ub.Bet”, indicating an attempt to market a cryptocurrency gambling service. The hosting stack consists of Apache serving a WordPress installation backed by MySQL, with additional components built on Node.js, Vue.js, and Nuxt.js, suggesting a multi‑framework deployment that may be used to host credential‑stealing forms or malicious scripts. The domain was registered on 21 February 2026 through GoDaddy.com, LLC and uses the standard GoDaddy nameservers ns39.domaincontrol.com and ns40.domaincontrol.com.
A Let’s Encrypt certificate (issued by the E7 intermediate) secures the site, and the HTTP response returns status 200, confirming that the web server is reachable and delivering content. Static analysis on VirusTotal shows that one of ninety‑three security vendors flagged the domain, and the site appears on the PhishDestroy blocklist as well as a single additional security blocklist. Independent scoring by Gridinsoft assigns a trust rating of 0 out of 100, further reinforcing the malicious assessment. No other public blocklists or safe‑browsing services are listed in the supplied data.
Given the combination of a high‑risk cryptocurrency gambling narrative, the presence of a trusted TLS certificate, and the observed detection by at least one vendor, defenders should treat ubbet.casino as a high‑confidence phishing or scam host. Network defenders should block outbound connections to 52.76.9.100 and add ubbet.casino to URL filtering policies. Incident responders should monitor for credential‑theft payloads targeting users who may be lured by promises of USDT gambling, and threat‑intel teams should enrich this indicator with any observed payload hashes or phishing email samples that reference the domain.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/ubbet7777Stored page referenceIoC extraction recorded 2026-07-29 02:38:27 UTC
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
ApacheScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=Apache
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.
ns40.domaincontrol.comLocation describes the IP network.
1b7fbb61386080dc70a65b99489a4046dc400d7d99767c66d9e39695d412c9dfwww.ubbet.casinoSaved 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 ubbet.casino · checked Mar 2, 2026
10 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.
Reported by 1 community member, first seen Jan 24, 2026
PD-20260125-0D2245 Recipient: abuse@godaddy.com Registrar: GoDaddy.com LLC (United States) Policy Violations: Universal TOS + Abuse Policy prohibit fraudulent, abusive, malicious, phishing and illegal activity; grants right to terminate or suspend services Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
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