The domain nj.gov-lvi.cc was scanned by VirusTotal on 2026-09-24, where it received a documented number of detections from multiple security scanners. This domain was also included in the PhishDestroy internal listing, and its first observation was recorded on 2026-10-06.
Recorded Evidence
VirusTotal reported 15 detections out of 92 total scanners for nj.gov-lvi.cc on 2026-09-24. The domain was first observed on 2026-10-06. PhishDestroy internally listed the domain as of 2026-10-07.
Interpretation
The VirusTotal scan provides a record of how nj.gov-lvi.cc was evaluated by a range of security tools on a specific date. The PhishDestroy internal listing and the first observation date offer additional context for when the domain became notable to these monitoring services. These dated records document the domain's presence and assessment by multiple sources.
Recommended Actions
For further analysis or review of nj.gov-lvi.cc, retain the VirusTotal scan results and the PhishDestroy internal listing as primary evidence. Compare these records with the first observation date to track the domain's timeline in monitoring systems. Use these specific dated entries to inform any subsequent steps or reporting involving nj.gov-lvi.cc.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
마지막 은폐 스캔
스캐너 메모:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='nj.gov-lvi.cc', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-11 10:09:37 UTC
RDAP registration알 수 없음
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: 15 detections
ADMINUSLabs
ArcSight Threat Intelligence
BitDefender
Chong Lua Dao
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
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.
Threat First Observed2026-10-06 21:59:09 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 47.84.28.89.
위협 대응 Pipeline
발견
Analysis
Monitoring
7 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)
