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

johnybee.pl

“Strona główna - MadaSweet”

Bureau d’enregistrement
home.pl sp. z o.o
Resolved IP
89.161.196.246
Registered
10/10/2018
PhishDestroy assessment Critique
Disponibilité Dernier actif connu Dernière observation d'accessibilité stockée Observé · HTTP probe
Détections VirusTotal : 14/92
OTX: 4 refs 11/10/2026
API
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.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Résumé du rapport

Hameçonnage: johnybee.pl — Dernier actif connu (HTTP 301). Résumé des preuves: VirusTotal 14/92 (alphaMountain.ai, BitDefender, CRDF, DNS8, Fortinet)…

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

Source evidenceVirusTotal 14 / 92 · OTX 4 references 5 sources

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

Analysis

Critique
VirusTotal
14 / 92
OTX
4 community refs
Page captures
4

PhishDestroy threat report

Overview

johnybee.pl is a Polish domain on the PhishDestroy blocklist. Its page carries the Polish title "Strona główna - MadaSweet" ("Home page - MadaSweet"), so it is aimed at Polish-speaking visitors. PhishDestroy first saw it on 2026-10-11. On 2026-10-19 the site was still online and its content now redirects visitors elsewhere. The page title names a brand, MadaSweet, that has nothing to do with the domain name johnybee. No specific scam type has been confirmed for this domain.

How the scam works

We have not tied this domain to a specific scheme. Two things raise the risk. A long-standing domain now shows content for an unrelated brand, and it sends visitors on to another destination. Redirects like this mean the page you end up on is not the one the address suggests. That destination can change at any time and may ask for logins, payment details or crypto transactions. Treat anything requested after landing here as untrusted.

Evidence

On 2026-10-12, 14 of 92 VirusTotal engines flagged the domain. They include alphaMountain.ai, BitDefender, CRDF, DNS8, Fortinet, G-Data, Gridinsoft and Kaspersky. That is a meaningful minority, and it spans several independent established vendors rather than a single source. The domain also appears in four AlienVault OTX threat pulses, so other researchers have reported it. Among blocklists, only PhishDestroy lists it so far.

Infrastructure

The domain was registered on 2018-10-10, about eight years before PhishDestroy detected it. That is not the profile of a freshly registered throwaway domain. It is closer to an older site whose content has changed. Registration, hosting and the TLS certificate all come from home.pl sp. z o.o., on a Polish network. The certificate is a standard domain-validated one, so it proves only that someone controls the domain, not who runs it.

What to do

Do not follow the redirect or enter anything on pages reached through this domain. If you typed a password there, change it, along with any reused copies, and turn on two-factor authentication. If you entered card or bank details, contact your bank to block the card and dispute charges. If you made a payment or crypto transfer, keep the transaction details and report it to your bank or the police. Security teams should block the domain and its redirect targets at DNS and proxy level, and check logs for users who visited it after 2026-10-11.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-08-18T11:16:29Z

Observé: · Retrieved:

Uuid
01a01496-3264-7679-8b52-385f69c7cbc7
Final url
https://www.johnybee.pl/
Statut
200
Redirigé
https-only
Redirects
[
    {
        "to": "https://www.johnybee.pl/",
        "from": "http://www.johnybee.pl/",
        "status": 307
    }
]
Ip
51.77.157.57
Ptr
vps-2d4512cf.vps.ovh.net
Contacted IP addresses
[
    "51.77.157.57"
]
Asns
[
    "16276"
]
Countries
[
    "FR"
]
Document hash
0bae6089419ea8f95d7ddf86ba40a6b6c8ae6fca852dd9b70351f869e19df27b
Tls
{
    "san": [
        "www.johnybee.pl"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR2",
    "subject": "www.johnybee.pl",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-16T01:49:59Z",
    "valid_from": "2026-08-18T01:50:00Z"
}
Domain age days
357
Apex age days
357
Tls age days
0
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": -21,
        "malicious": false
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html",
    "strict-transport-security": "max-age=31536000"
}
Cloudflare Radar · 2026-10-12T09:49:02Z

Observé: · Retrieved:

Uuid
fb2a4640-1844-4de0-a760-67399f79df69
Final url
https://madasweet.pl/
Statut
200
Redirigé
off-domain
History
[
    {
        "url": "https://johnybee.pl/",
        "status": 301
    },
    {
        "url": "https://madasweet.pl/",
        "status": 200
    }
]
DOM structure hash
657492ec1d24ae9f35ed5bef8ef5ee343d0d04c44398d02c12e56e561ae5398b
Document hash
fe31dd7d599972b3325e1afc524dcb99c4a33725852c0f344646340dfcda5c3c
Domain risks
[
    "Food & Drink",
    "Society & Lifestyle"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "madasweet.pl",
        "type": "A",
        "value": "89.161.196.246"
    }
]
Dnssec valid
false
Ip
89.161.196.246
Registration record
{
    "registrar": "home.pl sp. z o.o.",
    "created": "2007-05-11T12:31:13Z",
    "updated": "2022-03-30T06:50:02Z",
    "expires": "2027-05-11T12:31:13Z",
    "nameservers": [
        "dns.home.pl",
        "dns2.home.pl",
        "dns3.home.pl"
    ]
}
VirusTotal · 2026-10-19T23:40:02Z

Observé: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 44,
    "malicious": 14,
    "suspicious": 1,
    "undetected": 33
}
Vendor labels
{
    "CRDF": "malicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "phishing and other frauds. business and economy"
}
First seen
2024-06-25T09:07:01Z
DNS records
[
    {
        "ttl": 60,
        "type": "TXT",
        "value": "v=spf1 mx a ptr ~all"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "dns3.home.pl"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "dns2.home.pl"
    },
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "admin.home.pl",
        "value": "dns.home.pl"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "dns.home.pl"
    },
    {
        "ttl": 3600,
        "type": "MX",
        "value": "johnybee.pl",
        "priority": 10
    },
    {
        "ttl": 60,
        "type": "A",
        "value": "89.161.196.246"
    }
]
Dns at
2026-10-19T23:40:19Z
Jarm
2ad2ad16d2ad2ad00042d42d000000df133019600a83abfb096ff3e86cd79d
Certificate
{
    "san": [
        "johnybee.pl",
        "www.johnybee.pl"
    ],
    "issuer": "home.pl sp. z o.o. / home pl DV TLS G2 R36 CA",
    "serial": "c49119e0287bfaacff8307b66417844",
    "sha256": "c070c8ba51bd0116357868bc80354cb5584556c23885f16aa436a03fb42b9054",
    "subject": "johnybee.pl",
    "valid_to": "2027-02-11T05:42:53Z",
    "valid_from": "2026-07-27T05:42:54Z"
}
Registration record
{
    "dnssec": "Unsigned"
}
Registry data
{
    "events": {
        "expiration": "2029-10-10T16:10:38Z",
        "last changed": "2026-09-10T06:10:03Z",
        "registration": "2018-10-10T16:10:38Z",
        "last update of RDAP database": "2026-10-09T11:18:16Z"
    },
    "registrar": "home.pl sp. z o.o."
}
Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Capture enregistrée · 4 captures

Domain details

Domaine
URLScan verdict Analyse terminée score 0 report ↗
Réputation de l’IP abuse score 0/100 0 reports checked 12/10/2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainesdrainerfraudlivemonthlyphishdestroyphishingscam
Bureau d’enregistrement home.pl sp. z o.o PL(PL)
Registre de l'ICANNICANN Lookup (RDAP) →
EnregistrementCréé 10/10/2018 — Expires 10/10/2029
Statut HTTP301 Moved Permanently
Détails techniquesProvenance & timestamps
Première détection11/10/2026
DOM Analysisanalyzed 12/10/2026score 98/100
Submitted URLhttp://www.johnybee.pl/
Favicon Hash
Observed page title
Strona główna - MadaSweet
Certificat TLS
Émis par home.pl sp. z o.o. / home pl DV TLS G2 R36 CA · stored validity ends in 112 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
89.161.196.246
Network ASN
AS12824
Organization
home.pl S.A.
Observed location
Szczecin, PL
Server header
nginx

Serveurs de noms 1

  • dns3.home.pl

Mail routing 1 MX record

  • johnybee.plpriority 10

Location describes the IP network.

Certificat TLS

Issuer
home.pl sp. z o.o. / home pl DV TLS G2 R36 CA
Valid from
2026-07-27 05:42:54
Valid until
2027-02-11 05:42:53
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-12 10:02:09 UTC
Collection source
PhishDestroy collector
Certificate fingerprintc070c8ba51bd0116357868bc80354cb5584556c23885f16aa436a03fb42b9054
Certificate names · 1 SANs
  • www.johnybee.pl

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-21 10:30:28 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-21 10:30:28 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-21 10:30:28 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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.johnybee.plDomain record

The original observation time is not recorded for these hostnames.

Technologies · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
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 First positive detection Previous stored snapshot: 14 detections
alphaMountain.ai
BitDefender
CRDF
DNS8
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot

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 johnybee.pl · checked Oct 12, 2026

38
Poor
Performance
FCP
2.14s
First Contentful Paint
LCP
9.99s
Largest Contentful Paint
CLS
0.57
Cumulative Layout Shift
TBT
246ms
Total Blocking Time
SI
8.95s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable 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.

Stored observation history9

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

    http_redirect

  2. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

Earlier observations 4
  1. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. AlienVault OTX

    4 community references

    View source
  3. VirusTotal

    14/92 engine detections

    View source
  4. Added to PhishDestroy

    johnybee.pl

    View source

Check for cloaking

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

johnybee.pl

Données factuelles et rapports externes

Référencement naturel et nom de domaine
Analyse approfondie
Help & reporting

Ce site vous a-t-il affecté ?

4 evidence signal groups linked 0 stored notification records Dernier actif connu

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.

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 johnybee.pl)
  • 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/johnybee.pl"
  title="PhishDestroy threat report for johnybee.pl"
  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>