takelotzar.vip returned an HTTP status 200 on 2026-10-01, the most recent recorded response in this evidence set. The domain was first observed on 2026-09-23, and its registration date is 2026-01-11.
Recorded Evidence
An HTTP check on 2026-10-01 recorded status 200 for takelotzar.vip. VirusTotal recorded 16 detections across 91 scanners on 2026-09-25. OTX listed 4 pulses on 2026-09-25. The PhishDestroy internal listing records this domain, and the registrar is DNSPod, Inc. The first observation date is 2026-09-23.
Interpretation
The HTTP status, VirusTotal detections, OTX pulses and PhishDestroy listing each capture a different kind of source record, so they should be read separately rather than merged. The 2026-09-23 first observation and the 2026-10-01 HTTP check fall on different dates, which allows a reader to compare the recorded timeline without treating the gap as a change. The registration date of 2026-01-11 predates both observations and provides only a recorded starting point.
Recommended Actions
For takelotzar.vip, preserve the HTTP check record and the VirusTotal record as separate reference points for later comparison. Retain the OTX pulses and the PhishDestroy internal listing so each source can be reviewed on its own terms. Compare future HTTP checks against the recorded status, and compare future VirusTotal and OTX observations against their earlier values.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
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.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation활성 콘텐츠Ordinary HTTP content served90%2026-10-11 10:14:41 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:14:41 UTClast content: 2026-10-11 10:14:41 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 First positive detection Previous stored snapshot: 16 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
SafeToOpen
SOCRadar
URLQuery
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.
Threat First Observed2026-09-23 19:34:38 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 34.102.225.158.
위협 대응 Pipeline
발견
Analysis
Monitoring
9 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.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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.
(CN)
