This domain is flagged as a credential harvesting phishing site targeting users through fraudulent login portals. Analysis indicates the infrastructure was designed to mimic legitimate authentication pages, likely to capture sensitive account credentials for malicious purposes. The risk level remains under investigation due to limited detection but confirmed phishing indicators. Infrastructure analysis reveals zooms.solutions was registered on June 24, 2026, through HOSTINGER operations, UAB. The domain resolved to IP address 104.21.72.123 and was subsequently taken offline. At the time of assessment, the domain appeared on one security blocklist, while VirusTotal reported 0 detections out of 95 engines. No SSL certificate was present, increasing the likelihood of interception or tampering during transmission. The absence of prior detections suggests either a newly deployed campaign or evasion techniques to avoid automated detection systems. Mitigation steps for this threat type include immediate blocking of the domain and associated IP address (104.21.72.123) at the network perimeter. Organizations should monitor for credential reuse attempts from affected users and enforce multi-factor authentication (MFA) to mitigate account compromise risks. Security teams are advised to review logs for connections to the domain or IP, particularly from endpoints that may have interacted with the phishing page. User awareness training should emphasize identifying fraudulent login portals, especially those impersonating collaboration or productivity platforms.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='zooms.solutions', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
DOM Analysisanalyzed 2026年6月25日score 76/1001 brand signal
Submitted URLhttps://zooms.solutions/
案件 ID
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:12:24 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-07-08 16:18:09 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-08 16:18:09 UTC → 2026-09-30 16:14:55 UTC · 2,015.95hmidpoint estimate ≈ 2026-08-19 16:16:32 UTC · precision very low · basis bounded
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: 0 detections
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
