The domain lumax.capital, associated with a critical threat score of 95/100, presents itself as a generic phishing operation and is currently down. It has been flagged as malicious by 18 out of 95 security vendors, including notable names such as ADMINUSLabs, Fortinet, and SOCRadar, and is listed on three public blocklists. Despite this, it is not flagged by Google Safe Browsing, indicating a potential gap in detection.
Registered with HOSTINGER operations, UAB, the domain was created and first seen on March 4, 2026. The hosting IP address is 147.93.42.229. The absence of a specific brand being impersonated suggests a broader scam approach rather than targeting a particular entity.
Given the critical threat level, block the domain at the perimeter and submit a report to the registrar's abuse desk for further investigation.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='lumax.capital', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("
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.
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:10:23 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-16 22:11:24 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-16 22:11:24 UTC → 2026-09-30 16:14:55 UTC · 2,538.06hmidpoint estimate ≈ 2026-08-08 19:13:09 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 Previous stored snapshot: 18 detections
ADMINUSLabs
Fortinet
SOCRadar
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.
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.
VirusTotal
18 detections recorded on VirusTotal — vendor total unavailable
2026年5月16日
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Technical Analysis Recorded
该报告包含存储的技术或取证分析结果。
2026年10月14日
Cloudflare Radar Scan
使用 Cloudflare 雷达扫描；网络分析完成。
2026年3月7日
Sent Report Recorded
Stored outgoing record associated with registrar HOSTINGER operations, UAB, 1 abuse contact
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.
