VirusTotal
2 / 92
The domain betko.live returned an HTTP 301 status code on 2026-10-07, according to a recorded check. On the same date, it was also listed in the PhishDestroy internal catalogue.
VirusTotal reported 2 detections out of 92 scanners for betko.live on 2026-10-04. OTX referenced 3 pulses for this domain as of 2026-10-07. The domain was registered through Dynadot Inc on 2026-09-19, and a Let's Encrypt / YE2 SSL certificate was scanned on 2026-10-07.
These records provide a snapshot of betko.live's presence across several monitoring and security sources. The HTTP 301 response documents a redirection at the time of the check, while VirusTotal and OTX show that the domain has drawn attention from multiple security communities.
For betko.live, retain the HTTP response record and compare it with VirusTotal and OTX observations for future reference. Keep the PhishDestroy internal listing and VirusTotal detection results available for ongoing monitoring and review.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://betko.live/; 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.
Location describes the IP network.
a597088d6ba502c8360dcf1266381e098d886e7affe0c4cd460af82a3b81a796Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
188.114.96.1. 8 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.
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