VirusTotal
checked — no detections recorded
“betbeyci.com | 520: Web server is returning an unknown error”
On 2026-10-08 betbeyci.com returned HTTP status 520, indicating a server-side issue at that time. The domain’s server header was recorded as 'cloudflare' during the same observation.
VirusTotal detected the domain on 2026-10-07 with 0 detections out of 92 scanners. OTX recorded 2 pulses on 2026-10-08. A urlscan report was available on 2026-10-05, and the domain was listed in the PhishDestroy internal catalogue.
These dated records document technical responses and third-party assessments of betbeyci.com across different services. The HTTP 520 response and Cloudflare header indicate a specific server behavior at the time of measurement. VirusTotal and OTX provide independent security scanning results, while urlscan offers a page capture record.
Preserve the VirusTotal scan, OTX pulses, urlscan report, and PhishDestroy listing for future reference. Use these dated records to compare any new observations or changes related to betbeyci.com.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/BetbeyresmiStored page referenceIoC extraction recorded 2026-10-08 04:01:21 UTC
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='betbeyci.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
Saved 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 betbeyci.com · checked Oct 7, 2026
188.114.96.1. 9 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