탐지를 보고하는 보안 엔진: 17. 극도의 주의를 기울이십시오 — 자격 증명이나 개인 정보를 입력하지 마십시오.
ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Elapsed since first report
1 month
Reports sent
1
Latest case ID
PD-20260907-9DCD2D
Current status
HTTP 200 at latest stored check
보고서 요약
jrtewnbh.com — 마지막으로 알려진 활성 (HTTP 200). 브랜드 사칭: Google; 사기 유형: Impersonation. 증거 요약: VirusTotal 17/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); URLQuery 4 alerts; Spamhaus DBL_PHISH; CF Radar malicious; PhishDestroy score 100/100. 등록기관: Dynadot.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
jrtewnbh.com returned HTTP status 200 on 2026-10-01, according to the recorded HTTP check. The domain was first observed on 2026-09-07, and its registration date is recorded as 2026-06-04 with Dynadot Inc as registrar.
Recorded Evidence
A VirusTotal check dated 2026-09-18 recorded 17 detections across 89 scanners. An OTX check dated 2026-09-11 recorded 4 pulses, and the domain appears in the PhishDestroy internal listing. The HTTP check on 2026-10-01 recorded status 200, and the IP address 34.8.229.132 was listed under Google Cloud in the US.
Interpretation
The VirusTotal and OTX observations come from different dates, so their counts reflect separate snapshots rather than one measurement. The PhishDestroy internal listing and the 2026-10-01 HTTP response were also recorded at different times, which limits direct comparison between them. These named sources describe recorded observations only, and their differing dates mean later checks could produce different results.
Recommended Actions
Anyone reviewing jrtewnbh.com should retain the dated records from VirusTotal, OTX, and PhishDestroy alongside the HTTP check, keeping each source's original timestamp intact. Subsequent observations of jrtewnbh.com should be compared against these baselines rather than treated as replacements. During any review, avoid submitting sensitive information to the domain until its current status has been verified through separate means.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation활성 콘텐츠Ordinary HTTP content served90%2026-10-12 10:27:42 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-12 10:27:42 UTClast content: 2026-10-12 10:27:42 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: 17 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
카스퍼스키
Lionic
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.
Threat First Observed2026-09-07 20:31:19 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 34.8.229.132.
위협 대응 Pipeline
발견
Analysis
Notifications
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.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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.
