VirusTotal
1 / 92
bivadex.com was observed on 2026-10-07 with a server header of 'cloudflare', reflecting a recorded response from a Cloudflare endpoint. The domain is also included in the publisher-owned PhishDestroy internal listing, which catalogs observed domains for reference.
VirusTotal reported 1 detection out of 92 scanners for bivadex.com on 2026-10-07. OTX referenced the domain in 4 pulses as of 2026-10-07. The domain was registered via Fewmoretaps OU d/b/a Trustname.com on 2026-09-14. A URLscan report was available from 2026-09-21.
The evidence from VirusTotal, OTX, and PhishDestroy provides a dated record of bivadex.com’s presence across several monitoring platforms. These observations allow for comparison of the domain’s status at different points in time and across distinct catalogues. The registration and scanning dates offer chronological context for reviewing its recorded activity.
For bivadex.com, it is recommended to retain the VirusTotal detection record and OTX pulse references for ongoing review. The PhishDestroy internal listing should be preserved for catalog comparison. Examining the available URLscan report may provide further context for future monitoring or investigation.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Edge-IP reputation is not attributed to this domain.
isaac.ns.cloudflare.comLocation 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.
104.21.17.70. 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