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.
On 2026-10-01, dhl-tracking.com returned an HTTP status code 502, a server error recorded at that check. The domain was first observed on 2026-09-19, according to the recorded first-observation date.
Recorded Evidence
VirusTotal reported 20 detections across 89 scanners for dhl-tracking.com on 2026-09-20. OTX recorded four pulses on 2026-09-20. The PhishDestroy internal catalogue listed the domain, and the registration date was 2026-09-17 with registrar NICENIC INTERNATIONAL GROUP CO., LIMITED. The SSL certificate, issued by Let's Encrypt / YE1, was scanned on 2026-09-20.
Interpretation
The VirusTotal and OTX observations share the 2026-09-20 date, while the HTTP check and catalogue listing are dated 2026-10-01. Because these named sources were recorded on different dates, a reader can compare them only as separate snapshots rather than as one continuous record. The registration and first-observation dates fall earlier than the detection and HTTP checks, so the timeline spans several days of recorded observations.
Recommended Actions
Retain the existing records for dhl-tracking.com so later checks can be compared against the 2026-09-20 and 2026-10-01 observations. When reviewing dhl-tracking.com, avoid submitting sensitive information, and compare any new VirusTotal, OTX, or catalogue entries against the dates already recorded.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
마지막 은폐 스캔
스캐너 메모:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='dhl-tracking.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 비활성reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Active
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-11 02:43:25 UTC
RDAP registration활성NICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765RDAP HTTP 200source: Rdap Status CollectorclientDeleteProhibitedclientTransferProhibitedexpires 2027-09-17 20:00:56 UTCchecked 2026-09-20 04:31:38 UTC
Observed timelinelast reachable: 2026-09-20 02:34:06 UTClast content: 2026-09-20 02:34:06 UTCcurrent episode first observed: 2026-09-20 17:52:57 UTCobserved RIP window: 2026-09-20 02:34:06 UTC → 2026-09-20 17:52:57 UTC · 15.31hmidpoint estimate ≈ 2026-09-20 10:13:31 UTC · precision medium · basis bounded
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: 20 detections
Criminal IP
alphaMountain.ai
BitDefender
Certego
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
카스퍼스키
LevelBlue
Lionic
OpenPhish
Seclookup
SOCRadar
소포스
VIPRE
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.
Domain Status Transition2026-09-20 10:50:26 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-19 06:44:43 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 45.139.104.212.
위협 대응 Pipeline
발견
Analysis
Monitoring
12 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.
(RU)
PhishDestroy Investigation
