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.
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.
詐欺による金銭の返還を装った詐欺 — 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
