Skip to security report
app.googleoa.com favicon
Domain security and threat intelligence

app.googleoa.com

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

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.

VirusTotal detections: 16/92 Stored blocklist matches: 1 Google Safe Browsing: threat flag recorded
Registrar
Xin Net Technology
Resolved IP
Hong Kong SAR China119.28.83.45Tencent Building, Kejizhongyi Avenue
Registered
2009-08-09
First seen by PhishDestroy
2026-10-06
URLScan
engine verdict · score 86
Page captures
open gallery
Domain age
registered 2009-08-09 according to RDAP · source data differ
2026-10-06

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

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.

Critical
Status
Last known active
VirusTotal
16 / 92
Blocklist matches
1 external + PhishDestroy list
Scam type (automated label)
Impersonation
Hosting
Hong Kong SAR China119.28.83.45Tencent Building, Kejizhongyi Avenue
Registrar
Xin Net Technology
Registered
2009-08-09
Page captures
8

PhishDestroy analysis, earlier unreviewed version

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.

Source evidenceVirusTotal 16 / 92 · Google Safe Browsing: flagged 7 sources

VirusTotal

16 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 13 fields
Separate collector summary

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.

Source
VirusTotal
Result state
observed
Numerator
16
Denominator
92
Vendors
BitDefender, CRDF, CyRadar, DNS8, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Google Safe Browsing, Gridinsoft, Lionic, SOCRadar, Sophos, URLQuery, VIPRE, Webroot
Observed at
2026-10-02 16:26:56
Checked at
2026-10-19 10:49:03
Fetched at
2026-10-19 08:49:03

Google Safe Browsing

Threat flag recorded

Open report

URLScan

Page capture

SHA-256 821aaa9c…ac61591

Open report
URLScanOriginal source recordObserved: 21 fields
Separate monitor record · 2026-10-07 03:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a10b50-0ea5-73ab-a29a-2eeb35bb819b
Score
0
Malicious
✗
Result at
2026-10-07T03:30:38Z
Enriched at
2026-10-07T08:19:41Z
Source timestamps
Urlscan result at: 2026-10-07 05:30:38; Urlscan enriched at: 2026-10-07 10:19:41

PhishDestroy DOM

98 / 100 · heuristic score · 0 brand references · 1 classification

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 0 / 100 · 2026-10-06 22:20 UTC

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

Heuristic score
0
Analyzed at
2026-10-06T22:20:47Z
Source timestamp
2026-10-07 00:20:47
Technical metadata

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

AI title
app.googleoa.com — Impersonation Phishing Page (Google)
AI description
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/
AI generated by
threat-groq
AI generated at
2026-10-19T09:17:29Z
Revision
a1b5e8b0322b1584e5b9af5625a892a175ef9dcd0f80018de149a4384deeebfe
Mode
stored
Interpretation
Earlier stored analysis, not reviewed; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 22 fields

CAA records

Domain
app.googleoa.com

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Crawler rules

User agents
  • *
Present
Yes

Trackers

Requests
18

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
302
Request timings, ms
DNS
672
TLS
193
Waiting
491
Connection
190
Download
0
Response time, ms
1546

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 21
  • 22
  • 80
  • 443

Carbon estimate

Bytes
12504
CO₂, grams
0.0005
Cleaner than, %
67

DNS servers

Nameservers
  • IP address
    117.89.178.173
    Host
    ns19.xincache.com
  • IP address
    1.12.0.1
    Host
    ns20.xincache.com
DNS zone
googleoa.com

Cookies

Cookies
  • Name
    appgoogleoacom_session
    Secure
    Yes
    HTTP-only
    Yes
  • Name
    XSRF-TOKEN
    Secure
    Yes

Location

IP address
119.28.83.45
ASN
132203
Organization
ComsenzNet
City
Hong Kong
Country
HK

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
app.googleoa.com

DNS records

A
  • 119.28.83.45

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31536000
Observation
HSTS header does not include all subdomains.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
max-age=31536000
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
119.28.83.45
IP version
4

Redirects

Redirect chain
  • https://app.googleoa.com
  • https://app.googleoa.com/login
Count
1

Page links

Internal links
2

Registration record

Registrar
Xin Net Technology Corporation
Registered
Updated
Expires
Status
  • ok https://icann.org/epp
Nameservers
  • ns19.xincache.com
  • ns20.xincache.com

HTTP headers

Response headers
Server
nginx
Content-Type
text/html; charset=UTF-8
Strict-Transport-Security
max-age=31536000
Original source fields · JSON
Caa records
Domain: app.googleoa.com
Protective DNS results
Resolvers: 12; Blocked count: 0
Crawler rules
Agents: *; Present: ✓
Trackers
Requests: 18
Forms and mixed content
Third party scripts: 0
Status
Up: ✓; Code: 302; Timings: DNS: 672; TLS: 193; Wait: 491; Connect: 190; Download: 0; Response ms: 1546
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 21, 22, 80, 443
Carbon
Bytes: 12504; Co2 grams: 0.0005; Cleaner than: 67
DNS server
NS: (IP: 117.89.178.173; Host: ns19.xincache.com), (IP: 1.12.0.1; Host: ns20.xincache.com); Zone: googleoa.com
Cookies
Cookies: (Name: Appgoogleoacom session; Secure: ✓; HTTP only: ✓), (Name: XSRF-TOKEN; Secure: ✓)
Location
IP: 119.28.83.45; ASN: 132203; Org: ComsenzNet; City: Hong Kong; Country: HK
SSL
Issuer: Let's Encrypt / YR2; Subject: app.googleoa.com
DNS records
A: 119.28.83.45
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Header: max-age=31536000; Message: HSTS header does not include all subdomains.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: max-age=31536000; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 119.28.83.45; Family: 4
Redirects
Chain: https://app.googleoa.com, https://app.googleoa.com/login; Count: 1
Page links
Internal count: 2
Registration record
Registrar: Xin Net Technology Corporation; Created: 2009-08-09T04:31:49Z; Updated: 2026-07-07T03:35:22Z; Expires: 2027-08-09T04:31:49Z; Status: ok https://icann.org/epp; Nameservers: ns19.xincache.com, ns20.xincache.com
HTTP headers
Headers: Server: nginx; Content type: text/html; charset=UTF-8; Strict transport security: max-age=31536000
Security Signals
SA Scamadviser Warnings 1/100
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.

Explore

Blocklist matches1 external + PhishDestroy list · PhishDestroy · Phishunt 1
PhishDestroy PhishDestroy list View source
Phishunt Listed View source

Last checked

Page captures (8)

All capture links and hashes (8)
app.googleoa.com: Google impersonation — Flagged by Phishunt, Google Safe Browsing, 16/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card app.googleoa.com: Google impersonation — Flagged by Phishunt, Google Safe Browsing, 16/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v dd5353fdec65

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 86 report ↗
Google Safe Browsing Flagged Social engineering checked 2026-10-20
IP Reputation Hong Kong SAR China119.28.83.45 0/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worse This IP address has not been reported to the abuse database yet, but the domain itself is recognized as phishing. 0 reports checked 2026-11-06
Registrar (base domain) Xin Net Technology
Registration (base domain)googleoa.com · Created 2009-08-09 — Expires 2027-08-09
WHOIS statusNo restrictions
HTTP Status302 Found (Temporary)
Technical detailsProvenance & timestamps
First Detected2026-10-06
DOM Analysisanalyzed 2026-10-09score 98/100
Submitted URLhttps://app.googleoa.com/
Favicon Hash
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 36 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Hong Kong SAR China119.28.83.45
Network ASN
AS132203
AS name
TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN
Organization
Tencent Building, Kejizhongyi Avenue
Observed location
Hong Kong SAR ChinaHong Kong, HK
Server header
nginx

Nameservers 1

  • ns20.xincache.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-09-29 21:30:41
Valid until
2026-12-28 21:30:40
Hostname match
Yes
Validity
Within stored validity dates
Collection time
2026-10-11 07:02 UTC
Collection source
PhishDestroy collector
Certificate fingerprintafe3f2a75e3a454f8ed5b89af59bbac8342bd6b0a8839266b47d95be3b578b63
Certificate 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 Classified Outcome 2026-11-22 11:34 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting DNS: Resolved
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-11-22 11:34 UTC
RDAP registration
Observed timeline last 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.
Technologies · 5 identified
Open complete records

VirusTotal Analysis

16 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 16 detections
CRDF
DNS8
ESET
VIPRE
G-Data
Lionic
Sophos
CyRadar
Webroot
Fortinet
SOCRadar
URLQuery
Gridinsoft
BitDefender
Google Safe Browsing
Forcepoint ThreatSeeker
PageSpeed (mobile): 88

Google PageSpeed Insights — mobile performance audit of app.googleoa.com ·

88
Needs Work
Performance
FCP
2.85 s
First Contentful Paint
LCP
2.85 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
4.36 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data113
Open complete records

Captured network requests

Network requests: 19 SHA-256 hashes: 19 URLScan scan:

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.

Open this scan on URLScan 01a10b50-0ea5-73ab-a29a-2eeb35bb819b ↗

Stored observation history28
Open complete records
All retained availability observations207
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 15. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    app.googleoa.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Google Safe Browsing · Blocklist Detection · Automated brand label: Google · Forensic Evidence Collected · Technical Analysis Recorded · VirusTotal detections +1 · VirusTotal detections −1 · VirusTotal detections +1 · VirusTotal detections +14 recorded
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+6263 d 11 h
  3. Added to PhishDestroy+4 d 1 h
  1. Google Safe Browsing

    Threat flag recorded

    +13 d 15 h
  2. Added to PhishDestroy

    app.googleoa.com

    +32 h 56 min
  3. URLScan

    Malicious · engine verdict · score 86

    +64 h 39 min
  4. 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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

app.googleoa.com

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

After a phishing incident

Recommendations & Advice for Victims

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)
  • Europol — European cybercrime reporting (EU)
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/app.googleoa.com"
  title="PhishDestroy threat report for app.googleoa.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>