VirusTotal
13 / 92 engine detections
Apri il rapporto“Taxi Iława - Tania i Bezpieczna Taksówka - Jeziorak Taxi”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@lh.pl.
The latest stored availability evidence still shows the domain reachable; 10 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Imitazione di Google: jeziorak-taxi.pl — Ultimo attivo conosciuto (HTTP 200). Riepilogo delle prove: VirusTotal 13/92 (ADMINUSLabs, alphaMountain.ai…
L’analisi dettagliata di PhishDestroy AI resta in inglese per preservare il rapporto forense originale.
13 / 92 engine detections
Apri il rapporto2 det.
Apri il rapporto34 community references
Apri il rapportoprovider verdict: clean
Apri il rapportoNo threat flag
Apri il rapportoNo malicious flag
Apri il rapportoResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
jeziorak-taxi.pl presents itself as a cheap, safe taxi service in Iława, Poland, under the title "Taxi Iława - Tania i Bezpieczna Taksówka - Jeziorak Taxi". PhishDestroy classifies it as an impersonation phishing page. Its likely targets are locals and visitors searching for a cab around Iława and Lake Jeziorak. We first flagged it on 2026-10-10, and the site was still online with live content on 2026-10-19. The page title reads like an ordinary local taxi business, while our classification is impersonation.
Impersonation pages borrow the name and look of a real business so that visitors trust them with contact details, phone numbers or payments. For a taxi brand, that usually means a booking form, a phone number that routes to someone other than the genuine operator, or a request for an advance payment or card details to "confirm" a ride. The victim can lose the prepaid fare, expose payment card data, or hand over personal information that later feeds further fraud. The friendly local-taxi branding is what makes the request feel routine.
On 2026-10-12, 13 of 92 VirusTotal engines flagged the domain, including BitDefender, Fortinet, G-Data, Forcepoint ThreatSeeker, alphaMountain.ai, ADMINUSLabs, CyRadar and Chong Lua Dao. That is a minority of engines, but several of them are mainstream security vendors acting independently. The domain also appears in 34 AlienVault OTX threat pulses, meaning many researchers have tied it to malicious activity. Among blocklists, it is currently listed by PhishDestroy.
The domain was registered on 2018-03-20 through home.pl sp. z o.o., more than eight years before we detected it. A name that old does not fit a throwaway phishing domain. It may be a long-standing business site that has been compromised or repurposed, though that is not confirmed. It is hosted in Poland on the LH.pl network, which matches the local targeting.
If you booked a ride or paid through this site, contact your bank or card issuer immediately, report the transaction as fraud and ask about a chargeback. If you entered card details, have the card blocked and reissued. Watch for follow-up calls or texts that use the details you submitted. If you reused a password on any account you created there, change it elsewhere. Defenders should block the domain, search proxy and DNS logs for past visits, and warn users in the Iława region who may run into it while looking for a taxi.
Stored page, network and scanner observations, grouped by source and observation time.
Osservato: · Retrieved:
| Uuid | 01a127d2-163f-73ac-a5a4-5551629ebac2 |
|---|---|
| Final url | https://jeziorak-taxi.pl/ |
| Stato | 200 |
| Reindirizzato | https-only |
| Redirects | [
{
"to": "https://jeziorak-taxi.pl/",
"from": "http://jeziorak-taxi.pl/",
"status": 307
}
] |
| Ip | 5.252.231.173 |
| Ptr | d5.thecamels.org |
| Contacted domains | [
"cdn.trustindex.io",
"s.w.org",
"www.googletagmanager.com",
"region1.google-analytics.com",
"consent.cookiebot.com"
] |
| Contacted IP addresses | [
"216.239.32.36",
"23.36.162.220",
"192.0.77.48",
"142.251.110.97",
"54.192.35.57",
"5.252.231.173"
] |
| Asns | [
"15169",
"20940",
"2635",
"16509",
"203417"
] |
| Countries | [
"US",
"DE",
"PL"
] |
| Document hash | 8ae352033d709597cd8b97d0f63fe884765c65f315c56f28b240139b3cfef2cd |
| Script hashes | [
"cb6f2d32c49d1c2b25e9ffc9aaafa3f83075346c01bcd4ae6eb187392a4292cf",
"5274f11e6fb32ae0cf2dfb9f8043272865c397a7c4223b4cfa7d50ea52fbde89",
"d09012005a283292d543b53dd988d15275c61904c97ebc45de2110b3d2f7d9e1",
"fdbac8131b3ff1d5b523a0d8f1373ee03f0d4fac66b8928645adb243841b7bac",
"454e41f5c4f3b318bcf8a71a296121220e4912eff7fa43c0896de0f6936b72de",
"b7a27a4b4abfc300eaf7d9151afeef8df2663d98586e38f59f91bbe98ef30af7",
"ca1f7ccb6ebf20e7d08cadca4fc3444686f39303e9f08a555e37b5a603e85d13",
"f9b60ae2f2938c589960ef00d9b9a644f0847f7183f597cdc3fbf8cfe904c552",
"34bbd1c367ffc7d80fcff86c7e5f8777e70f4911bb324e8ecfc7dd3604a96e68",
"9aa9bb8be2b834059533ce5de7eed3a662ad3d3e70643bbe5f75265075e9bd28"
] |
| Globals | [
"jQuery",
"dataLayer",
"webpackChunkelementorFrontend",
"elementorModules",
"elementorFrontendConfig",
"elementorFrontend",
"Sticky",
"Swiper",
"webpackChunkelementor_pro",
"wp",
"ElementorProFrontendConfig",
"elementorProFrontend",
"_wpemojiSettings",
"tiWidgetInstances",
"Trustindex",
"TrustindexWidget",
"TrustindexReviewWidget",
"TrustindexSliderWidget",
"TrustindexMasonryWidget",
"TrustindexPopupWidget",
"TrustindexTopRatedWidget",
"TrustindexFomoWidget",
"TrustindexCloseModule",
"TrustindexReadMoreModule",
"TrustindexLoadMoreModule",
"TrustindexHeaderModule",
"TrustindexReviewImageModule",
"TrustindexLightboxModule",
"TrustindexAiSummaryModule",
"TrustindexDarkModeModule",
"tiElementToWaitForVisibility",
"tiElementToWaitForActivity",
"renderTrustindexWidgets",
"DialogsManager",
"twemoji",
"google_tag_data",
"google_tag_manager",
"onYouTubeIframeAPIReady",
"CookieControl",
"__uspapi"
] |
| Cookie | [
"CookieConsent",
"_ga_FKKVMBF964",
"_ga"
] |
| Storage keys | [
"elementor",
"wpEmojiSettingsSupports"
] |
| Tls | {
"san": [
"*.jeziorak-taxi.pl",
"jeziorak-taxi.pl"
],
"cipher": "AES_256_GCM",
"issuer": "YE2",
"subject": "*.jeziorak-taxi.pl",
"protocol": "TLS 1.3",
"valid_to": "2026-11-23T05:24:54Z",
"valid_from": "2026-08-25T05:24:55Z"
} |
| Domain age days | 2797 |
| Apex age days | 2797 |
| Tls age days | 46 |
| Tls valid days | 89 |
| Requests | 100 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 88,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "Apache/2",
"content-type": "text/html; charset=UTF-8"
} |
Osservato: · Retrieved:
| Uuid | 82e2f5ef-f904-487f-b09f-12c49ab8db89 |
|---|---|
| Final url | https://jeziorak-taxi.pl/ |
| Stato | 200 |
| History | [
{
"url": "https://jeziorak-taxi.pl/",
"status": 200
}
] |
| DOM structure hash | 2d1625595f0ee5fa7850e7472ac6ddc29050e439c463e65454030982d27dd24d |
| Document hash | 1c074e286ea6c0d78b18fe5ae31bad4363133562b73e6801722c5514c3a9ed8b |
| Domain risks | [
"Travel",
"Vehicles"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "jeziorak-taxi.pl",
"type": "A",
"value": "5.252.231.173"
}
] |
| Dnssec valid | false |
| Ip | 5.252.231.173 |
Osservato: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 44,
"malicious": 14,
"suspicious": 1,
"undetected": 33
} |
|---|---|
| Vendor labels | {
"VIPRE": "malware",
"G-Data": "phishing",
"Lionic": "malicious",
"Sophos": "phishing",
"CyRadar": "phishing",
"Fortinet": "malware",
"SOCRadar": "phishing",
"URLQuery": "suspicious",
"Seclookup": "malicious",
"Gridinsoft": "malicious",
"ADMINUSLabs": "malicious",
"BitDefender": "phishing",
"Chong Lua Dao": "malicious",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "malicious"
} |
| Reputation | 0 |
| Categories | {
"Sophos": "phishing and fraud",
"BitDefender": "blogs",
"alphaMountain.ai": "Phishing, Travel (alphaMountain.ai)",
"Forcepoint ThreatSeeker": "malicious web sites"
} |
| First seen | 2023-10-06T01:55:23Z |
| DNS records | [
{
"ttl": 3600,
"type": "SOA",
"rname": "hostmaster.jeziorak-taxi.pl",
"value": "dns1.thecamels.org"
},
{
"ttl": 3600,
"type": "NS",
"value": "dns2.thecamels.org"
},
{
"ttl": 3600,
"type": "TXT",
"value": "v=spf1 a mx ip4:5.252.231.173 ~all"
},
{
"ttl": 3600,
"type": "MX",
"value": "mail.jeziorak-taxi.pl",
"priority": 10
},
{
"ttl": 3600,
"type": "NS",
"value": "dns1.thecamels.org"
},
{
"ttl": 3600,
"type": "A",
"value": "5.252.231.173"
}
] |
| Dns at | 2026-10-17T23:36:28Z |
| Jarm | 27d27d27d00027d00042d42d0000005631adf8cfd24423913fd470a749070f |
| Certificate | {
"san": [
"*.jeziorak-taxi.pl",
"jeziorak-taxi.pl"
],
"issuer": "Let's Encrypt / YE2",
"serial": "657e156cd77560333b416a9312170f5e22b",
"sha256": "c31622d43621abe3ed54aee3e9abb46696510439634bd8ee33f2c2c90f543fec",
"subject": "*.jeziorak-taxi.pl",
"valid_to": "2026-11-23T05:24:54Z",
"valid_from": "2026-08-25T05:24:55Z"
} |
| Registration record | {
"dnssec": "Unsigned"
} |
| Registry data | {
"events": {
"expiration": "2027-03-20T15:12:27Z",
"last changed": "2026-03-09T11:14:03Z",
"registration": "2018-03-20T15:12:27Z",
"last update of RDAP database": "2026-10-17T23:36:14Z"
},
"registrar": "home.pl sp. z o.o."
} |
dns1.thecamels.orgdns2.thecamels.orgmail.jeziorak-taxi.plpriority 10Location describes the IP network.
c31622d43621abe3ed54aee3e9abb46696510439634bd8ee33f2c2c90f543fec*.jeziorak-taxi.pljeziorak-taxi.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.
autodiscover.jeziorak-taxi.plDomain recordcpanel.jeziorak-taxi.plDomain recordcpcalendars.jeziorak-taxi.plDomain recordcpcontacts.jeziorak-taxi.plDomain recordtest.jeziorak-taxi.plDomain recordwebdisk.jeziorak-taxi.plDomain recordwebmail.jeziorak-taxi.plDomain recordwww.jeziorak-taxi.plDomain recordwww.test.jeziorak-taxi.plDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of jeziorak-taxi.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.
Sconosciuto→live_content
content_served
Sconosciuto→live_content
content_served
Sconosciuto→live_content
content_served
Sconosciuto→live_content
content_served
Sconosciuto→live_content
content_served
Sconosciuto→live_content
content_served
Sconosciuto→live_content
content_served
Sconosciuto→live_content
content_served
Sconosciuto→live_content
content_served
Sconosciuto→live_content
content_served
Sconosciuto→live_content
content_served
Raggiungibile
No threat flag
View source34 community references
View source13/92 engine detections
View sourcePD-20261010-5D4FF3
jeziorak-taxi.pl
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
jeziorak-taxi.pl
PD-20261010-5D4FF3 Recipient: abuse@lh.pl Se hai inserito credenziali dell'account, informazioni personali o di pagamento oppure hai scaricato un file da questo dominio, agisci immediatamente. Di seguito sono riportate le risorse per aiutarti a segnalare l'incidente e proteggerti.
Seleziona il tuo Paese per ottenere contatti ufficiali del crimine informatico o creare una bozza di reclamo →.
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 ↗
jeziorak-taxi.pl)Anche se non conosci tutti i dettagli — sporgere comunque denuncia. Anche le informazioni parziali sono comunque utili alle indagini.
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
Analisi delle minacce utilizzando blocklist archiviate, WHOIS, DNS e prove di scansione pubblica
Scansiona oraSegnala i domini sospetti al nostro database delle minacce — proteggi la comunità
SegnalaSegnalazioni recenti di phishing e modifiche osservate della disponibilità
MonitoraControlla le minacce in tempo reale oppure contesta questa segnalazione se ritieni che si tratti di un falso positivo
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.