VirusTotal
17 / 89 engine detections
Bericht öffnen“500 Internal Server Error”
Phishing: kosmetyk-pl.shop — Erreichbar · Zugang eingeschränkt (HTTP 403). Zusammenfassung der Beweislage: VirusTotal 17/89 (alphaMountain.ai, BitDefender…
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
17 / 89 engine detections
Bericht öffnenSchädlich
Bericht öffnenDBL_PHISH
5 community references
Bericht öffnenNo threat flag
Bericht öffnenNo malicious flag
Bericht öffnenResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
kosmetyk-pl.shop is an impersonation phishing site. Its name combines the Polish word for cosmetics with a country tag on a .shop domain, so it is pitched at Polish-speaking shoppers looking for beauty products. PhishDestroy first saw it on 2026-09-13. As of 2026-10-19 the domain was still live and its content was reachable behind protection.
Impersonation shops of this kind copy the look of a legitimate retailer or brand. They then steer visitors to a checkout or account page where card numbers, billing addresses, phone numbers and passwords are harvested. The victim may pay for goods that never arrive, have the card reused for other charges, and see the stolen login tried on other services. When checked, the page returned the title "500 Internal Server Error", which differs from the impersonation content we classified.
On 2026-09-21, 17 of 89 VirusTotal engines flagged the domain. Detections came from security vendors including BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, alphaMountain.ai, CRDF and CyRadar. Spamhaus lists it in its domain blocklist with the DBL_PHISH tag, which means mail filters relying on that feed will treat links to it as phishing. The domain also appears in five AlienVault OTX threat pulses and is on the PhishDestroy blocklist.
The domain was registered through Spaceship, Inc. on 2026-07-08, about two months before PhishDestroy detected it. That gap leaves room for setup and early promotion before anyone flagged it. Traffic is routed through Cloudflare, Inc. at an address geolocated to Canada, so the true origin server is hidden behind the proxy. The TLS certificate from Google Trust Services is the standard kind issued at that edge and says nothing about legitimacy.
If you entered card details on this site, call your bank and block the card, then dispute any charges you do not recognise. If you created an account or typed a password there, change that password everywhere you reused it and turn on two-factor authentication. Expect follow-up phishing by email or SMS that mentions your order, and do not click links in such messages. Security teams should block the domain at DNS and web proxies and add it to mail filtering if the Spamhaus feed is not already in use. Report any lures pointing to it so the hosting and registrar side can act.
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.
Die Edge-IP-Reputation wird dieser Domäne nicht zugeordnet.
bethany.ns.cloudflare.comLocation describes the IP network.
82870696ef08579cbd4d71516bdf14938179acf94c324bb47c18539446ad69deSaved 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 kosmetyk-pl.shop · checked Sep 13, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
alive_content: raw=waf_403; http=403; via=https_proxy; server=cloudflare
kosmetyk-pl.shop
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unbekannt→protected
http_access_restricted · Cloudflare · access_restriction
Unbekannt→protected
http_access_restricted · Cloudflare · access_restriction
Unbekannt→protected
http_access_restricted · Cloudflare · access_restriction
Unbekannt→protected
http_access_restricted · Cloudflare · access_restriction
Unbekannt→protected
http_access_restricted · Cloudflare · access_restriction
Unbekannt→protected
http_access_restricted · Cloudflare · access_restriction
Unbekannt→protected
http_access_restricted · Cloudflare · access_restriction
Unbekannt→protected
http_access_restricted · Cloudflare · access_restriction
Unbekannt→protected
http_access_restricted · Cloudflare · access_restriction
Unbekannt→protected
http_access_restricted · Cloudflare · access_restriction
Unbekannt→protected
http_access_restricted · Cloudflare · access_restriction
Unbekannt→protected
http_access_restricted · Cloudflare · access_restriction
Unbekannt→protected
http_access_restricted · Cloudflare · access_restriction
Unbekannt→protected
http_access_restricted · Cloudflare · access_restriction
Unbekannt→protected
http_access_restricted · Cloudflare · access_restriction
Unbekannt→protected
http_access_restricted · Cloudflare · access_restriction
Unbekannt→protected
http_access_restricted · Cloudflare · access_restriction
Unbekannt→protected
http_access_restricted · Cloudflare · access_restriction
Unbekannt→protected
http_access_restricted · Cloudflare · access_restriction
5 community references
View sourceNo threat flag
View source17/89 engine detections
View sourcePage captured
View sourcekosmetyk-pl.shop
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
Wenn Sie Kontoanmeldeinformationen, persönliche oder Zahlungsinformationen eingegeben oder eine Datei von dieser Domain heruntergeladen haben, ergreifen Sie sofort Maßnahmen. Nachfolgend finden Sie Ressourcen, die Ihnen helfen, den Vorfall zu melden und sich zu schützen.
Wählen Sie Ihr Land aus, um Offizielle Kontakte im Bereich Cyberkriminalität oder einen Beschwerdeentwurf erstellen → zu erhalten.
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 ↗
kosmetyk-pl.shop)Auch wenn dir nicht alle Details bekannt sind — trotzdem Anzeige erstatten. Auch unvollständige Informationen sind für die Ermittlungen hilfreich.
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
Bedrohungsanalyse anhand gespeicherter Blocklisten, WHOIS, DNS und öffentlicher Scan-Beweise
Jetzt scannenMelden Sie verdächtige Domains an unsere Bedrohungsdatenbank – schützen Sie die Community
MeldenAktuelle Phishing-Meldungen und beobachtete Verfügbarkeitsänderungen
ÜberwachenBeobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt
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.