The owner of the website is using a service to hide their identity on WHOIS According to Tranco this site has a low rank The registrar has a high % of spammers and fraud sites This website is (very) young.
The SSL certificate is valid This website is safe according to DNSFilter
ネットワークセキュリティインテリジェンス Registrar context
Registrar contextNiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
The domain app-backpack.exchange, associated with a critical threat score of 95/100, presents itself as a generic phishing operation and is currently down. Fourteen out of 95 security vendors have flagged this domain as malicious, including notable names like Kaspersky and BitDefender. It is listed on three public blocklists, though Google Safe Browsing has not flagged it.
Registered with NiceNIC International Group Co., Limited in Hong Kong, the domain was created on February 16, 2026, and first detected on February 19, 2026. The hosting IP is 188.114.97.3. Given the critical threat level, block the domain at the perimeter and report it to the registrar abuse desk.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='app-backpack.exchange', port=80): Max retries exceeded with url: / (Caused by NewConnectio
DOM Analysisanalyzed 2026年7月29日score 98/1001 brand signal
Submitted URLhttp://app-backpack.exchange/
ICANN OVERSIGHT
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
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 outcomeRegistration hold observedreason: Registrar clientHold95% confidence
AttributionNICENIC INTERNATIONAL GROUP CO., LIMITEDmechanism: Registrar clientHoldsource: Rdap Status Collector
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Registrar clientHold
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 10:49:44 UTC
RDAP registrationRegistrar clientHoldNICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765RDAP HTTP 200source: Rdap Status CollectorclientDeleteProhibitedclientHoldclientTransferProhibitedexpires 2027-02-17 11:31:37 UTCchecked 2026-10-11 03:45:55 UTC
Registrar action markerverified clientHold markerNICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765causal link to our report not established
Observed timelinecurrent episode first observed: 2026-08-05 01:45:38 UTCfirst terminal observation: 2026-08-05 01:45:38 UTC
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.
13 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.
Web Archive
Preserved in ウェイバック・マシン — historical evidence archived
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.
(RU)
PhishDestroy Investigation
