VirusTotal
14 / 89 engine detections
レポートを開く“Login - Spotify”
Googleなりすまし: spotify.servernotification.events — 最後に確認されたアクティブな状態 (HTTP 302). 証拠の概要: VirusTotal 14/89 (BitDefender, Certego, Chong Lua Dao, CyRadar, ESET)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
14 / 89 engine detections
レポートを開く悪意あり
レポートを開くno community references
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain spotify.servernotification.events hosted a page titled "Login - Spotify" and is classified as an impersonation scam. The site was designed to mimic the Spotify login interface to deceive users into entering credentials. Although the page title references Spotify, the site impersonates the Google brand, indicating a targeted phishing attempt to harvest Google account credentials.
Technical analysis reveals the site was flagged by 20 of 95 VirusTotal vendors, with detections from ADMINUSLabs, BitDefender, Certego, Chong Lua Dao, and Cluster25. Google Safe Browsing flagged the site for social engineering. The domain was registered through NameCheap, Inc., hosted on IP address 3.174.46.79 (Germany) assigned to AS16509 Amazon.com, Inc., and used an Amazon RSA 2048 M02 SSL certificate. Nameservers were provided by Amazon Web Services.
The site is currently down/offline. GridinSoft trust rating is 0 out of 100, and the DOM risk score is 83, indicating a high-risk threat. Despite being offline, the domain remains a significant risk due to its association with credential theft and impersonation of trusted brands.
For the registrable domain servernotification.events behind this subdomain, 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.
ns-310.awsdns-38.comservernotification-events.mail.protection.outlook.compriority 0Location describes the IP network.
897eb86112360ee4445589437fd72b5f635fbcb414d0edab26a155544271df47account-management.net.auauk.co.nzauthorised-support.comcardpaysecurity.orgcargoforwarders.usdeaal.infodocument-share.servicesgoogle-notifications.orghzeak.inlang-en.uslifae.usliinkediin.comnochargemail.comobviouslyfakedomain.compasswordresets.onlinephishpond.comresetnoreply.comsecure-login.net.ausecurity-unauthorised-request.comsecurityresponse.orgservernotification.eventsserviceadministrator.networksupport-request.co.ukthefederalgovernment.orgtraulic.orgtrustedentity.comuserid-81d.wsuserid.teamvaevk.orgwebtoinvoice.comwinningfootytips.comzezol.mobiSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
redirect: raw=redirect_302; http=302; via=https_proxy; location=https://training.phriendlyphishing.com/landing_pages/simulated_phishing_page/story.html; server=CloudFront
spotify.servernotification.events
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
No threat flag
View source14/89 engine detections
View sourcePage captured
View sourcespotify.servernotification.events
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 ↗
spotify.servernotification.events)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.