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.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
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: StaleRegistration: Unknown
Latest HTTP observation비활성Http No Content70%2026-10-13 01:00:12 UTC
RDAP registration알 수 없음
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.
기술 · 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: 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.
위협 대응 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.
위협 탐지됨
hjemmeleveringstjenesteus.ink 탐지되어 전체 분석을 위해 대기열에 추가됨
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.
최근에 저장된 확인 결과에 따르면 보고된 콘텐츠를 사용할 수 없습니다. 이는 변경의 원인이 누구인지, 원인이 무엇인지 확인하지 않습니다.
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.
(HK)
