VirusTotal
17 / 92 engine detections
レポートを開く“ostrzeżenie - 4***l”
フィッシング: 4fpl.detaliczny.co — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 17/92 (alphaMountain.ai, BitDefender, CRDF, CyRadar, DNS8); Spamhaus DBL_PHISH; CF…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
17 / 92 engine detections
レポートを開く悪意あり
レポートを開くDBL_PHISH
Scan report
レポートを開くno community references
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy has listed 4fpl.detaliczny.co on its internal blocklist. The domain was first observed by PhishDestroy on 2026-10-19. No page title was recorded at the time of analysis.
The current evidence does not identify a specific malicious mechanism for this domain. In general, domains that trigger multiple security engine detections may be used for phishing, fraud, or malware distribution, but no concrete behavior has been observed here.
VirusTotal reported 17 detections from 92 scanning engines, with alerts from AlphaMountain.ai, BitDefender, CRDF, CyRadar, DNS8, ESET, Forcepoint ThreatSeeker and Fortinet; the data were retrieved on 2026-10-19 after analysis on 2026-10-18. Google Safe Browsing checked the domain on 2026-10-19 and did not flag it. External blocklist checks on the same date returned zero hits, and OTX listed zero pulses. PhishDestroy’s own internal list marked the domain as suspicious on 2026-10-19.
The recorded IP address for the domain is 104.18.13.234. No additional registration or hosting details are available, and the IP alone does not indicate operator identity or intent.
If you visited the site, verify that no credentials or personal data were entered and change any passwords that may have been used. Organizations should audit logs for connections to 104.18.13.234 and consider blocking the address if it is not required for legitimate business. Continue to monitor the domain for any changes in reputation from security vendors.
Edge-IP の評判はこのドメインに起因しません。
kolton.ns.cloudflare.comlaila.ns.cloudflare.comLocation describes the IP network.
1a74297e3e20df9d0a6d4ef64c0e8a7ebc0b0a346434b5ea5eea3c0c72ed7babSaved 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 4fpl.detaliczny.co · checked Oct 19, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://4fpl.detaliczny.co/https://4fpl.detaliczny.co/Content-Type: text/html; charset=utf-8Server: cloudflareContent-Encoding: gzipCF-Cache-Status: DYNAMICDYNAMICa4d262fede4cacbf-GRUkeep-alivegziptext/html; charset=utf-8Mon, 19 Oct 2026 20:03:32 GMT0.0329709053cloudflarechunkedAccept-EncodingValues retained by the collector; long values may be shortened during collection.
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.
不明→live_content
content_served
到達可能
No threat flag
View source17/92 engine detections
View sourcePD-20261019-2F275E
Page captured
View source4fpl.detaliczny.co
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
4fpl.detaliczny.co
PD-20261019-2F275E Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
4fpl.detaliczny.co)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.