VirusTotal
14 / 89 engine detections
レポートを開くフィッシング: facebooknotify-noreply.com — コンテンツが利用できません. 証拠の概要: VirusTotal 14/89 (alphaMountain.ai, CRDF, ESET, Emsisoft, Forcepoint ThreatSeeker); Google Safe…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
14 / 89 engine detections
レポートを開くThreat flag recorded
レポートを開く3 community references
レポートを開くprovider verdict: clean
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
facebooknotify-noreply.com is an impersonation phishing domain dressed up as Facebook's automated notification system. The "notify" and "noreply" wording copies the sender style of genuine platform alerts, which targets Facebook users and the people who manage business pages and ad accounts. PhishDestroy first flagged it on 2026-09-18. The site has been offline since 2026-09-22, and DNS for the domain was still inactive at the last check on 2026-10-19.
Schemes like this usually start with a message that looks like a routine Facebook alert, such as a policy violation, a security warning or a page-restriction notice, and push the recipient to act quickly. The link leads to a page styled after Facebook that asks for an email or phone number, the password and often a two-factor code. Anyone who completes the form gives the operators enough to take over the account. A hijacked account can then be used to message contacts, run fraudulent ads or spread the same lure further.
On 2026-09-21, VirusTotal showed 14 of 89 engines flagging the domain. They included alphaMountain.ai, CRDF, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data and Google Safe Browsing. Google Safe Browsing specifically lists it under SOCIAL_ENGINEERING, its category for deceptive pages that impersonate trusted services. The domain appears in three AlienVault OTX threat pulses, which means other researchers have tracked it independently, and it is on the PhishDestroy blocklist.
The domain was registered through Cloudflare, Inc. on 2026-06-19, about three months before PhishDestroy detected it. That kind of gap is typical of domains registered early and held until a campaign is ready. It resolved to 216.198.79.65, an address in the United States. The site used a free Let's Encrypt certificate, so the padlock in the browser only meant the connection was encrypted and said nothing about whether Facebook was behind it.
If you entered your Facebook password on this site, change it right away. Change it anywhere else you reused it too. Then review active sessions in Facebook's security settings and log out any device you don't recognize. Turn on two-factor authentication with an authenticator app, and check whether your recovery email, phone number and page or ad-account admins have been changed. Defenders should block the domain and IP at mail and web gateways and search mail logs for messages that link to it. Users should also be reminded that real Facebook alerts can be checked inside the app or the official site instead of through emailed links.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
d5ed14243f1fe3655cedeb99bf5f8cfc65f6887a64ed480350ebca6180738332Saved 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 facebooknotify-noreply.com · checked Sep 18, 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.
facebooknotify-noreply.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
到達可能→利用不可
4→5
No flag recorded→Flag recorded
Threat flag recorded
View source14/89 engine detections
View source3 community references
View sourcefacebooknotify-noreply.com
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 ↗
facebooknotify-noreply.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.