VirusTotal
4 / 92
betovia.top was observed on 2026-10-09 with a recorded presence in the PhishDestroy internal listing and a VirusTotal scan showing 0 detections out of 92 scanners. The domain was registered recently, on 2026-10-06.
PhishDestroy internally listed betovia.top as of 2026-10-09. VirusTotal checked the domain on 2026-10-09 and reported 0 detections from 92 scanners. OTX recorded two pulses for betovia.top on 2026-10-09. The domain was registered with Openprovider on 2026-10-06.
The evidence for betovia.top spans multiple sources, each providing a distinct observation on 2026-10-09. The PhishDestroy internal listing and OTX pulses indicate that the domain has been noted by security monitoring platforms. VirusTotal's scan result offers a snapshot of how the domain was evaluated by a wide range of security engines at the time of its check.
For betovia.top, it is advisable to retain the PhishDestroy internal listing and VirusTotal scan records for future comparison. The OTX pulse count should also be preserved and monitored for any changes. Reviewing these sources periodically will help track any new developments or observations associated with the domain.
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://betovia.top/; 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.
aida.ns.cloudflare.com.Location describes the IP network.
3f61205e5e89f700901920611a6d39a124bde09adac1f7766b2877770d3e3689Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
172.67.177.243. 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