Security engines reporting a detection: 13. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
The domain googlelogos.com was listed on the Phishunt blocklist as of 2026-10-06, providing a recent external observation of its status. Additionally, a PageSpeed assessment on the same date recorded a performance score of 56 for this domain.
Recorded Evidence
On 2026-10-06, googlelogos.com appeared on the Phishunt blocklist. VirusTotal checked the domain on 2026-10-02, reporting 13 detections out of 91 scanners. OTX referenced googlelogos.com in 3 pulses as of 2026-10-06. The registrar is GMO Internet Group, Inc. d/b/a Onamae.com, and the domain was registered on 2018-04-03.
Interpretation
The inclusion of googlelogos.com on the Phishunt blocklist and its multiple VirusTotal detections indicate that it has been recognized by several external security sources. OTX references further show that the domain has been noted in multiple security-related discussions. These observations are based on specific dates and do not provide information about the current content or activities associated with the domain.
Recommended Actions
For googlelogos.com, retain all records from Phishunt, VirusTotal, and OTX for ongoing reference. Compare these source records regularly to track any new or changed observations. Use the dated evidence to inform further review or monitoring of this domain.
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.
Stored cloaking flag
Not yet scanned
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
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: 13 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
Seclookup
Sophos
VIPRE
Webroot
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of googlelogos.com· checked Oct 6, 2026
56
Needs Work
Performance
FCP
7.67s
First Contentful Paint
LCP
13.07s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
134ms
Total Blocking Time
SI
7.81s
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-06 05:04:01 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 104.21.7.86.
Threat Response Pipeline
Discovery
Analysis
Monitoring
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
googlelogos.com detected and queued for full analysis
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.
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 · googlelogos.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.
