VirusTotal
14 / 92
“Strona główna - MadaSweet”
The domain johnybee.pl returned an HTTP status code 301 on 2026-10-12, documenting a redirect at that time. Additionally, the domain was first observed in records on 2026-10-11, providing a recent timeline for these observations.
On 2026-10-12, the HTTP status for johnybee.pl was recorded as 301. According to VirusTotal on 2026-10-09, there were 14 detections out of 92 total scanners. OTX referenced johnybee.pl in 4 pulses as of 2026-10-12. The domain is listed in the PhishDestroy internal catalogue, and its registration date is 2018-10-10.
The VirusTotal record contains a scanner-based measurement of detections, which documents how the domain was evaluated by multiple external engines. OTX provides intelligence entries that reflect how johnybee.pl has been referenced in curated security pulses. The HTTP status record offers a technical observation of the domain’s response at a specific time, which is useful for understanding its network behavior.
It is advisable to retain the VirusTotal, OTX, and HTTP status records for johnybee.pl for future reference. Comparing these records over time can help track changes in detections, intelligence entries, and technical responses. Further monitoring of the domain using these sources is recommended to maintain an up-to-date security profile.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
IdeaWebServer/6.4.2Scanner note: redirect: raw=redirect_301; http=301; via=https_proxy; location=https://madasweet.pl; server=IdeaWebServer/6.4.2
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.
Google PageSpeed Insights — mobile performance audit of johnybee.pl · checked Oct 12, 2026
89.161.196.246. 8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive