On 2026-10-07, the domain waren-umschlagzentrum7s.ink returned an HTTP 404 response, indicating that the requested page was not found on the server at that time. This domain was also referenced in the PhishDestroy internal listing on the same date.
Recorded Evidence
waren-umschlagzentrum7s.ink was first observed on 2026-10-07 and registered on 2026-10-01 with Dominet (HK) Limited. On 2026-10-07, VirusTotal reported 1 detection out of 92 scanners for this domain. OTX recorded 3 pulses associated with the domain on 2026-10-07. The PhishDestroy internal listing also included this domain on 2026-10-07.
Interpretation
The records from OTX, VirusTotal, and PhishDestroy each provide a dated reference to waren-umschlagzentrum7s.ink, allowing for cross-comparison of observations from different sources. The HTTP 404 response only describes the result of a specific web request and does not provide information about other possible services or content on the domain. The presence of entries in OTX and VirusTotal indicates that the domain was reviewed by both community and automated security sources.
Recommended Actions
For future assessments of waren-umschlagzentrum7s.ink, compare new HTTP responses to the recorded 404 result. Retain the VirusTotal and OTX source records for reference in subsequent reviews. Keep the PhishDestroy internal listing as a baseline for tracking changes over time.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcome非活动reason: Http No Content70% confidence
Attributionsource: Current Http Probe
Evidence layersAvailability: Root path has no contentContent: Absent At RootDNS: ResolvedRegistration: Unknown
Latest HTTP observation非活动Http No Content70%2026-10-13 01:34:16 UTC
RDAP registration未知
Observed timelinecurrent episode first observed: 2026-10-07 10:00:24 UTCfirst terminal observation: 2026-10-07 10:00:24 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.
技术 · 2 identified
Cloudflare
CDN
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Last analyzed Previous stored snapshot: 1 detection
alphaMountain.ai
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.
Domain Status Transition2026-10-07 10:00:24 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-10-07 07:54:38 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 188.114.96.1.
威胁响应 Pipeline
发现
Analysis
Monitoring
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.
(HK)
