VirusTotal
13 / 92
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
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.
13 / 92
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
no community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
View stored capture ↗ ReportA preserved page image documents what the collector received; a capture is not a safety verdict.
Report stored; verdict not recorded
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
DetailsA 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 bigfacebrandshop.shop was observed with a VirusTotal detection record on 2026-10-12, providing insight into its security profile. Additionally, a PageSpeed performance score was recorded for this domain, offering a technical perspective on its web infrastructure.
On 2026-10-12, VirusTotal recorded 13 detections out of 92 total scanners for bigfacebrandshop.shop. The domain was internally listed by PhishDestroy as of 2026-10-16. A PageSpeed performance score of 86 was documented on 2026-10-16, reflecting technical aspects of the site at that time.
The VirusTotal record contains a count of detections from multiple external scanners, serving as a quantitative measure of how the domain was classified by various security engines. The PhishDestroy internal listing documents the domain's inclusion in a publisher-owned catalogue, which is distinct from external blocklists. These records together provide a snapshot of how bigfacebrandshop.shop was viewed by select security sources on their respective dates.
For ongoing monitoring, retain the VirusTotal detection record for bigfacebrandshop.shop as a reference for future comparison. Preserve the PhishDestroy internal listing to document its status in publisher-owned catalogues. The PageSpeed performance score can be used to compare technical changes over time.
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
bradley.ns.cloudflare.comlana.ns.cloudflare.comLocation describes the IP network.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
img.bigfacebrandshop.shopDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of bigfacebrandshop.shop · checked Oct 16, 2026
Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.
/robots.txt
A legacy response is stored, but it does not establish whether the file exists.
/sitemap.xml
A legacy response is stored, but it does not establish whether the file exists.
/.well-known/security.txt
A legacy response is stored, but it does not establish whether the file exists.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
212.52.28.186.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown
stale_current_evidence
Unknown
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.
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