PhishDestroy first recorded app.googleoa.com on 2026-10-06. Stored VirusTotal result: 16/92 engines flagged. Malicious: 15. Suspicious: 1. Analysis time (as stored): 2026-10-02 16:26 UTC. Retrieved (as stored): 2026-10-21 13:16 UTC. Google Safe Browsing flags it.
More about the sources
Recorded security signals
Stored VirusTotal result: 16/92 engines flagged. Malicious: 15. Suspicious: 1. Analysis time (as stored): 2026-10-02 16:26 UTC. Retrieved (as stored): 2026-10-21 13:16 UTC. Listed by external blocklists: Phishunt. Use caution — do not enter credentials or personal information.
Risk signals
VirusTotal detections: 16/92Stored blocklist matches: 1Google Safe Browsing: threat flag recorded
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Analysis
Domain summary
PhishDestroy first recorded app.googleoa.com on 2026-10-06. Stored VirusTotal result: 16/92 engines flagged. Malicious: 15. Suspicious: 1. Analysis time (as stored): 2026-10-02 16:26 UTC. Retrieved (as stored): 2026-10-21 13:16 UTC. Google Safe Browsing flags it. Risk: critical (evidence score 100/100). Registrar: Xin Net Technology. Status: Last known active. Hosting: TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN. Listed by external blocklists: Phishunt. Do not enter credentials or connect a wallet.
app.googleoa.com hosts a phishing page that pretends to be a Google service. It targets anyone who trusts a Google domain, attempting to capture login credentials. PhishDestroy first identified the site on 2026-10-06. As of 2026-10-19 the page is still alive and returns a reachable redirect.
How the scam works
The page displays a Google‑look‑alike login form and asks visitors to enter their email address and password. Submitted credentials are captured and can be used to hijack accounts or for further fraud. Because the site uses a valid TLS certificate from Let’s Encrypt, the connection appears secure, increasing victim trust.
Evidence
VirusTotal scans flag the domain with 16 detections out of 92 engines, including BitDefender, CRDF, CyRadar, DNS8, ESET, Forcepoint ThreatSeeker, Fortinet and G‑Data. Google Safe Browsing lists the site as a SOCIAL_ENGINEERING threat. The domain is also listed on PhishDestroy and Phishunt blocklists.
Infrastructure
The domain was registered on 2009-08-09 through Xin Net Technology Corporation. It is hosted on IP 119.28.83.45, part of the TENCENT‑NET‑AP‑CN network located in Hong Kong. The site presents a Let’s Encrypt / YR2 TLS certificate.
What to do
Anyone who entered Google credentials on this page should change their password immediately and enable two‑factor authentication. Review recent account activity and revoke any unknown sessions or authorized apps. If a Google account was linked to other services, update those credentials as well. Security teams should add app.googleoa.com to blocklists, monitor DNS queries for the domain, and share indicators of compromise with partners.
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
The site app.googleoa.com is an impersonation phishing page that mimics Google to steal credentials from Google users, first seen by PhishDestroy on 2026-10-06.
AI summary
Overview app.googleoa.com hosts a phishing page that pretends to be a Google service. It targets anyone who trusts a Google domain, attempting to capture login credentials. PhishDestroy first identified the site on 2026-10-06. As of 2026-10-19 the page is still alive and returns a reachable redirect. How the scam works The page displays a Google‑look‑alike login form and asks visitors to enter their email address and password. Submitted credentials are captured and can be used to hijack accounts or for further fraud. Because the site uses a valid TLS certificate from Let’s Encrypt, the connection appears secure, increasing victim trust. Evidence VirusTotal scans flag the domain with 16 detections out of 92 engines, including BitDefender, CRDF, CyRadar, DNS8, ESET, Forcepoint ThreatSeeker, Fortinet and G‑Data. Google Safe Browsing lists the site as a SOCIAL_ENGINEERING threat. The domain is also listed on PhishDestroy and Phishunt blocklists. Infrastructure The domain was registered on 2009-08-09 through Xin Net Technology Corporation. It is hosted on IP 119.28.83.45, part of the TENCENT‑NET‑AP‑CN network located in Hong Kong. The site presents a Let’s Encrypt / YR2 TLS certificate. What to do Anyone who entered Google credentials on this page should change their password immediately and enable two‑factor authentication. Review recent account activity and revoke any unknown sessions or authorized apps. If a Google account was linked to other services, update those credentials as well. Security teams should add app.googleoa.com to blocklists, monitor DNS queries for the domain, and share indicators of compromise with partners. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a10b50-0ea5-73ab-a29a-2eeb35bb819b/ VirusTotal report: https://www.virustotal.com/gui/domain/app.googleoa.com Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=app.googleoa.com Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
The owner of the website is using a service to hide their identity on WHOIS According to Tranco this site has a low rank This site is a website within another website The registrar has a high % of spammers and fraud sites This website has been marked as threat by DNSFilter in the last 30 days
The SSL certificate is valid This website is (very) old
Questions about app.googleoa.com
Is app.googleoa.com legit?
PhishDestroy rates app.googleoa.com as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-10-06. Stored VirusTotal result: 16/92 engines flagged. Malicious: 15. Suspicious: 1. Analysis time (as stored): 2026-10-02 16:26 UTC. Retrieved (as stored): 2026-10-21 13:16 UTC. Google Safe Browsing flags it. Listed by external blocklists: Phishunt. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is app.googleoa.com safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on app.googleoa.com. A confirmed blockchain transaction cannot be reversed.
What should I do if I used app.googleoa.com?
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Downloaded a file — do not open it and scan the device with security software
Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.
Google Safe BrowsingFlaggedSocial engineeringchecked 2026-10-20
IP Reputation119.28.83.450/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worseThis IP address has not been reported to the abuse database yet, but the domain itself is recognized as phishing.0 reportschecked 2026-11-06
Certificate fingerprintafe3f2a75e3a454f8ed5b89af59bbac8342bd6b0a8839266b47d95be3b578b63Certificate names · 1 SAN
app.googleoa.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-11-22 11:34 UTC
RDAP registration
Observed timelinelast reachable: 2026-11-22 11:34 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.
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 02:25 UTC.
Recorded events: 15. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The domain remains reachable or access-restricted; future checks may update this observation.
ongoing
Recorded activity
4 entries
Lifecycle
Domain registered
VirusTotal analysis with detections+6263 d 11 h
Added to PhishDestroy+4 d 1 h
Google Safe Browsing
Threat flag recorded
+13 d 15 h
Added to PhishDestroy
app.googleoa.com
+32 h 56 min
URLScan
Malicious · engine verdict · score 86
+64 h 39 min
VirusTotal
16/92 engine detections
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.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Same automated brand label: Google8
Reports with the same collector label. A shared label does not establish impersonation or common ownership. View matching reports →
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Downloaded a file — do not open it and scan the device with security software
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including app.googleoa.com)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
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 →
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.