Analysis as of July 24, 2026 indicates that the domain capitalprimeplc.com.standardfirm.online was registered on September 27, 2025 through HOSTINGER operations, UAB. The domain resolves to the IPv4 address 198.12.93.82, which belongs to AS36352 operated by HostPapa and is geolocated to the United States. Nameserver records point to ns1.megatronserver.com and ns2.megatronserver.com. No TLS certificate was observed, meaning the site was served over HTTP only.
The page title returned by the server is “capitalprimeplc”, providing no additional context about the malicious payload. Google Safe Browsing classifies the URL as a social‑engineering threat, and VirusTotal reports that three of ninety‑five scanned security vendors flagged the domain, indicating a low but non‑zero detection rate. The domain appears on a single external blocklist and has been actively blocked by the PhishDestroy sinkhole, confirming that at least one defensive network has taken mitigation steps. Gridinsoft assigned a trust score of 0 out of 100, reinforcing the perception of high risk.
The site is currently taken offline, which limits immediate exposure but does not guarantee that the infrastructure will not be re‑used. Uncertainty remains regarding the specific phishing kit, the exact content served, and whether additional infrastructure such as command‑and‑control servers is shared with other campaigns. Defenders should add the IP address 198.12.93.82 and the full domain name to inbound and outbound filtering rules, monitor for any resurgence of the domain or its aliases, and ensure that alerts from Safe Browsing, VirusTotal, or blocklist feeds are correlated with this indicator. Continuous observation of the registrar HOSTINGER operations, UAB for future registrations that mimic the same naming pattern is also advised.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='capitalprimeplc.com.standardfirm.online', port=80): Max retries exceeded with url: / (Caus
For the registrable domain standardfirm.online behind this subdomain, 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:09:07 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-17 22:20:02 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-17 22:20:02 UTC → 2026-09-30 16:14:55 UTC · 2,513.91hmidpoint estimate ≈ 2026-08-09 07:17:28 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.
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.
12 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.
(LT)
