일치를 보고하는 공개 차단 목록: 2. 극도의 주의를 기울이십시오 — 자격 증명이나 개인 정보를 입력하지 마십시오.
ABUSE NOTICE · 24H+ 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@internet.gmo.
The latest stored availability evidence still shows the domain reachable; 27 hours 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
27 hours
Reports sent
1
Latest case ID
PD-20261010-5F6B1F
Current status
HTTP 200 at latest stored check
보고서 요약
junpukai-google.com — 마지막으로 알려진 활성 (HTTP 200). 브랜드 사칭: Google; 사기 유형: Impersonation. 증거 요약: URLQuery 2 det.; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 90/100. 등록기관: GMO Internet Group.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
junpukai-google.com was recorded on 2026-10-10 with a MetaMask external blocklist observation, documenting a security-related entry on that date. The domain was also present in the SEAL blocklist, adding another reference point for its status.
Recorded Evidence
MetaMask listed junpukai-google.com on its external blocklist as of 2026-10-10. SEAL also included the domain in its external blocklist on the same date. PhishDestroy recorded an internal listing for junpukai-google.com on 2026-10-10. The domain was registered through GMO Internet Group, Inc. d/b/a Onamae.com on 2026-10-07.
Interpretation
The PhishDestroy record contains an internal listing, which measures the domain's inclusion in a security monitoring system. MetaMask and SEAL each provide external blocklist entries, documenting how junpukai-google.com was referenced in their respective databases. These dated records offer a snapshot of the domain's presence in multiple security sources at a specific point in time.
Recommended Actions
Retain the MetaMask and SEAL blocklist entries for junpukai-google.com to support future comparisons and reviews. Preserve the PhishDestroy internal listing as an additional reference. Use these records to inform ongoing monitoring and analysis of the domain's security status.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation활성 콘텐츠Ordinary HTTP content served90%2026-10-11 10:00:44 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:00:44 UTClast content: 2026-10-11 10:00:44 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.
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-10 13:56:58 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 150.95.255.38.
위협 대응 Pipeline
발견
Analysis
Notifications
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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.
PDF notice generated Notice text archived (856 chars)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
