VirusTotal
8 / 89
“Apache2 Ubuntu Default Page: It works”
On 2026-10-01, chatbot-virbac.heyyou.cc returned an HTTP 403 status code, indicating that access to the domain was restricted at that time. The domain was first observed on 2026-09-05, providing a baseline for its recorded activity.
According to the PhishDestroy internal listing, chatbot-virbac.heyyou.cc was included as of the latest records. An SSL scan performed on 2026-09-15 identified the certificate issuer as PhishDestroy / botadmin.destroy.tools. VirusTotal checked the domain on 2026-09-19 and reported 8 detections out of 89 scanners.
These observations document a sequence of technical checks on chatbot-virbac.heyyou.cc, each with its own focus and timing. The HTTP 403 response is specific to the 2026-10-01 check, while the VirusTotal and SSL scan results reflect their respective dates and criteria. The internal listing by PhishDestroy provides another reference point for the domain's status within that system.
For chatbot-virbac.heyyou.cc, maintain the PhishDestroy internal listing and VirusTotal scan results as distinct reference records. Compare the HTTP status to future checks to monitor any changes in access restrictions. Preserve the SSL scan and first observation date for historical comparison. Review updated records from each source as they become available.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginxScanner note: hosting_placeholder: raw=placeholder; http=200; via=https_direct; server=nginx
ns245.neubox.netLocation describes the IP network.
7c5e1aa1ed0482d2a202122f3cc8f8bc15b8422f8c159c68c0f475e8e865e16bSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
6 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.
1 community report
CategoryPHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-09-04T16:06:45.430Z.
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