The domain fi-ca.digital was observed resolving to the IPv4 address 207.174.61.1, which belongs to the Amazon Web Services network (ASN16509) located in the United States. Registration records indicate the domain was created on 11 December 2025 through NameCheap, Inc., and the authoritative name servers are dns1.registrar-servers.com and dns2.registrar-servers.com. The site presented the page title “fi-ca.digital is a custom short domain” and did not serve an SSL/TLS certificate, indicating HTTP‑only delivery. Threat intelligence sources have flagged the domain: it appears on a single security blocklist, is listed in one AlienVault OTX pulse, and is actively blocked by the PhishDestroy service. Gridinsoft assigned a trust score of 0 out of 100, reinforcing the malicious assessment.
VirusTotal scanned the URL with 95 engines, of which five returned positive detections, further corroborating the phishing classification. The current operational status is offline, suggesting the hosting has been taken down or the site has been disabled. Analysis indicates that the infrastructure relies on a cloud provider (AWS) and a low‑cost registrar, a pattern commonly used to reduce attribution and increase turnover of malicious short‑link services. The lack of TLS, the generic page title, and the low trust score point to a purpose-built redirector rather than a legitimate service. No additional content has been captured, so the exact phishing payload, target brand, or credential‑stealing mechanism remains unknown.
Defenders should prioritize immediate blocking of the domain and its resolved IP address at network perimeters. Adding the domain to internal DNS blocklists and updating endpoint security signatures to reflect the five VirusTotal detections will reduce exposure. Continuous monitoring of the associated AWS CIDR ranges for new short‑link domains registered through NameCheap can help identify future replicas.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='fi-ca.digital', 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:09:37 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-05-18 00:12:20 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-18 00:12:20 UTC → 2026-09-30 16:14:55 UTC · 3,256.04hmidpoint estimate ≈ 2026-07-24 20:13:37 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.
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)
