Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
网络安全情报 Registrar context
Registrar contextNameSilo
Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
click5.microsoftsupportcenter.digital is an impersonation phishing page that trades on the Microsoft name, wrapping it in a fake "support center" domain to look like an official help channel. It targets Microsoft users who believe they are dealing with genuine support. PhishDestroy first flagged it on 2026-10-11, and it was still online with live content on 2026-10-19.
How the scam works
Sites built on a "Microsoft support" name usually reach victims through links in emails, ads or pop-up warnings that claim an account or device problem. The visitor is then pushed toward a page that asks for Microsoft account credentials or a call to a fake support line. Either path can end with stolen logins, remote-access tools on the computer, or payment for useless "fixes". The page itself carries only the title "Redirecting...", which suggests a hand-off point that forwards visitors elsewhere, while our classification is Microsoft impersonation phishing.
Evidence
Sixteen of 92 VirusTotal engines flagged the domain as of 2026-10-12. The flagging vendors include BitDefender, CRDF, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Google Safe Browsing and Gridinsoft. Google Safe Browsing lists it under SOCIAL_ENGINEERING, so Chrome, Firefox and Safari users should see a warning before the page loads. The domain is also on the PhishDestroy blocklist.
Infrastructure
The parent domain was registered through NameSilo, LLC on 2025-10-06, about a year before PhishDestroy detected this subdomain. That gap points to an operator who registered the name ahead of time rather than running a throwaway site. The host sits on Akamai Connected Cloud in the US. It uses a free Let's Encrypt certificate, so the padlock in the browser says nothing about whether Microsoft is behind it.
What to do
If you typed a Microsoft password on a page reached through this domain, change it right away from the real Microsoft account site and review recent sign-in activity. Turn on two-factor authentication and change the same password anywhere else you reused it. If you called a number or let someone connect to your computer, uninstall any remote-access tool they had you install and run a full security scan. If you paid them, contact your bank or card issuer to dispute the charge. Defenders should block the full microsoftsupportcenter.digital domain, not just this one subdomain, and search mail and proxy logs for users who clicked through.
For the registrable domain microsoftsupportcenter.digital 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.
Accreditation is a contract, not a safety certification.
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.
Certificate fingerprint96c77180a7861fb4630f45bc7fc0cbdbe3fc818b200526d4c5d278b5c2c631a1Certificate names · 1 SANs
microsoftsupportcenter.digital
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-19 22:27:42 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-19 22:35:30 UTClast content: 2026-10-19 22:27:42 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
(US)
PhishDestroy Investigation
