Ir al informe de seguridad
Domain security report
bigfacebrandshop.shop favicon

bigfacebrandshop.shop

Veredicto de amenaza
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Disponibilidad No verificado La accesibilidad actual no está verificada Observado · HTTP probe
VirusTotal detecciones: 13/92
16/10/2026
API
Resolved IP
212.52.28.186
3 sources
In this reportGet help
Este dominio ha sido señalado como malicioso
Motores de seguridad que informan una detección: 13. Tenga extrema precaución: no ingrese credenciales o información personal.
Resumen del informe

bigfacebrandshop.shop — No verificado. Resumen de las pruebas: VirusTotal 13/92 (alphaMountain.ai, BitDefender, Chong Lua Dao, ESET, Fortinet); URLScan capture; PhishDestroy score 89/100.

El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.

Additional indicators at a glance

VirusTotal
VirusTotal
13 det.
URLScan
URLScan
Certificado TLS
Within stored validity dates
Let's Encrypt / YE2 · Hostname coverage not recorded
PhishDestroy
DestroyList
Incluido

Source evidence

7 · 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.

VirusTotal

13 / 92

Denunciar
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

Report stored; detailed verdict not recorded

Observation time not recorded
Denunciar
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

OTX

no community references

Denunciar
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

URLScan capture

informe almacenado

View stored capture ↗
Denunciar
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

CF Radar

Report stored; verdict not recorded

Observation time not recorded
Denunciar
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Google Safe Browsing

Checked; no threat flag recorded

Denunciar
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

0 external matches

Detalles
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Resumen de las pruebas

Crítico
VirusTotal
13/92
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

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.

Recorded Evidence

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.

Interpretation

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.

Recommended Actions

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.

Data coverage & collection

18 · datasets with records / 13 · not recorded

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.

Recorded dataPartial recordUTC
VirusTotal
13 / 92 · engine detections
URLScan analysis
Capture retained; no provider verdictCollection time not recorded
URLQuery
Stored source recordCollection time not recorded
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
0 · external matches
Cloudflare Radar
Report link retainedCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Network & DNS
212.52.28.186 · 2 · nameserversCollection time not recorded
Certificado TLS
Let's Encrypt / YE2
Page captures
3 · retained captures
Page analysis
0 · automated brand labels
Site configuration files
robots.txt · sitemap.xml · security.txt
PageSpeed performance
86/100 · mobile performance
Recorded subdomains
1 · retained hostnamesCollection time not recorded
Availability history
1 · stored state changes
Source observation history
1 · stored source events
IP reputation
Network-level observations
Not recorded in this report 13

These checks have no retained result. This does not mean they passed or that a scan is running.

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Domain registration
  • HTML archives
  • Observed indicators
  • Detection & evasion
  • Response records
  • Lookalike relationships
  • Reportes de la comunidad
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Estado de la lista de bloqueados pública

Domain, network & archive

212.52.28.186 · DNS, TLS and retained responses

Domain details

Dominio
Reputación de IP abuse score 0/100 0 reports checked 16/10/2026
Registrador Desconocido
Contacto de abusoabuse@rashost.com
Detalles técnicosProvenance & timestamps
Primera detección16/10/2026
DOM Analysisanalyzed 16/10/2026score 0/100
Submitted URLhttp://bigfacebrandshop.shop/
Favicon Hash
ID del caso

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
212.52.28.186
Network ASN
AS199242
Organization
Malakmadze Web LLC
Observed location
Los Angeles, US
Servidores de nombres 2
  • bradley.ns.cloudflare.com
  • lana.ns.cloudflare.com

Location describes the IP network.

Certificado TLS

Issuer
Let's Encrypt / YE2
Valid from
2026-09-28 18:24:40
Valid until
2026-12-27 18:24:39
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-16 01:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprintc10e5383b33b542fdf32ae4e81c34a6f9b426f090088b59912719b5a160f6543

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-16 00:03:56 UTC

Primary outcome Desconocido reason: Stale Current Evidence 0% confidence
Attribution source: Current State Backfill
Evidence layers Availability: Unknown Content: Unknown DNS: Stale Registration: Unknown
RDAP registration Desconocido
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • img.bigfacebrandshop.shopDomain record

The original observation time is not recorded for these hostnames.

Denunciar este dominio Envía pruebas y ayuda a proteger a los demás

Análisis de VirusTotal

13 / Los proveedores de seguridad de 92 marcaron este dominio
View on VT
Last analyzed
alphaMountain.ai
BitDefender
Chong Lua Dao
ESET
Fortinet
G-Data
Gridinsoft
LevelBlue
Lionic
Netcraft
Sophos
VIPRE
Webroot
Análisis del rendimiento del sitio

Google PageSpeed Insights — mobile performance audit of bigfacebrandshop.shop · checked Oct 16, 2026

86
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
2.89s
Largest Contentful Paint
CLS
0.037
Cumulative Layout Shift
TBT
187ms
Total Blocking Time
SI
3.91s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Crawler & disclosure files

Site configuration evidence

3 · file checks

Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.

robots.txt

Unverified (legacy)
/robots.txt
HTTP response
301
Observed at
2026-10-16 00:04:18 UTC
Fuente
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Sitemap

Unverified (legacy)
/sitemap.xml
HTTP response
301
Observed at
2026-10-16 00:04:18 UTC
Fuente
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

security.txt

Unverified (legacy)
/.well-known/security.txt
HTTP response
301
Observed at
2026-10-16 00:04:18 UTC
Fuente
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Detection & evasion checks

Stored browser and crawler observations

Análisis de detección y evasión

Comprobación del enmascaramiento y la distribución del tráfico

Aún no se ha escaneado Aún no se ha registrado ninguna diferencia entre los rastreadores y los navegadores

Observaciones almacenadas de rastreadores frente a navegadores para este servidor, además de una comprobación en tiempo real de la huella digital para sistemas de distribución de tráfico al estilo Keitaro.

Indicador de camuflaje almacenado
Aún no se ha escaneado
Comprobación de huellas dactilares en directo en TDS
Siete indicadores de Keitaro y una comparación entre navegador y rastreador. El análisis comienza solo al pulsar el botón.
Bajo demanda

No hay un resultado de comprobación guardado.

Timeline & response

Collection history, report status and investigation channels

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Threat First Observed 2026-10-16 00:03:38 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as unknown pointing to IP 212.52.28.186.
Stored observation history2

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Desconocido

    stale_current_evidence

  2. Availability monitor · First collection record

    Desconocido

Proceso de respuesta ante amenazas Pipeline

Descubrimiento
Analysis
Monitoring

7 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Amenaza detectada
bigfacebrandshop.shop detectados y puestos en cola para su análisis completo
16/10/2026
URLScan.io Capture
Almacenado URLScan report with capture artifacts
16/10/2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
VirusTotal
13/92 recorded on VirusTotal
16/10/2026
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
16/10/2026
Technical Analysis Recorded
El informe contiene tecnología almacenada o resultados de análisis forenses.
16/10/2026
Lista de destrucción publicada
16/10/2026
How we investigate & report

Public scans, evidence and abuse channels

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.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

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.

Related infrastructure

Shared hosting, registrar records and related domains

Evidence & investigation tools

Original reports, independent checks and evidence links

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

¿Te ha afectado esta página web?

4 evidence signal groups linked 0 stored notification records No verificado

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

Si ingresó credenciales de cuenta, información personal o de pago, o descargó un archivo de este dominio, tome medidas inmediatas. A continuación encontrará recursos que le ayudarán a informar el incidente y protegerse.

Official reporting routes
¡Cuidado con los estafadores que se hacen pasar por empresas de recuperación de datos! Los delincuentes pueden volver a contactar a las víctimas haciéndose pasar por investigadores, abogados o agentes de recuperación. No pague tarifas por adelantado ni comparta credenciales. Más información sobre el fraude en las ayudas de recuperación →
Informa a las autoridades locales

Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.

directorio de 97 países

Template-based draft · optional AI wording assistance requires separate consent

Borrador asistido por IA: el proveedor de IA procesa los detalles del incidente · Revíselo y envíelo usted mismo
After a phishing incident

Recomendaciones y consejos para las víctimas

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

¿Qué debo hacer ahora mismo?

Urgente

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Cambiar todas las contraseñas — correo electrónico, cuentas de Exchange, cualquier cosa que utilice la misma contraseña
  • Activar la autenticación de dos factores utilizando una aplicación de autenticación (no SMS). Desactivar la recuperación mediante SMS
  • Tarjetas de congelación si has introducido tus datos bancarios en la página de phishing

¿Qué información debo recopilar para mi informe?

Directrices del FBI

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Fechas y horas exactas — de cada transacción y del primer contacto con el estafador
  • Capturas de pantalla — páginas web fraudulentas, mensajes de chat, correos electrónicos, transacciones con monederos electrónicos, redes sociales
  • Todas las URL y dominios utilizados por el estafador (incluidos bigfacebrandshop.shop)
  • Comunicaciones — correos electrónicos, mensajes de texto, números de teléfono y nombres de usuario que utilizó el estafador

Aunque no tengas todos los detalles — presenta la denuncia de todos modos. Incluso la información parcial sigue siendo útil para las investigaciones.

¿Dónde debo denunciar la estafa?

  • IC3 del FBI — Centro de Denuncias de Delitos en Internet (sistema federal de denuncia de EE. UU.)
  • Europol — Informes sobre la ciberdelincuencia en Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Policía local — deja constancia oficial, aunque no puedan actuar de inmediato

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Páginas web falsas — Clones idénticos al milímetro de sitios web legítimos, con dominios ligeramente modificados
  • Sacrificio de cerdos — Se ganaba la confianza de las víctimas a lo largo de varias semanas a través de Telegram, WhatsApp o aplicaciones de citas, y luego les robaban el dinero.
  • Estafas relacionadas con la recuperación — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Estafas basadas en la inteligencia artificial — los «deepfakes», el phishing automatizado y los sitios web generados por IA, que hacen que el fraude sea más difícil de detectar

¿Cómo puedo protegerme en el futuro?

  • Añadir a favoritos las páginas web oficiales — Nunca hagas clic en enlaces de correos electrónicos, mensajes directos o anuncios
  • Verificar dominios — comprobar si PhishDestroy antes de interactuar. Comprueba que sea HTTPS, la ortografía y la antigüedad del dominio
  • «Demasiado bueno para ser verdad» = estafa — rendimientos garantizados, recomendaciones de famosos, plazos urgentes

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Mantente informado, mantente a salvo

Supervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de un falso positivo.

Flujo de amenazas en tiempo real Reclamar este anuncio
Read the evidence in context

Acerca de este informe: bigfacebrandshop.shop

Este informe presenta la última evidencia almacenada disponible para PhishDestroy. Las marcas de tiempo de origen se muestran cuando están disponibles; La disponibilidad y los veredictos de los proveedores pueden cambiar después de la recolección.

A partir de 2026-10-16 00:04:02 UTC, bigfacebrandshop.shop tuvo detecciones de los motores de seguridad 13.

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Incrustar este informe

Comparte esta información sobre amenazas en tu página web o blog

embed.html
<iframe
  src="https://phishdestroy.io/es/embed/domain/bigfacebrandshop.shop"
  title="PhishDestroy threat report for bigfacebrandshop.shop"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>