Aller au rapport de sécurité
Sécurité des domaines et renseignements sur les menaces
milky.beauty favicon

milky.beauty

“Milky | Best lip combo”

Bureau d’enregistrement
Name.com
Resolved IP
63.176.8.218
Registered
31/12/2025
PhishDestroy assessment Critique
Disponibilité Dernier actif connu Dernière observation d'accessibilité stockée Observé · HTTP probe
Détections VirusTotal : 4/91 URLQuery threat systems: 2 alerts Type d'arnaque : Credential Phishing
OTX: 16 refs 28/05/2026 1 Report Sent CDN
API
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 4. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@name.com. The latest stored availability evidence still shows the domain reachable; 4 months 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.

Elapsed since first report
4 months
Reports sent
1
Latest case ID
PD-20260528-AE6BCE
Current status
HTTP 200 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
URLQuery
threat alerts
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Résumé du rapport

Vol d’identifiants: milky.beauty — Dernier actif connu (HTTP 200). Résumé des preuves: VirusTotal 4/91 (alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet…

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

Source evidenceVirusTotal 4 / 91 · OTX 16 references 6 sources

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Renseignements sur la sécurité réseau
Threat Detection Systems 2 alerts
Detection System Indicator Verdict Alert
Nextron YARA rules i.ibb.co/ztwhp5rd/img-2224.gif malware Detects files with GIF headers and format anomalies - which means that this image could be an obfuscated file of a different type
DNS4EU milky.beauty malicious Sinkholed

Analysis

Critique
VirusTotal
4 / 91
OTX
16 community refs
Page captures
3

PhishDestroy threat report

This domain is flagged as an elevated-risk credential harvesting phishing site targeting users through cosmetic product lures. Analysis indicates the infrastructure was designed to mimic legitimate beauty retailers, using social engineering tactics to collect login credentials or financial information under the pretense of exclusive offers. Infrastructure analysis reveals the domain milky.beauty resolved to IP address 63.176.8.218 and was registered through Name.com, Inc. on December 31, 2025. The site employed a Let's Encrypt SSL certificate to present a false sense of security. Detection metrics show 6 out of 95 security vendors on VirusTotal flagged the domain as malicious, while it appeared on one security blocklist prior to takedown. The page title 'Milky | Best lip combo' suggests a thematic approach to lure victims with fake product promotions. Mitigation for credential harvesting threats involves immediate domain blacklisting across enterprise security gateways. Network administrators should block the IP 63.176.8.218 at the perimeter and monitor for related indicators of compromise. End users should be educated on verifying domain legitimacy before entering credentials, particularly for offers that appear too good to be genuine. Security teams are advised to check logs for connections to this IP and domain during the exposure window.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Capture enregistrée · 3 captures

Observed page title
Milky | Best lip combo
Certificat TLS
Émis par Let's Encrypt · stored validity ends in 33 days

Domain details

Domaine
URLScan verdict Analyse terminée score 0 report ↗
IP Context Netlify shared edge origin IP hidden La réputation Edge-IP n’est pas attribuée à ce domaine.
OTX tags 2026-05activeall-domainsblocklistcontentcryptodomainesdrainerfraudlivemonthlyphishdestroyphishingscam
Bureau d’enregistrement Name.com US(US)
Contact anti-abusabuse@name.com
Registre de l'ICANNICANN Lookup (RDAP) →
EnregistrementCréé 31/12/2025 (293d) — Expires 31/12/2026
Statut HTTP200
Détails techniquesProvenance & timestamps
Première détection28/05/2026
DOM Analysisanalyzed 01/06/2026score 81/100
Submitted URLhttps://milky.beauty/
Favicon Hash
ID du dossier
ICANN OVERSIGHT

Contexte de l’accréditation et du RAA

Registrar accreditation and DNS abuse obligations

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.

Accreditation is a contract, not a safety certification.

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.

Accountability draft Rien n’est envoyé automatiquement.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
63.176.8.218
Network ASN
AS16509
Organization
Amazon.com, Inc.
Observed location
Frankfurt am Main, DE
Server header
Netlify

La réputation Edge-IP n’est pas attribuée à ce domaine.

Serveurs de noms 4

  • dns1.p03.nsone.net
  • dns2.p03.nsone.net
  • dns3.p03.nsone.net
  • dns4.p03.nsone.net

Location describes the IP network.

Certificat TLS

Issuer
Let's Encrypt
Valid from
2026-08-28 08:15:15
Valid until
2026-11-26 08:15:14
Validity
Within stored validity dates
Collection time
2026-10-10 04:03:32 UTC
Collection source
PhishDestroy collector
Certificate fingerprint75faec0728c51ebf94945f15f5524a583d0e18638a8526fec7b3c03e40b2ae44

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-19 22:31:31 UTC

Primary outcome Contenu actif reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Contenu actif Ordinary HTTP content served 90% 2026-10-19 22:31:31 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-19 22:35:35 UTC last content: 2026-10-19 22:31:31 UTC
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

4 / Les fournisseurs de sécurité 91 ont signalé ce domaine
View on VT
Last analyzed Previous stored snapshot: 6 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Fortinet
Gridinsoft

Preuves archivées

Wayback Machine Snapshot
Un instantané historique est disponible pour l’examen des preuves
View Archive
Analyse des performances du site

Google PageSpeed Insights — mobile performance audit of milky.beauty · checked Jun 26, 2026

60
Needs Work
Performance
FCP
0.77s
First Contentful Paint
LCP
61.17s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
342ms
Total Blocking Time
SI
7.17s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

No cloaking flag in this check

alive_content: raw=ok; http=200; via=https_proxy; server=Netlify

milky.beauty
Stored observation history18

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→live_content

    content_served

  2. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  3. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  4. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  5. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

Earlier observations 13
  1. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  2. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  3. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  4. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  5. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  6. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  7. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  8. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  9. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  10. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  11. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  12. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  13. VirusTotal · Detection count

    3→6

Recorded activity

6 entries
  1. AlienVault OTX

    16 community references

    View source
  2. VirusTotal

    4/91 engine detections

    View source
  3. Google Safe Browsing

    No threat flag

    View source
  4. URLScan

    Page captured

    View source
  5. Added to PhishDestroy

    milky.beauty

    View source
  6. Abuse report sent

    PD-20260528-AE6BCE

    abuse@name.com

Signalements communautaires

Signalé par 1 membre de la communauté ; première observation le 28/05/2026

Signalements enregistrés
1
URL signalées uniques
1
Accepté1

Données factuelles et rapports externes

Instantané des preuves transmises
Sent: Ledger records: 1 Case ID: PD-20260528-AE6BCE Recipient: abuse@name.com
Page title stored with report: Milky | Best lip combo
PDF notice generated Notice text archived (1,248 chars)
Abuse notice text as sent to the provider
Policy Violations:
Acceptable Use Policy (AUP): The domain milky.beauty is engaged in phishing activities, which directly contravenes the AUP by facilitating fraud and deception.
Terms of Service (TOS): The registrar reserves the right to suspend or terminate services for violations, and the use of this domain for illegal activities constitutes a clear breach of the TOS.
Applicable Laws (US):
Computer Fraud and Abuse Act (18 U.S.C. § 1030): This law prohibits unauthorized access to computers and the use of such access to commit fraud, which is applicable to the phishing activities associated with milky.beauty.
CAN-SPAM Act (15 U.S.C. § 7701 et seq.): This act addresses the sending of deceptive commercial emails, which is relevant as phishing often involves misleading email communications.
Wire Fraud (18 U.S.C. § 1343): This statute criminalizes schemes to defraud individuals or entities via electronic communications, which is applicable to the phishing schemes conducted through this domain.
Regulatory Note: Failure to take immediate action against this domain may result in regulatory scrutiny and potential liability under federal and state laws. Compliance with your AUP and TOS is not only a best practice but a legal obligation.
Référencement naturel et nom de domaine
Analyse approfondie
Help & reporting

Ce site vous a-t-il affecté ?

6 evidence signal groups linked 1 stored notification records Dernier actif connu
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.

Official reporting routes

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 milky.beauty)
  • 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

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
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA 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/milky.beauty"
  title="PhishDestroy threat report for milky.beauty"
  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>