The domain onmicrosoft.live was recorded with an HTTP 200 response on 2026-10-03, indicating a successful connection at that time. The domain is also listed in the PhishDestroy internal catalogue, providing another distinct source observation.
Recorded Evidence
onmicrosoft.live was first observed on 2026-09-11. An HTTP check on 2026-10-03 recorded a status code of 200. The domain appears in the PhishDestroy internal listing as of the blocklist check on 2026-10-03. VirusTotal reported 6 detections out of 89 scanners on 2026-09-21. The registrar is Tucows Domains Inc., and the domain was registered on 2021-11-06.
Interpretation
The PhishDestroy internal listing and the VirusTotal detection record are separate observations, each reflecting different types of review on their respective dates. The HTTP 200 status code documents only the response received during its specific check and does not describe all possible content or uses of the domain. The first observation and registration dates provide context for when onmicrosoft.live entered public records, but do not indicate any specific activity.
Recommended Actions
Preserve the HTTP response, PhishDestroy internal listing, and VirusTotal detection records for onmicrosoft.live as separate sources for future reference. Compare each source's findings independently to monitor for any changes or new observations. Avoid submitting sensitive information to onmicrosoft.live until further review of these records is completed.
DOM Analysisanalyzed 2026年9月11日score 78/1001 brand signal
Submitted URLhttp://www.onmicrosoft.live/
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.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-11 10:37:45 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:37:45 UTClast content: 2026-10-11 10:37:45 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.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-09-11 05:39:52 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 216.40.34.41.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in ウェイバック・マシン — historical evidence archived
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
(CA)
