VirusTotal
3 / 92
“beige-crossbody.shop”
beige-crossbody.shop was observed on 2026-10-08 with several security reviews, including a VirusTotal scan and an OTX pulse listing. The domain is also catalogued in the PhishDestroy internal listing, providing multiple dated perspectives for evaluation.
VirusTotal scanned beige-crossbody.shop on 2026-10-08, reporting 3 detections out of 92 scanners. OTX reviewed the domain on 2026-10-08, recording its inclusion in one OTX pulse. The PhishDestroy internal catalogue also listed the domain on the same date.
These source records offer a coordinated snapshot of beige-crossbody.shop as seen by VirusTotal, OTX, and PhishDestroy on 2026-10-08. Each source applies its own review process, allowing for comparison of their independent findings without implying a unified assessment.
For beige-crossbody.shop, preserve the VirusTotal, OTX, and PhishDestroy records for future reference. Compare later source observations to these records to track any changes or updates in the domain's security profile.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginxScanner note: alive_content: raw=ok; http=200; via=http_proxy; server=nginx
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.
ns2.dnsip.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.
34.8.77.192. 10 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