VirusTotal
1 / 92
DenunciarEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
Assessment based on the stored source evidence below. Review sources →
bezhaven.shop — No verificado. Resumen de las pruebas: VirusTotal 1/92 (Gridinsoft); URLScan capture; PhishDestroy score 55/100. Registrador: Dynadot.
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
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.
1 / 92
DenunciarEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
Report stored; detailed verdict not recorded
Alerts refer to the preserved scan. They do not describe the current state of the site.
3 community references
DenunciarCommunity publication references, not a vendor verdict or evidence of a common operator.
informe almacenado
View stored capture ↗ DenunciarA 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
DenunciarA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
DetallesA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
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.
bezhaven.shop was observed in a VirusTotal detection record on 2026-10-16, providing a dated external reference for the domain. The same date includes a PageSpeed performance measurement for bezhaven.shop.
VirusTotal recorded 1 detection out of 92 scanners for bezhaven.shop on 2026-10-16. On this date, the domain was also present in the PhishDestroy internal listing. OTX referenced bezhaven.shop in 3 pulses as of 2026-10-16. The PageSpeed performance score was measured at 85 on 2026-10-16. Registration records show bezhaven.shop was registered through Dynadot Inc. on 2026-05-25.
PhishDestroy contains a dated listing for bezhaven.shop, documenting its inclusion in an internal catalogue. VirusTotal provides a measurement of the domain's detection by external scanners, while OTX records its mention in multiple intelligence pulses. These sources each capture different aspects of the domain's presence and technical characteristics on their respective observation dates.
For bezhaven.shop, retain the VirusTotal detection record and the PhishDestroy internal listing for ongoing reference. Compare the OTX pulse mentions with later intelligence records to track any changes. Preserve the PageSpeed performance score as a technical benchmark for future infrastructure assessments.
20 · datasets with records / 11 · 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.
These checks have no retained result. This does not mean they passed or that a scan is running.
0 · external source matches
Dynadot Inc. · 195.96.130.209 · DNS, TLS and retained responses
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.
bonnie.ns.cloudflare.comvalentin.ns.cloudflare.comLocation describes the IP network.
a76bc4eaa7e9e4990bc9ac5de4a4a5dc7e81b7ef174ade8ac012827a3dac3255Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of bezhaven.shop · checked Oct 16, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://bezhaven.shop/https://bezhaven.shop/Cache-Control: private, no-cache, no-store, max-age=0, must-revalidateContent-Encoding: gzipContent-Type: text/html; charset=utf-8summary_large_imageh3=":443"; ma=2592000private, no-cache, no-store, max-age=0, must-revalidategziptext/html; charset=utf-8Fri, 16 Oct 2026 00:01:37 GMT; rel=preload; as="style"strict-origin-when-cross-originchunkedRSC, Next-Router-State-Tree, Next-Router-Prefetch, Next-Router-Segment-Prefetch, Accept-Encoding1.1 CaddynosniffSAMEORIGIN1; mode=blockValues retained by the collector; long values may be shortened during collection.
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.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
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.
Local archivado el 2026-10-16 00:01:38 UTCNo hay un resultado de comprobación guardado.
1 · outbound report records
195.96.130.209.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Desconocido
probe_inconclusive
Accesible
9 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.
Shared hosting, registrar records and related domains
Original reports, independent checks and evidence links
PD-20261016-91E987 Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
Recovery steps, reporting contacts and complaint drafts
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.
Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
bezhaven.shop)Aunque no tengas todos los detalles — presenta la denuncia de todos modos. Incluso la información parcial sigue siendo útil para las investigaciones.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Análisis de amenazas utilizando listas de bloqueo almacenadas, WHOIS, DNS y evidencia de escaneo público
Escanear ahoraEnvía los dominios sospechosos a nuestra base de datos de amenazas: protege a la comunidad
DenunciarInformes de phishing recientes y cambios de disponibilidad observados
MonitorizarSupervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de un falso positivo.
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:33:32 UTC, bezhaven.shop tuvo detecciones de los motores de seguridad 1.
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.
Si cree que esta lista es inexacta, presentar una apelación. Para conocer nuestra metodología, visita el Página de preguntas frecuentes.