The domain hjemmeleveringstjenesteus.ink returned an HTTP status 404 on 2026-10-13, documenting a lack of accessible content at that time. The domain was first observed on 2026-10-13, establishing the initial date of recorded evidence.
Recorded Evidence
VirusTotal checked hjemmeleveringstjenesteus.ink on 2026-10-12, recording 6 detections out of 92 total scanners. OTX referenced the domain with 2 pulses as of 2026-10-13. The domain was internally listed by PhishDestroy on 2026-10-13. Registration with Dominet (HK) Limited was recorded on 2026-10-11.
Interpretation
The VirusTotal record contains a technical measurement of scanner detections and total checks, providing insight into the domain's recognition by external security tools. OTX documents the domain's inclusion in two intelligence pulses, reflecting its presence in external security monitoring. The HTTP status record captures a dated response code, while the PhishDestroy entry serves as a publisher-owned catalogue reference.
Recommended Actions
For hjemmeleveringstjenesteus.ink, preserve the VirusTotal detection record and OTX pulse references for future comparison. Retain the HTTP status 404 observation as a technical reference for subsequent checks. Archive the PhishDestroy internal listing for ongoing review of domain-related evidence.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
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 outcomeInactivereason: Http No Content70% confidence
Attributionsource: Current Http Probe
Evidence layersAvailability: Root path has no contentContent: Absent At RootDNS: StaleRegistration: Unknown
Latest HTTP observationInactiveHttp No Content70%2026-10-13 01:00:12 UTC
RDAP registrationUnknown
Observed timelinecurrent episode first observed: 2026-10-13 01:00:12 UTCfirst terminal observation: 2026-10-13 01:00:12 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.
Last analyzed Previous stored snapshot: 7 detections
alphaMountain.ai
CRDF
Fortinet
Gridinsoft
SOCRadar
Webroot
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.
VirusTotal Detections Update2026-10-13 00:58:47 UTC
VirusTotal scanner detections updated from 7 to 6. Resolved alerts: DNS8.
Threat First Observed2026-10-12 23:52:47 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 188.114.96.1.
Threat Response Pipeline
Discovery
Analysis
Monitoring
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
hjemmeleveringstjenesteus.ink detected and queued for full analysis
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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
How we investigate & report
Public scans, evidence and abuse channels
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.
4 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(HK)
