Analysis of ms-call.online indicates a high-risk phishing domain targeting users with fraudulent support-themed lures. The domain was registered on July 31, 2026, through NAMECHEAP INC, and currently resolves to IP address 192.64.119.195. Infrastructure review reveals nameservers dns1.registrar-servers.com and dns2.registrar-servers.com, a common configuration for domains registered via Namecheap. While no detections were recorded by the 95 security vendors that scanned the domain on VirusTotal, this absence does not confirm safety, as phishing sites often evade initial detection through rapid rotation or obfuscation.
The domain appears on three security blocklists, including PhishDestroy, MetaMask, and SEAL, which classify it as malicious. These listings provide concrete evidence of suspicious activity, though the specific phishing kit or targeted brand remains unconfirmed in available data. The domain name itself suggests an attempt to impersonate Microsoft support channels, a tactic frequently used to deceive users into disclosing credentials or installing malware. No SSL certificate details, HTTP response codes, or page content analysis are currently available, limiting further assessment of its operational status or technical sophistication.
Defenders should treat ms-call.online as an active threat. Network-level blocking is recommended based on its presence in multiple blocklists and its recent registration, which aligns with patterns observed in short-lived phishing campaigns. Organizations using Microsoft services should monitor for references to this domain in logs or user reports, as it may be leveraged in credential harvesting or tech-support scams. Given its high-risk classification and ongoing activity, continued vigilance and proactive mitigation are advised.
DOM Analysisanalyzed 2026年8月3日score 100/1001 brand signal
Submitted URLhttp://ms-call.online/
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.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-13 10:11:12 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-13 10:11:12 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.
Last analyzed First positive detection Previous stored snapshot: 10 detections
alphaMountain.ai
Bfore.Ai PreCrime
BitDefender
Chong Lua Dao
CRDF
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
カスペルスキー
Lionic
SOCRadar
ソフォス
VIPRE
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
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-08-03 12:37:51 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 192.64.119.195.
脅威対応 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.
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.
(US)
