Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
PhishDestroy first observed googalagoogala.cfd on Oct 12, 2026. Current evidence score: 66/100 (high).
Positive findings are stored from 3 sources: VirusTotal, MetaMask, and SEAL. VirusTotal recorded 2 detections among 92 engines: alphaMountain.ai, Fortinet on Oct 12, 2026 at 23:53 UTC. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Oct 12, 2026 at 22:20 UTC. Additional recorded evidence: AlienVault OTX listed 2 community pulse references (not vendor detections) on Oct 12, 2026 at 23:07 UTC.
Latest classified outcome: unknown; cause stale current evidence on Oct 12, 2026 at 20:42 UTC. Registration records for the domain list NICENIC INTERNATIONAL GROUP CO., LIMITED as the registrar and Sep 21, 2026 as the creation date. Registration preceded first observation by 21 days. At collection time, the hostname resolved to 172.67.198.220. The IP and ASN identify shared Cloudflare edge infrastructure; the origin server is not established by this address. The evidence archive retains 1 visual capture from PhishDestroy; the captures preserve the landing-page appearance.
The record contains 3 positive source findings supporting the current phishing classification.
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
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: 2 detections
alphaMountain.ai
Fortinet
网站性能分析
Google PageSpeed Insights — mobile performance audit of googalagoogala.cfd· checked Oct 13, 2026
94
Good
Performance
FCP
2.45s
First Contentful Paint
LCP
2.45s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.45s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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-12 22:37:22 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 172.67.198.220.
威胁响应 Pipeline
发现
Analysis
Monitoring
9 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.
(RU)
PhishDestroy Investigation
