injective-app.xyz was observed in security records with a VirusTotal scan on 2026-10-13, providing a technical detection snapshot for the domain. The domain is also referenced in multiple blocklist entries, offering additional context for its recorded status.
Recorded Evidence
VirusTotal documented 5 detections out of 92 total scanners for injective-app.xyz on 2026-10-13. On the same date, MetaMask and SEAL external blocklists listed the domain. OTX recorded two pulses for injective-app.xyz, and PhishDestroy included an internal listing. The domain was registered with Global Domain Group LLC on 2026-08-04.
Interpretation
VirusTotal provides a quantitative measurement of detections from a broad set of scanners, capturing technical evidence for injective-app.xyz. PhishDestroy records the domain in its internal listing, documenting its presence in their intelligence database. External blocklists such as MetaMask and SEAL offer additional references for the domain’s status in security monitoring.
Recommended Actions
For injective-app.xyz, retain the VirusTotal and OTX records for ongoing comparison with future scans. Preserve MetaMask and SEAL blocklist entries to monitor changes in external blocklist references. Maintain the PhishDestroy internal listing for historical analysis and context.
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.
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.
Values retained by the collector; long values may be shortened during collection.
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
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.
Threat First Observed2026-10-13 12:59:57 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 188.114.97.1.
威胁响应 Pipeline
发现
Analysis
Monitoring
8 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)
