Security engines reporting a detection: 15. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
PhishDestroy first observed www-app-google.com on Oct 6, 2026. Current evidence score: 95/100 (critical).
Positive findings are stored from 2 sources: VirusTotal and Phishunt. VirusTotal recorded 15 detections among 91 engines: Criminal IP, alphaMountain.ai, BitDefender, Chong Lua Dao, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, LevelBlue, Lionic, Seclookup, Sophos, VIPRE, Webroot on Oct 6, 2026 at 06:41 UTC. Phishunt listed the hostname in the separate external-blocklist snapshot on Oct 6, 2026 at 02:20 UTC. Additional recorded evidence: AlienVault OTX listed 1 community pulse reference (not vendor detections) on Oct 6, 2026 at 05:41 UTC.
Latest classified outcome: unknown; cause stale current evidence on Oct 6, 2026 at 03:44 UTC. Registration records for the domain list Gname.com Pte. Ltd. as the registrar and Jan 11, 2026 as the creation date. At collection time, the hostname resolved to 172.67.202.185 on AS13335 (Cloudflare, Inc.). 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 2 positive source findings supporting the current phishing classification.
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: 15 detections
Criminal IP
alphaMountain.ai
BitDefender
Chong Lua Dao
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
LevelBlue
Lionic
Seclookup
Sophos
VIPRE
Webroot
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of www-app-google.com· checked Oct 6, 2026
100
Good
Performance
FCP
0.82s
First Contentful Paint
LCP
0.82s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
1ms
Total Blocking Time
SI
1.23s
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:40:35 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 172.67.202.185.
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
www-app-google.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 · www-app-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.
(SG)
