VirusTotal
5 / 91 engine detections
レポートを開く“404 Not Found”
ブロックリスト掲載ドメイン: forteckio.online — 最後に確認されたアクティブな状態 (HTTP 301). 証拠の概要: VirusTotal 5/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
5 / 91 engine detections
レポートを開く4 community references
レポートを開くprovider verdict: clean
レポートを開く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
The domain forteckio.online was registered through Namecheap Inc on 16 July 2026 and is currently resolving to the address 172.67.164.49. The authoritative name servers listed are alberto.ns.cloudflare.com and hazel.ns.cloudflare.com, indicating that the domain is hosted behind Cloudflare's edge network. As of the report date (21 July 2026) the domain remains active and is listed on a single public blocklist, where it is identified by PhishDestroy as a malicious phishing entry. VirusTotal has processed the domain with scans from 95 security vendors; at the time of analysis none of the vendors reported a detection, but the absence of a detection does not constitute a safety assurance. The rapid creation-to‑deployment timeline—registration on 16 July and active status by 21 July—matches typical patterns observed in opportunistic phishing campaigns that exploit newly minted domains to evade historical reputation. The use of Cloudflare’s DNS services provides basic DDoS mitigation and obscures the true origin of the hosting infrastructure, complicating attribution efforts. No SSL certificate details, HTTP response codes, or page title information have been disclosed, leaving the content of the site unverified. Given the limited public intelligence, the primary confidence indicators are the registrar record, the IP address association with Cloudflare, and the inclusion on PhishDestroy’s blocklist. Defenders should add forteckio.online to internal URL filtering and sink‑hole rules, monitor DNS queries for the listed Cloudflare name servers, and treat any traffic to the domain as potentially malicious. Continuous re‑scanning with VirusTotal or comparable multi‑engine services is advised to capture any future detections. Analysts should also query threat‑intel feeds such as OTX and Google Safe Browsing for updates, and consider requesting passive DNS data to track any future IP changes that may signal infrastructure migration.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Edge-IP の評判はこのドメインに起因しません。
alberto.ns.cloudflare.comhazel.ns.cloudflare.comLocation describes the IP network.
a58ada259a0c565eb6a6b1061509dd029fdc9c31ab770aef8831ee037590e105Saved 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 forteckio.online · checked Jul 21, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
forteckio.online
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
到達可能→利用不可
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
利用不可→到達可能
到達可能→利用不可
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
4 community references
View source5/91 engine detections
View sourceNo threat flag
View sourceforteckio.online
View sourcePage captured
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
forteckio.online)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.