VirusTotal
12 / 91 engine detections
レポートを開く“403 · Forbidden — SilkGuard”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@regtons.com.
The latest stored availability evidence still shows the domain reachable; 1 month 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.
フィッシング: fortmog.com — 未検証. 証拠の概要: VirusTotal 12/91 (alphaMountain.ai, BitDefender, Emsisoft, Forcepoint ThreatSeeker, Fortinet); Spamhaus DBL_SPAM…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
12 / 91 engine detections
レポートを開くDBL_SPAM
checked — no detections recorded
レポートを開く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
fortmog.com is an impersonation phishing site that poses as a legitimate service to win the trust of crypto users. PhishDestroy first flagged it on 2026-09-19, barely three weeks after the domain was registered. On 2026-10-19 the domain still responded, but the phishing content behind it was no longer active.
Impersonation pages copy the look, wording and login flow of a brand people already trust. The goal is to make a visitor sign in, confirm an account or enter a wallet recovery phrase on the fake page. Anything typed there goes straight to the operators, who can then take over the account or empty the wallet. The page title currently reads "403 · Forbidden — SilkGuard", which is an access-denied screen rather than a branded lure, while our classification remains impersonation phishing.
On 2026-09-30, 12 of 91 VirusTotal engines flagged the domain. That is a modest share, but the list includes established vendors such as Kaspersky, BitDefender, Fortinet, Forcepoint ThreatSeeker, G-Data, Emsisoft, Gridinsoft and alphaMountain.ai, so the verdict does not rest on a single scanner. Spamhaus lists the domain in its DBL under the spam category. Four AlienVault OTX threat pulses also reference it, which shows other researchers have tracked the same infrastructure. PhishDestroy lists it on its own blocklist.
The domain was registered on 2026-08-28 through Gransy, s.r.o. and was flagged 22 days later. That short gap between registration and active abuse is typical of throwaway phishing domains. It is hosted on the UFO TECHNOLOGIES LIMITED network in the United Kingdom. Its free Let's Encrypt certificate means the browser padlock only confirms an encrypted connection, not that the site is legitimate.
If you entered a password on fortmog.com, change it right away on the real service and on any other site where you reused it. Turn on app-based two-factor authentication and check your account for unfamiliar sessions or changed settings. If you typed a wallet recovery phrase, treat that wallet as compromised and move any remaining funds to a new wallet created with a fresh phrase. Defenders should block the domain and its hosting IP at DNS and proxy level and search their logs for earlier visits.
a.dnspod.comb.dnspod.comc.dnspod.comLocation describes the IP network.
fb8c9b19c2b1c180c4843e6a7d5cf5185e801c89265bdf8b0bc5cdc5748b6224Saved 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 fortmog.com · checked Sep 19, 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.
fortmog.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
live_content→dns_inactive
dns_nxdomain
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
4→5
3→4
0→3
No threat flag
View source12/91 engine detections
View source4 community references
View sourcePD-20260919-56B0E8
Page captured
View sourcefortmog.com
View sourcePD-20260919-56B0E8 Recipient: abuse@regtons.com アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
fortmog.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.