microsoft365-verify[.]com
PhishDestroy first observed microsoft365-verify.com on Aug 19, 2026. The hostname explicitly references Microsoft and uses “verify,” a pattern consistent with a account-verification lure; stored content metadata identifies the same apparent target. Stored page analysis classifies the content as impersonation. Current evidence score: 86/100 (critical).
Positive findings are stored from 2 sources: VirusTotal and SEAL. VirusTotal recorded 1 detections among 91 engines: SOCRadar on Aug 20, 2026 at 05:57 UTC. SEAL listed the hostname in the separate external-blocklist snapshot on Aug 20, 2026 at 06:20 UTC. Non-positive and contextual checks: On Aug 20, 2026 at 05:58 UTC, AlienVault OTX listed 4 community pulse references (not vendor detections); Google Safe Browsing returned no flag. URLQuery recorded no positive detection; no observation timestamp was retained. URLScan completed without a malicious verdict (score 0) on Aug 20, 2026 at 05:08 UTC.
The collector marked the hostname reachable on Aug 19, 2026 at 23:20 UTC, but did not retain the HTTP response code. Registration records for the domain list Web Commerce Communications Limited dba WebNic.cc as the registrar and Aug 18, 2026 as the creation date. Registration preceded first observation by 1 day. At collection time, the hostname resolved to 103.163.138.39 on AS55688 (PT. Beon Intermedia). The recorded endpoint location is Prapen, ID. The stored server header is Apache. The evidence archive retains 2 visual captures from PhishDestroy and URLScan; no page title was retained, so the captures preserve the landing-page appearance. TLS metadata lists Let's Encrypt as the certificate issuer with validity through Oct 20, 2026; checked Aug 20, 2026 at 01:02 UTC.
The content indicators and 2 positive source findings support the current Microsoft-themed account-verification phishing classification.
Network Security Intelligence
Threat Response Pipeline
Public Blocklist Status
Stored Capture
Domain Intelligence
Technical detailsDNS, SSL SANs, timestamps
ICANN OVERSIGHT
Accreditation and RAA context
Accreditation and RAA context
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.
VirusTotal Analysis
Evidence & External Reports
PD-20260819-110E8C Recipient: abuse@byakta.com Were You Affected by This Site?
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive