VirusTotal
13 / 91
“Domain Inactive”
The domain rbx.ac was included in a VirusTotal scan on 2026-09-29, providing a dated security observation. This domain was also referenced in the publisher-owned PhishDestroy internal listing, which catalogues domains for monitoring.
VirusTotal recorded 13 detections out of 91 scanners for rbx.ac on 2026-09-29. OTX noted 14 pulses referencing rbx.ac as of 2026-10-02. The PhishDestroy internal listing included rbx.ac on 2026-10-02, and the domain was first observed on the same date.
These records from VirusTotal, OTX, and the PhishDestroy catalogue indicate that rbx.ac has been referenced by several security data sources. The presence of detection counts and pulse references shows that the domain has been noted in multiple monitoring systems, though the evidence does not specify the content or context associated with these references.
To facilitate ongoing review, retain the VirusTotal, OTX, and PhishDestroy records for rbx.ac for future comparison. Use these source records to track any subsequent changes or additional observations related to this domain.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: alive_content: raw=content_403; http=403; via=https_proxy
max.ns.cloudflare.commail.hotwall.apppriority 10Location describes the IP network.
104e958cc3019de1449fc27db2efcc4ae8ab6dfc74139a4a3f13ec198d416179Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
51.254.208.172. 13 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