VirusTotal
4 / 92
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Royalty Free Beat Packs | Beatpackshop”
Assessment based on the stored source evidence below. Review sources →
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
4 / 92
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
malicious
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
4 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored report
A preserved page image documents what the collector received; a capture is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
The domain beatcurrent.shop was first observed on 2026-10-11, with a VirusTotal scan on that date recording 4 detections out of 92 scanners. OTX also checked the domain on 2026-10-12, providing an additional intelligence reference for that period.
VirusTotal recorded 4 detections out of 92 scanners for beatcurrent.shop on 2026-10-11. OTX checked the domain on 2026-10-12 and documented 4 pulses. The domain is included in the PhishDestroy internal listing according to the latest evidence.
VirusTotal provides a measurement of security scanner detections for beatcurrent.shop, which reflects how the domain was evaluated by multiple engines on its scan date. The OTX record contains pulse counts, documenting external intelligence activity referencing the domain. The PhishDestroy internal listing adds another distinct record, capturing its presence in a publisher-maintained catalogue. These records together offer a snapshot of how the domain was observed by different sources within a short timeframe.
For beatcurrent.shop, preserve the VirusTotal detection record and the OTX pulse record for future reference and comparison. Retain the PhishDestroy internal listing as a separate source to monitor any changes in catalogue status. Comparing these records over time can help track shifts in external intelligence and detection measurements for the domain.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
CaddyScanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://beatcurrent.shop/; server=Caddy
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.
hunts.ns.cloudflare.comLocation describes the IP network.
8e705ca4479d8794b349017b6bc07786b3fd781cdaba2eec5f3bba0d8e8b3fd8Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
188.244.119.46.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