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.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-10 13:56:58 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-10 13:56:58 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.
Threat Response Pipeline
Discovery
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.
Threat Ingested
junpukai-google.com detected and queued for full analysis
The domain remains reachable or access-restricted; future checks may update this observation.
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.
6 evidence signal groups linked1 reports recordedLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · junpukai-google.com
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
