VirusTotal
8 / 91 engine detections
レポートを開く“(1) Notification”
フィッシング: flyblog.online — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 8/91 (alphaMountain.ai, CRDF, ESET, Forcepoint ThreatSeeker, Lionic); PhishDestroy…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
8 / 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
flyblog.online is an impersonation phishing page. It presents itself under the title "(1) Notification", a format built to look like an unread alert from a familiar service. PhishDestroy first flagged it on 2026-09-16. As of 2026-10-19 the site was still online and serving its content.
The "(1)" in the title copies the unread-count style that social networks and account dashboards show in browser tabs. It creates the sense that something is waiting for you. Impersonation pages use that urgency to get visitors to "verify" an account, sign in to view the message, or confirm details on a page that looks legitimate. Anything typed there goes to the operators, including passwords, one-time codes, personal information and sometimes crypto recovery phrases. Stolen access is then used to take over accounts or to reach the funds behind them.
On 2026-09-29, 8 of 91 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, ESET, Forcepoint ThreatSeeker, Lionic, SOCRadar, Webroot and Yandex Safebrowsing. That count is modest, but these are unrelated vendors reaching the same verdict. The domain is also referenced in 4 AlienVault OTX threat pulses, so other researchers have tracked it as well. It appears on the PhishDestroy blocklist.
The domain was registered on 2025-11-20 through HOSTINGER operations, UAB, about ten months before PhishDestroy detected it. That gap suggests an aged domain kept in reserve or quietly reused, not one spun up the day of a campaign. Traffic is fronted by Cloudflare, Inc., with the address geolocated to Canada, which hides the actual origin server. The Google Trust Services certificate gives the page a padlock, which proves only an encrypted connection, not a trustworthy site.
If you signed in or entered any details on this page, change that password right away and change it anywhere else you reused it. Turn on or reset two-factor authentication and sign out of all active sessions on the affected account. If you typed a wallet recovery phrase, treat that wallet as compromised and move its funds to a new wallet created from a fresh phrase. Defenders should block flyblog.online at DNS, proxy and email gateways, and search logs for users who reached it after 2026-09-16 so they can force credential resets.
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 の評判はこのドメインに起因しません。
alfred.ns.cloudflare.comjoan.ns.cloudflare.comLocation describes the IP network.
0919fdb6d816cd1f9620845ada29564ff76786799cfc78d773a296554fb56de1Saved 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 flyblog.online · checked Sep 16, 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.
flyblog.online
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
不明→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
不明→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
不明→live_content
content_served
不明→live_content
content_served
6→7
5→6
4→5
到達可能
4 community references
View sourceNo threat flag
View source8/91 engine detections
View sourceflyblog.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 ↗
flyblog.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.