跳转到安全报告
域安全和威胁情报
microsoftofficial.support favicon

microsoftofficial.support

“Microsoft Official Support - Help & Troubleshooting”

注册商
Name.com
Resolved IP
34.111.179.208
Registered
2025年11月22日
PhishDestroy assessment 关键
可用性 最后已知的活跃状态 最新存储的可达性观察 观察到 · HTTP probe
病毒检测总数:3/91 自动品牌标签:Microsoft
OTX: 23 refs 2025年12月17日
API
该域名已被标记为恶意域名
安全引擎报告检测:3。 请格外小心——不要输入凭据或个人信息。
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
报告概览

虚假技术支持: microsoftofficial.support — 最后已知的活跃状态 (HTTP 301). 证据摘要: VirusTotal 3/91 (alphaMountain.ai, Gridinsoft, LevelBlue); PhishDestroy score 81/100. 注册商…

为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。

Source evidenceVirusTotal 3 / 91 · OTX 23 references 5 sources

VirusTotal

3 / 91 engine detections

打开报告

Google Safe Browsing

No threat flag

打开报告

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

关键
VirusTotal
3 / 91
OTX
23 community refs
Page captures
2

PhishDestroy threat report

The domain microsoftofficial.support is a confirmed phishing site engaged in brand impersonation targeting Microsoft. It poses as 'Microsoft Official Support - Help & Troubleshooting' to deceive users into believing they are interacting with legitimate Microsoft technical support, a tactic classified as tech-support scam. No crypto drainer kit was detected. The domain is currently taken offline, but it previously operated as an elevated-risk threat.

Technical indicators confirm microsoftofficial.support as malicious. As of analysis, 2 of 95 VirusTotal security vendors flagged the domain, including Gridinsoft and SOCRadar. It appears on 1 security blocklist (PhishDestroy) but is not flagged by Google Safe Browsing. The domain was registered on November 22, 2025, through Name.com, Inc, and resolves to the IP address 34.111.179.208, hosted on Google Cloud (AS396982). The SSL certificate is issued by Let's Encrypt (E7), and the site used Google Cloud CDN with HTTP/3. Nameservers are ns1cny.name.com, ns2ckr.name.com, ns3jkl.name.com, and ns4hny.name.com. The observed HTTP status is 404.

Users who interacted with microsoftofficial.support should immediately change any passwords entered on the site, especially for Microsoft accounts, and enable two-factor authentication. Monitor accounts for unauthorized activity and report suspected fraud to Microsoft's official support channels. The domain can be reported to Google Safe Browsing, PhishTank, or the registrar Name.com for further action. If financial or personal data was shared, contact relevant institutions to secure accounts.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

已保存的截图 · 2 captures

Observed page title
Microsoft Official Support - Help & Troubleshooting
Automated brand references
Microsoft Office 365 Outlook Xbox
TLS 证书
颁发者 Let's Encrypt / E7

Domain details

域名
URLScan verdict 分析完成 score 0 report ↗
IP 信誉 abuse score 24/100 82 reports Fraud OrdersPhishingOpen ProxyEmail SpamPort ScanHackingSpoofingBad Web BotExploited HostWeb App Attack checked 2026年10月15日
OTX tags 2025-12activeall-domainsblocklistcontentcrypto域名drainerfraudlivemonthlyphishdestroyphishingscam
注册商 Name.com US(US)
滥用举报联系方式abuse@name.com
ICANN 注册管理机构ICANN Lookup (RDAP) →
注册信息创建 2025年11月22日 (332d) — Expires 2026年11月22日
HTTP 状态码301 Moved Permanently
技术详情Provenance & timestamps
首次发现2025年12月17日
DOM Analysisanalyzed 2026年10月20日score 81/1004 brand signals
Submitted URLhttp://microsoftofficial.support/
Favicon Hash
ICANN OVERSIGHT

认证和 RAA 背景

Registrar accreditation and DNS abuse obligations

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.

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.

Accountability draft 不会自动发送任何内容。

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
34.111.179.208
Network ASN
AS396982
Organization
Google LLC
Observed location
Kansas City, US
Server header
Google Frontend

域名服务器 4

  • ns1cny.name.com
  • ns2ckr.name.com
  • ns3jkl.name.com
  • ns4hny.name.com

Location describes the IP network.

TLS 证书

Issuer
Let's Encrypt / E7
Valid from
2025-12-16 19:53:40
Valid until
2026-03-16 19:53:39
Validity
Stored certificate expired
Collection time
2026-10-20 13:02:14 UTC
Collection source
PhishDestroy collector
Certificate fingerprinta4baa1a045906f7a93c22d1835b0245af708ea2d2a6d437cafe2380265aad886

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-19 22:17:47 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-19 22:17:47 UTC
RDAP registration 未知
Observed timeline last reachable: 2026-10-19 22:17:47 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.
技术 · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据,帮助保护他人

VirusTotal 分析

3 / 91 安全供应商标记了该域
View on VT
Last analyzed Previous stored snapshot: 3 detections
alphaMountain.ai
Gridinsoft
LevelBlue

存档证据

Wayback Machine Snapshot
历史快照可供证据审查
View Archive
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history20

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  2. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  3. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  4. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  5. Availability monitor · Recorded state

    未知→redirected

    http_redirect

Earlier observations 15
  1. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  2. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  3. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  4. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  5. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  6. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  7. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  8. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  9. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  10. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  11. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  12. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  13. Availability monitor · Recorded state

    不可用→可访问

  14. Availability monitor · Recorded state

    https://radar.cloudflare.com/scan/40cb15ea-9ee4-40f7-87a8-d05e0c718dbc

  15. Availability monitor · Recorded state

    可访问→不可用

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. AlienVault OTX

    23 community references

    View source
  3. VirusTotal

    3/91 engine detections

    View source
  4. URLScan

    Page captured

    View source
  5. Added to PhishDestroy

    microsoftofficial.support

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

microsoftofficial.support

证据与外部报告

深度分析
Help & reporting

您是否受到本网站的影响?

5 evidence signal groups linked 0 stored notification records 最后已知的活跃状态

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。

Official reporting routes

警惕“数据恢复”诈骗! 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。

97个国家目录

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.
  • 确切日期和时间 — 每笔交易的详情以及与诈骗者的首次接触
  • 屏幕截图 — 诈骗网站、聊天消息、电子邮件、钱包交易、社交媒体
  • 所有网址和域名 诈骗者使用的(包括 microsoftofficial.support)
  • 通信 — 诈骗者使用的电子邮件、短信、电话号码、用户名

即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。

我应该向哪里举报这起诈骗?

  • 联邦调查局(FBI)IC3 — 互联网犯罪投诉中心(美国联邦举报渠道)
  • 欧洲刑警组织 — 欧洲网络犯罪报告(欧盟)
  • 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
  • 利用人工智能实施的诈骗 — 深度伪造、自动化网络钓鱼以及人工智能生成的网站,使得欺诈行为更难被察觉

将来我该如何保护自己?

  • 将官方网站添加到书签 — 切勿点击来自电子邮件、私信或广告中的链接
  • 验证域名 — 查看 PhishDestroy 在进行互动之前,请检查HTTPS、拼写和域名注册时间。
  • “好得令人难以置信”=骗局 — 保证收益、名人代言、紧迫的截止日期

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

随时掌握最新信息,确保安全

请实时监控威胁,或者如果您认为这是误报,请对该条目提出异议

实时威胁动态 对该列表提出异议
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

嵌入此报告

在您的网站或博客上分享此威胁情报

embed.html
<iframe
  src="https://phishdestroy.io/zh/embed/domain/microsoftofficial.support"
  title="PhishDestroy threat report for microsoftofficial.support"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>