Aller au rapport de sécurité
Tableau de bord analytique
Domain security report
bigshotfashion.shop favicon

bigshotfashion.shop

Verdict de menace
CritiqueRecours en matière de nom de domaine
Assessment sources

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

Disponibilité Non vérifié L'accessibilité actuelle n'est pas vérifiée Observé · HTTP probe
Signaux de risque
Détections VirusTotal : 14/92
16/10/2026
API
Resolved IP
5.255.61.90
2 sources
The capture source is temporarily unavailable.
1 / 2
Source
Primary capture
Collected · UTC
Open capture
In this reportGet help
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 14. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
Résumé du rapport

bigshotfashion.shop — Non vérifié. Résumé des preuves: VirusTotal 14/92 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); URLQuery 2 det.; URLScan capture; PhishDestroy score 95/100.

L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.

Additional indicators at a glance

VirusTotal
VirusTotal
14 det.
URLQuery
URLQuery
2 det.
URLScan
URLScan
Signaler ↗
PhishDestroy
DestroyList
Répertorié

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

14 / 92

Signaler
Interpretation & limits

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

URLQuery

2 det.

Observation time not recorded
Signaler
Interpretation & limits

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

OTX

no community references

Signaler
Interpretation & limits

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

URLScan capture

rapport stocké

View stored capture ↗
Signaler
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
Signaler
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

Signaler
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

Détails
Interpretation & limits

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

Résumé des preuves

Critique
VirusTotal
14/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

bigshotfashion.shop was observed with a VirusTotal scan on 2026-09-23, providing a recent security data point for the domain. The domain also has a recorded PageSpeed performance score that may inform technical assessments.

Recorded Evidence

On 2026-09-23, VirusTotal recorded 14 detections out of 92 total scanners for bigshotfashion.shop. The domain was listed in the PhishDestroy internal catalogue as of 2026-10-16. A PageSpeed performance score of 67 was documented on 2026-10-16.

Interpretation

VirusTotal provides a record of scanner detections, which measures how many participating security engines flagged bigshotfashion.shop on the scan date. The PhishDestroy listing documents internal catalogue status, offering another perspective on how the domain is tracked within that system. The PageSpeed score adds a technical metric relevant to site performance but does not reflect security posture.

Recommended Actions

For future review of bigshotfashion.shop, retain the VirusTotal detection results and the PhishDestroy internal listing as reference points. Compare these records with subsequent scans and listings to monitor any changes in security-related findings. The PageSpeed performance score should also be preserved for technical benchmarking in later assessments.

Data coverage & collection

17 · datasets with records / 14 · 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
14 / 92 · engine detections
URLScan analysis
Capture retained; no provider verdictCollection time not recorded
URLQuery
2 · recorded detections / alertsCollection 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
5.255.61.90 · 2 · nameserversCollection time not recorded
Page captures
2 · retained captures
HTML archives
1 · retained responses
Page analysis
0 · automated brand labels
Site configuration files
robots.txt · sitemap.xml · security.txt
PageSpeed performance
67/100 · mobile performance
Availability history
1 · stored state changes
Source observation history
1 · stored source events
IP reputation
Network-level observations
Not recorded in this report 14

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
  • Certificat TLS
  • Observed indicators
  • Detection & evasion
  • Response records
  • Recorded subdomains
  • Lookalike relationships
  • Signalements communautaires
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Statut de la liste de blocage publique

Domain, network & archive

5.255.61.90 · DNS, TLS and retained responses

Domain details

Domaine
Réputation de l’IP abuse score 0/100 0 reports checked 16/10/2026
Bureau d’enregistrement Inconnu
Contact anti-abusabuse@rashost.com
Détails techniquesProvenance & timestamps
Première détection16/10/2026
DOM Analysisanalyzed 16/10/2026score 0/100
Submitted URLhttp://bigshotfashion.shop/
Favicon Hash
ID du dossier

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
5.255.61.90
Network ASN
AS199242
Organization
Malakmadze Web LLC
Observed location
Los Angeles, US
Serveurs de noms 2
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

Location describes the IP network.

viewdns.info · 5.255.61.90rapiddns.io

Latest Classified Outcome 2026-10-16 01:23:07 UTC

Primary outcome Inconnu reason: Stale Current Evidence 0% confidence
Attribution source: Current State Backfill
Evidence layers Availability: Unknown Content: Unknown DNS: Stale Registration: Unknown
RDAP registration Inconnu
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.
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

14 / Les fournisseurs de sécurité 92 ont signalé ce domaine
View on VT
Last analyzed
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
Netcraft
Sophos
Analyse des performances du site

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

67
Needs Work
Performance
FCP
2.9s
First Contentful Paint
LCP
5.47s
Largest Contentful Paint
CLS
0.004
Cumulative Layout Shift
TBT
327ms
Total Blocking Time
SI
2.9s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://bigshotfashion.shop/
Final URL: https://bigshotfashion.shop/
Home | BIGSHOT Fashion
BigShot Fashion
Réponse
HTTP 200
HTML body
268.9 KB
Compressed
44.1 KB
Links
32 internal · 0 external
Detected technologies
react
Selected response headers
Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Security headers present
X-Frame-OptionsX-Content-Type-OptionsX-XSS-ProtectionReferrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Open Graph title: Accueil
Open Graph description: BigShot Fashion
Twitter card: summary_large_image
Saved response-header values · 13
Alt-Svc
h3=":443"; ma=2592000
Cache-Control
private, no-cache, no-store, max-age=0, must-revalidate
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Fri, 16 Oct 2026 01:17:05 GMT
Link
; rel=preload; as="style"
Referrer-Policy
strict-origin-when-cross-origin
Transfer-Encoding
chunked
Vary
RSC, Next-Router-State-Tree, Next-Router-Prefetch, Next-Router-Segment-Prefetch, Accept-Encoding
Via
1.1 Caddy
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN
X-XSS-Protection
1; mode=block

Values retained by the collector; long values may be shortened during collection.

Archived
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 01:17:06 UTC
Source
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 01:17:06 UTC
Source
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 01:17:06 UTC
Source
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

Analyse de la détection et de l'évasion

Vérification du cloaking et de la répartition du trafic

Pas encore numérisé Aucune différence entre les robots d'indexation et les navigateurs n'a encore été constatée

Enregistrement des observations « crawler contre navigateur » pour cet hôte, ainsi qu'une vérification en temps réel des empreintes numériques pour les systèmes de répartition du trafic de type Keitaro.

Indicateur de camouflage enregistré
Pas encore numérisé
Routage de la capture
Local archivé le 2026-10-16 01:17:06 UTC
Vérification en direct des empreintes digitales d'TDS
Sept empreintes Keitaro et une comparaison entre navigateur et robot. Une nouvelle analyse démarre uniquement en cliquant sur le bouton.
À la demande

Aucun résultat de vérification enregistré.

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 01:17:31 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 5.255.61.90.
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

    Inconnu

    stale_current_evidence

  2. Availability monitor · First collection record

    Accessible

Processus de réponse aux menaces Pipeline

Découverte
Analysis
Monitoring

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

Menace détectée
bigshotfashion.shop détectés et mis en file d'attente en vue d'une analyse complète
16/10/2026
URLScan.io Capture
Enregistré 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
14/92 recorded on VirusTotal
16/10/2026
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
16/10/2026
Technical Analysis Recorded
Le rapport contient des résultats de technologie ou d’analyse médico-légale stockés.
16/10/2026
DestroyList publié
Listed in the public PhishDestroy/DestroyList repository
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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecÉvaluation du site AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Related infrastructure

Shared hosting, registrar records and related domains

Evidence & investigation tools

Original reports, independent checks and evidence links

Données factuelles et rapports externes

Analyse de sécurité
URLScan Stored capture VirusTotal 14 det. ChainPatrol URLQuery 2 det. SSL Laboratoires CF Radar Ouvrir le rapport WOT ScamAdviser Vérificateur de liste noire URL nulle Sucuri SiteCheck Observatoire MDN
OSINT et renseignement
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certificats WHOIS Wayback
DNS et réseau
nslookup.io DNS bgp.tools ASN /Itinéraire
Référencement naturel et nom de domaine
SpyFu Moz DA/PA Ahrefs Liens entrants
Analyse approfondie
Analyse approfondie

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Ce site vous a-t-il affecté ?

4 evidence signal groups linked 0 stored notification records Non vérifié

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 vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.

Immediate steps Find reporting contacts
Official reporting routes
PhishDestroy listing review Pas un rapport des forces de l'ordre
Recours en matière de nom de domaine
Demandez un examen si vous possédez ce domaine et pensez que la liste est incorrecte
Méfiez-vous des escrocs qui prétendent vous aider à récupérer vos biens ! Les criminels peuvent recontacter leurs victimes tout en se faisant passer pour des enquêteurs, des avocats ou des agents de recouvrement. Ne payez pas de frais initiaux et ne partagez pas vos informations d'identification. En savoir plus sur la fraude liée aux aides à la reprise →
Signalez-le à vos autorités locales

Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.

Annuaire de 97 pays

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

Brouillon assisté par l'IA : les détails de l'incident sont traités par le fournisseur d'IA · Examinez-le et soumettez-le vous-même
After a phishing incident

Recommandations et conseils à l'intention des victimes

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

Que dois-je faire tout de suite ?

Urgent

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

  • Modifier tous les mots de passe — e-mail, comptes Exchange, tout ce qui utilise le même mot de passe
  • Activer l'authentification à deux facteurs (2FA) en utilisant une application d'authentification (et non par SMS). Désactivez la récupération par SMS
  • Cartes « Freeze » si vous avez saisi vos coordonnées bancaires sur le site de hameçonnage

Quelles informations dois-je rassembler pour mon rapport ?

Directives du 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.
  • Dates et horaires exacts — de chaque transaction et du premier contact avec l'escroc
  • Captures d'écran — sites web frauduleux, messages de chat, e-mails, transactions via des portefeuilles numériques, réseaux sociaux
  • Toutes les URL et tous les noms de domaine utilisés par l'escroc (notamment bigshotfashion.shop)
  • Communications — les e-mails, SMS, numéros de téléphone et noms d'utilisateur utilisés par l'escroc

Même si vous ne disposez pas de tous les détails — déposer quand même une plainte. Même des informations partielles peuvent aider les enquêtes.

À qui dois-je signaler cette arnaque ?

  • FBI IC3 — Centre de signalement des délits sur Internet (système fédéral américain de signalement)
  • Europol — Rapports sur la cybercriminalité en Europe (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Police locale — permet de consigner officiellement la situation, même s’ils ne peuvent pas agir immédiatement

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?

  • Faux sites web — des clones identiques au pixel près de sites légitimes, dont les noms de domaine ont été légèrement modifiés
  • Découpe du porc — une relation de confiance établie au fil des semaines via Telegram, WhatsApp ou des applications de rencontre, puis une escroquerie financière
  • Arnaques liées au recouvrement — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Escroqueries basées sur l'IA — les « deepfakes », le hameçonnage automatisé et les sites générés par l'IA, qui rendent la fraude plus difficile à détecter

Comment puis-je me protéger à l'avenir ?

  • Ajouter les sites officiels à vos favoris — Ne cliquez jamais sur les liens contenus dans les e-mails, les messages privés ou les publicités
  • Vérifier les noms de domaine — vérifier si PhishDestroy avant d'entrer en contact. Vérifiez le protocole HTTPS, l'orthographe et l'ancienneté du domaine
  • « Trop beau pour être vrai » = arnaque — des rendements garantis, des témoignages de célébrités, des délais serrés

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

Vérifier n'importe quel domaine

Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique

Scanner maintenant

Signaler une tentative d'hameçonnage

Signalez les domaines suspects à notre base de données des menaces — protégez la communauté

Signaler

Flux d'alertes en temps réel

Rapports de phishing récents et changements de disponibilité observés

Surveiller

Restez informés, restez en sécurité

Surveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif

Flux d'alertes en temps réel Contester cette annonce
Read the evidence in context

À propos de ce rapport : bigshotfashion.shop

Ce rapport présente les dernières preuves stockées disponibles pour PhishDestroy. Les horodatages sources sont affichés lorsqu'ils sont disponibles ; la disponibilité et les verdicts des fournisseurs peuvent changer après la collecte.

Depuis 2026-10-16 01:17:55 UTC, bigshotfashion.shop avait des détections provenant des moteurs de sécurité 14.

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 vous pensez que cette liste est inexacte, déposer un recours. Pour en savoir plus sur notre méthodologie, visitez le Page FAQ.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Intégrer ce rapport

Partagez ces informations sur les menaces sur votre site web ou votre blog

embed.html 
<iframe
  src="https://phishdestroy.io/fr/embed/domain/bigshotfashion.shop"
  title="PhishDestroy threat report for bigshotfashion.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>