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.
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-19 01:08:31 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.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
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("
fi-ca.digital
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
(US)
