support-google.pl is a Google impersonation page detected by PhishDestroy on 2026-10-10. Risk: critical (100/100). Registrar: nazwa.pl sp. z o.o. Status: Last known active. Hosting: NETARTGROUP Nazwa.pl Sp.z.o.o., PL. PhishDestroy sent 1 abuse report. VirusTotal: 10/92 engines flag it. Do not enter credentials or connect a wallet.
Security engines reporting a detection: 10. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@netart.com.
The latest stored availability evidence still shows the domain reachable; 12 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
support-google.pl is a phishing site that impersonates Google by presenting itself as a support portal. It targets Google users who expect help with their accounts. PhishDestroy first flagged it on 2026-10-10. As of 2026-10-19 the site was still online and serving content.
How the scam works
The page title is just the bare domain, so the deception rests on the address itself. A hyphenated name like support-google reads as official at a glance, especially in a link from a message warning about a locked account or a security problem. Fake support pages of this kind steer visitors into entering their Google email and password, one-time codes, or recovery details. Some also push victims to contact a fake support agent. Whatever is typed goes to the operators, who can use it to take over the account and everything linked to it, including email, cloud storage and any crypto services secured through that inbox.
Evidence
On 2026-10-14, 10 of 92 VirusTotal engines classified the domain as malicious. Flagging vendors include alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data and Gridinsoft. That count is modest, so many browsers and filters may still load the page without a warning. The domain is listed on the MetaMask and SEAL blocklists alongside PhishDestroy, which signals concern from crypto-focused defenders. It also appears in two AlienVault OTX threat pulses.
Infrastructure
The domain was registered on 2026-10-09 through nazwa.pl sp. z o.o., one day before PhishDestroy detected it. A gap that short is typical of throwaway phishing domains set up for immediate use. It resolves to 85.128.244.69 on the NETARTGROUP Nazwa.pl network in Poland. Its domain-validated TLS certificate was issued by nazwa.pl's own certificate authority, so registration, hosting and the padlock all come from one provider. The padlock only shows the connection is encrypted and says nothing about whether the site is legitimate.
What to do
If you entered your Google password on this site, change it immediately from the real Google account page. Then review recent security activity and sign out every unfamiliar session. Turn on or reset two-step verification, preferably with a passkey or security key. Check that your recovery email and phone number have not been changed. Change the password on any other service that shared it, and if you gave out a wallet recovery phrase, move your funds to a new wallet at once. Security teams should block the domain and its IP address, search mail and proxy logs for visits, and report it to the registrar and hosting provider.
No. PhishDestroy classifies support-google.pl as a Google impersonation page (risk: critical, 100/100); it was first detected on 2026-10-10. VirusTotal: 10/92 engines flag it. Treat the site as unsafe.
Is support-google.pl safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on support-google.pl. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used support-google.pl?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
RegistrationCreated Oct 9, 2026 (13d · Very New!)—Expires Oct 9, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 10, 2026
DOM Analysisanalyzed Oct 10, 2026score 100/1001 brand signal
Submitted URLhttp://support-google.pl/
Case ID
Observed page title
support-google.pl
Automated brand references
Google
TLS Certificate
Issued by nazwa.pl Sp. z o.o. / nazwaSSL DV TLS G2 E29 CA· stored validity ends in 16 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
85.128.244.69
Network ASN
AS15967
Organization
Nazwa.pl Sp.z.o.o.
Observed location
Kraków, PL
Server header
Apache/2
Nameservers 3
ns1.nazwa.pl
ns2.nazwa.pl
ns3.nazwa.pl
Mail routing 1 MX record
support-google.plpriority 10
Location describes the IP network.
TLS certificate
Issuer
nazwa.pl Sp. z o.o. / nazwaSSL DV TLS G2 E29 CA
Valid from
2026-10-09 12:30:32
Valid until
2026-11-08 00:00:00
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-10 16:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint3859432ca7dd84a1f47ebfee0d6cd82ef92bb32698a3f95047904d8b80062678Certificate names · 1 SAN
www.support-google.pl
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-10-22 10:33:44 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-22 10:33:44 UTClast content: 2026-10-22 10:33:44 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 · 3 identified
A
Apache HTTP Server
Web servers
Apache is a free and open-source cross-platform web server software.
jQuery is a JavaScript library which is a free, open-source software designed to simplify HTML DOM tree traversal and manipulation, as well as event handling, CSS animation, and Ajax.
Google Hosted Libraries is a stable, reliable, high-speed, globally available content distribution network for the most popular, open-source JavaScript libraries.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · support-google.pl
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.
Same automated brand label: Google8
Reports with the same collector label. A shared label does not establish impersonation or common ownership. View matching reports →
6 evidence signal groups linked1 stored notification recordsLast known active
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
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.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
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 support-google.pl)
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
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.
(PL)
