VirusTotal
14 / 92 engine detections
Bericht öffnen“Strona główna - MadaSweet”
Phishing: johnybee.pl — Letzter bekanntermaßen aktiv (HTTP 301). Zusammenfassung der Beweislage: VirusTotal 14/92 (alphaMountain.ai, BitDefender, CRDF, DNS8…
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
14 / 92 engine detections
Bericht öffnen4 community references
Bericht öffnenprovider verdict: clean
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
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.
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.
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.
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.
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.
Stored page, network and scanner observations, grouped by source and observation time.
Beobachtet: · Retrieved:
| Uuid | 01a01496-3264-7679-8b52-385f69c7cbc7 |
|---|---|
| Final url | https://www.johnybee.pl/ |
| Status | 200 |
| Weitergeleitet | 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"
} |
Beobachtet: · Retrieved:
| Uuid | fb2a4640-1844-4de0-a760-67399f79df69 |
|---|---|
| Final url | https://madasweet.pl/ |
| Status | 200 |
| Weitergeleitet | 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"
]
} |
Beobachtet: · 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."
} |
dns3.home.pljohnybee.plpriority 10Location describes the IP network.
c070c8ba51bd0116357868bc80354cb5584556c23885f16aa436a03fb42b9054www.johnybee.plSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.johnybee.plDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of johnybee.pl · checked Oct 12, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
No threat flag
View source4 community references
View source14/92 engine detections
View sourcejohnybee.pl
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
johnybee.pl
Listed 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 ↗
johnybee.pl)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.