Mesin keamanan melaporkan deteksi: 17. Berhati-hatilah — jangan memasukkan kredensial atau informasi pribadi.
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
Ringkasan laporan
jrtewnbh.com — Terakhir diketahui aktif (HTTP 200). Peniruan identitas merek: Google; Jenis penipuan: Impersonation. Ringkasan bukti: VirusTotal 17/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); URLQuery 4 alerts; Spamhaus DBL_PHISH; CF Radar malicious; PhishDestroy score 100/100. Registrar: Dynadot.
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
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.
Analisis deteksi dan penghindaran
Pemeriksaan penyamaran dan distribusi lalu lintas
Belum dipindaiBelum ada perbedaan yang tercatat antara crawler dan browser
Data pengamatan perbandingan crawler versus browser yang telah disimpan untuk host ini, ditambah pemeriksaan sidik jari secara real-time untuk sistem distribusi lalu lintas bergaya Keitaro.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationKonten aktifOrdinary HTTP content served90%2026-10-13 10:27:43 UTC
RDAP registrationTidak diketahui
Observed timelinelast reachable: 2026-10-13 10:27:43 UTClast content: 2026-10-13 10:27:43 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
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
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.
Alur Tanggapan Ancaman Pipeline
Penemuan
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.
Ancaman Telah Diterima
jrtewnbh.com telah terdeteksi dan dimasukkan ke dalam antrian untuk analisis menyeluruh
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.
Domain tetap dapat dijangkau atau aksesnya dibatasi; pemeriksaan di masa depan dapat memperbarui pengamatan ini.
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.
6 evidence signal groups linked1 reports recordedTerakhir diketahui aktif
If credentials were compromised, report immediately. Do not engage with recovery scammers.
Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.
Waspadalah terhadap penipu yang mengatasnamakan pemulihan! Penjahat dapat menghubungi korban lagi sambil berpura-pura menjadi penyelidik, pengacara, atau agen pemulihan. Jangan membayar biaya di muka atau membagikan kredensial.Pelajari lebih lanjut tentang penipuan dalam proses pemulihan →
Laporkan kepada Pihak Berwenang di Daerah Anda
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
Direktori 97 negara
Template-based draft · optional AI wording assistance requires separate consent
Draf yang dibantu AI — detail insiden diproses oleh penyedia AI · Tinjau dan kirimkan sendiri
Infrastruktur dan Laporan Terkait
Hubungan yang disimpan dikelompokkan berdasarkan atribut pencocokan tepat. Penyedia atau registrar bersama saja tidak membuktikan kepemilikan bersama.
Tautan langsung Menggunakan pendaftaran yang sama atau perangkat phishing yang identik.
Sinyal pendukung Berbagi infrastruktur atau merek sasaran; bukan bukti adanya satu operator.
Hanya untuk penemuan Terdaftar untuk navigasi; tidak ada atribut yang sama dengan host ini.
Peta infrastruktur · jrtewnbh.com
Setiap jalur merupakan salah satu alasan mengapa sebuah domain terhubung ke host ini. Ukuran node menandai deteksi VirusTotal, sedangkan node bergaris putus-putus menunjukkan bahwa node tersebut sudah offline. Daftar lengkapnya tercantum di bawah ini.
Konten cocok4
Hash favicon yang sama atau judul halaman yang sama dengan host ini.
Didaftarkan melalui penyedia layanan pendaftaran yang sama. Sebuah penyedia layanan pendaftaran melayani jutaan pelanggan yang tidak saling terkait, sehingga hal ini sekadar mengelompokkan laporan-laporan tersebut, bukan membuktikan adanya hubungan.
