セキュリティレポートへ移動
ドメインのセキュリティと脅威インテリジェンス
johnybee.pl favicon

johnybee.pl

“Strona główna - MadaSweet”

レジストラ
home.pl sp. z o.o
Resolved IP
89.161.196.246
Registered
2018年10月10日
PhishDestroy assessment クリティカル
可用性 最後に確認されたアクティブな状態 最新の保存された到達可能性の観測 観測された · HTTP probe
VirusTotal 検出数: 14/92
OTX: 4 refs 2026年10月11日
API
このドメインは悪意のあるものとして報告されています
検出を報告するセキュリティ エンジン: 14。 細心の注意を払ってください — 資格情報や個人情報を入力しないでください。
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
レポート概要

フィッシング: johnybee.pl — 最後に確認されたアクティブな状態 (HTTP 301). 証拠の概要: VirusTotal 14/92 (alphaMountain.ai, BitDefender, CRDF, DNS8, Fortinet); PhishDestroy score 100/100.…

元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。

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

クリティカル
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

観測された: · Retrieved:

Uuid
01a01496-3264-7679-8b52-385f69c7cbc7
Final url
https://www.johnybee.pl/
ステータス
200
リダイレクト
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

観測された: · Retrieved:

Uuid
fb2a4640-1844-4de0-a760-67399f79df69
Final url
https://madasweet.pl/
ステータス
200
リダイレクト
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

観測された: · 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

保存済みキャプチャ · 4 captures

Domain details

ドメイン
URLScan verdict 分析完了 score 0 report ↗
IPレピュテーション abuse score 0/100 0 reports checked 2026年10月12日
OTX tags 2026-10activeall-domainsblocklistcontentcryptoドメインdrainerfraudlivemonthlyphishdestroyphishingscam
レジストラ home.pl sp. z o.o PL(PL)
登録情報作成日 2018年10月10日 — Expires 2029年10月10日
HTTPステータス301 Moved Permanently
技術詳細Provenance & timestamps
初確認2026年10月11日
DOM Analysisanalyzed 2026年10月12日score 98/100
Submitted URLhttp://www.johnybee.pl/
Favicon Hash
Observed page title
Strona główna - MadaSweet
TLS証明書
発行者 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

ネームサーバー 1

  • dns3.home.pl

Mail routing 1 MX record

  • johnybee.plpriority 10

Location describes the IP network.

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 不明
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.

使用技術 · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
このドメインを報告する 証拠を提出し、他の人を守る手助けをしましょう

VirusTotalによる分析

14 / 92 セキュリティ ベンダーがこのドメインにフラグを立てました
View on VT
Last analyzed First positive detection Previous stored snapshot: 14 detections
alphaMountain.ai
BitDefender
CRDF
DNS8
Fortinet
G-Data
Gridinsoft
カスペルスキー
Lionic
Seclookup
SOCRadar
ソフォス
VIPRE
Webroot

アーカイブ済み証拠

Wayback Machine Snapshot
過去のスナップショットは証拠のレビューに利用可能です
View Archive
サイトパフォーマンス分析

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

    不明→redirected

    http_redirect

  2. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  3. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  4. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  5. Availability monitor · Recorded state

    不明→redirected

    http_redirect

Earlier observations 4
  1. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  2. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  3. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  4. Availability monitor · Recorded state

    不明→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

証拠および外部報告書

詳細な分析
Help & reporting

このサイトによって何か影響を受けましたか?

4 evidence signal groups linked 0 stored notification records 最後に確認されたアクティブな状態

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.

アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。

Official reporting routes

復旧を装った詐欺に注意! 犯罪者は、捜査員、弁護士、または回収業者を装い、被害者に再び連絡を取る可能性があります。 前払い料金を支払ったり、資格情報を共有したりしないでください。 回復詐欺について詳しくはこちら →

お住まいの地域の当局へ報告してください

サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。

97か国のディレクトリ

Template-based draft · optional AI wording assistance requires separate consent

AI 支援ドラフト — インシデントの詳細は AI プロバイダーによって処理されます · 自分で確認して送信する
After a phishing incident

被害者への推奨事項とアドバイス

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.

  • すべてのパスワードを変更する — メール、Exchangeアカウントなど、同じパスワードを使用しているものすべて
  • 2段階認証を有効にする 認証アプリ(SMSではない)を使用する。SMSによる復旧機能を無効にする
  • カードの凍結 フィッシングサイトに銀行口座情報を入力してしまった場合

レポート作成のために、どのような情報を収集すべきでしょうか?

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.
  • 正確な日時 — 各取引および詐欺師との最初の接触について
  • スクリーンショット — 詐欺サイト、チャットメッセージ、メール、ウォレットでの取引、ソーシャルメディア
  • すべてのURLおよびドメイン 詐欺師が使用した(以下を含む) johnybee.pl)
  • コミュニケーション — 詐欺師が使用したメール、テキストメッセージ、電話番号、ユーザー名

たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。

この詐欺はどこに通報すればいいですか?

  • FBI IC3 — インターネット犯罪通報センター(米国連邦政府の通報窓口)
  • ユーロポール — 欧州におけるサイバー犯罪の報告(EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される

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?

  • 偽のウェブサイト — 正規サイトのドメインをわずかに変更した、ピクセル単位で完璧に再現されたクローンサイト
  • pig butchering — TelegramやWhatsApp、出会い系アプリを通じて数週間にわたって信頼関係を築き、その後、金銭をだまし取られる
  • 詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AIを利用した詐欺 — ディープフェイク、自動化されたフィッシング、AI生成サイトにより、詐欺の発見が難しくなっている

今後、どうすれば身を守ることができるでしょうか?

  • 公式サイトをブックマークする — メール、DM、広告に含まれるリンクは絶対にクリックしないでください
  • ドメインの確認 — 確認する PhishDestroy 操作を行う前に、HTTPS、スペル、ドメインの登録期間を確認してください。
  • 「良すぎて怪しい」=詐欺 — 確実なリターン、有名人の推薦、差し迫った締め切り

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

最新情報を入手し、安全を確保しましょう

リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください

リアルタイム脅威情報フィード この掲載情報について異議を申し立てる
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

このレポートを埋め込む

この脅威情報を、ご自身のウェブサイトやブログで共有してください

embed.html
<iframe
  src="https://phishdestroy.io/ja/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>