URLScan verdict
malicious
SignalerThis is the recorded automated analysis. Completion alone is not a safety verdict.
“Billie Eilish Shop | Billie Eilish”
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@rashost.com.
The latest stored availability evidence still shows the domain reachable; 27 hours has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
billieeilishdirect.shop — Dernier actif connu (HTTP 200). Usurpation de l'identité de la marque : Fakeshop; Type d'arnaque : Impersonation. Résumé des preuves: VirusTotal 0/92; URLScan malicious verdict; PhishDestroy score 65/100. Bureau d’enregistrement: Dynadot.
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique 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.
malicious
SignalerThis is the recorded automated analysis. Completion alone is not a safety verdict.
checked — no detections recorded
SignalerEngine 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.
no community references
SignalerCommunity 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.
rapport stocké
View stored capture ↗ SignalerA preserved page image documents what the collector received; a capture is not a safety verdict.
Checked; no threat flag recorded
SignalerA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
DétailsA 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.
The domain billieeilishdirect.shop was recorded with a PhishDestroy internal listing on 2026-10-16, providing a dated entry in the publisher's catalogue. A PageSpeed performance score of 75 was also documented for this domain on the same date, offering a technical perspective on its web performance.
VirusTotal checked billieeilishdirect.shop on 2026-10-12, recording 0 detections out of 92 total scanners. The domain was registered through Dynadot Inc. on 2026-06-13. PhishDestroy marked an internal listing for the domain on 2026-10-16. PageSpeed measured the domain's performance score at 75 on 2026-10-16.
PhishDestroy provides a listing that records the domain's presence in its internal catalogue, which serves as a publisher-managed reference. VirusTotal's entry documents the results of automated security scans, capturing the domain's status with numerous external scanners at a specific point in time. These records offer a snapshot of technical and security-related observations, each reflecting a distinct aspect of the domain's profile.
For billieeilishdirect.shop, retain the PhishDestroy listing and the VirusTotal scan results as key records for ongoing reference. Compare future technical and security scans with these documented entries to monitor for any changes. Use the PageSpeed performance score as a baseline for evaluating technical adjustments over time.
23 · datasets with records / 8 · 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. · 91.246.50.210 · 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.
hassan.ns.cloudflare.comkinsley.ns.cloudflare.comLocation describes the IP network.
970de27ecf00a69cba7afa95805efb69f98ee361cf6a90c42659676b7f672578Saved 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 billieeilishdirect.shop · checked Oct 16, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://billieeilishdirect.shop/https://billieeilishdirect.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 17:28:17 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
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.
Local archivé le 2026-10-16 17:28:18 UTCNote relative à la numérisation: alive_content: raw=ok; http=200; via=https_proxy
Aucun résultat de vérification enregistré.
1 · outbound report records
91.246.50.210.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Inconnu→live_content
content_served
Indisponible→Accessible
Accessible→Indisponible
Inconnu
stale_current_evidence
Inconnu
12 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-8D9601 Recipient: abuse@rashost.com AUP & Terms of Service Violations: Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices. Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension. Applicable Legal Framework (Unknown): International Anti-Cybercrime Regulations Budapest Convention on Cybercrime Universal Fraud Prevention Laws Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws. Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
Recovery steps, reporting contacts and complaint drafts
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.
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
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 ↗
billieeilishdirect.shop)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.
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
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerRapports de phishing récents et changements de disponibilité observés
SurveillerSurveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif
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.
Le site capturé affichait le titre de la page “Billie Eilish Shop | Billie Eilish” et usurpait peut-être l'identité de Fakeshop.
PhishDestroy répertorie billieeilishdirect.shop comme suspect. Il a été vérifié par les moteurs de sécurité 92 ; les verdicts automatisés peuvent changer. La surveillance se poursuit. Observé: 2026-10-16 17:28:48 UTC
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.