app[.]ligter[.]network
“Un instant…”
Analysis of app.ligter.network shows it was registered on 27 February 2026 through PDR Ltd. d/b/a PublicDomainRegistry.com and is served from Cloudflare’s network (ASN 13335) with the IP address 104.21.93.60 located in the United States. The domain resolves to Cloudflare nameservers leo.ns.cloudflare.com and phoenix.ns.cloudflare.com, indicating use of a CDN for rapid content delivery and possible obfuscation of origin infrastructure. The site presented a page title “Un instant…”, which is the only content observed before the service was taken offline.
No TLS certificate was presented, meaning the site operated over plain HTTP, a common characteristic of low‑cost phishing deployments. Threat intelligence sources have recorded a single detection: one of ninety‑three VirusTotal scanners flagged the domain, and it appears on a single public blocklist, where it is actively blocked by PhishDestroy. Gridinsoft assigned a trust score of 0 out of 100, reinforcing the malicious assessment.
The current offline status suggests the operator may be rotating domains, but the underlying infrastructure – Cloudflare front‑end and the same registrar pattern – remains reusable for future campaigns. Defenders should add the domain to outbound and inbound filtering rules, monitor DNS queries for the IP 104.21.93.60 and associated Cloudflare nameservers, and consider extending blocklist coverage to similar registration fingerprints. Continuous re‑scanning of the domain, especially if it reappears, is recommended to capture any changes in payload or TLS usage.
Threat Response Pipeline
Public Blocklist Status
Stored Capture
Domain Intelligence
Technical detailsDNS, SSL SANs, timestamps
ICANN OVERSIGHT
Registration: ligter.network
Accreditation and RAA context
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For the registrable domain ligter.network 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.
Forensic Intelligence
VirusTotal Analysis
Evidence & External Reports
PD-20260227-A86F3A Recipient: abuse@publicdomainregistry.com Were You Affected by This Site?
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive