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@cosmotown.com.
The latest stored availability evidence still shows the domain reachable; 13 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.
googlebusiness.xyz is an impersonation phishing domain built around the Google name, with a domain that suggests Google's business tools. That framing targets business owners and staff who manage company listings, ads or workspace accounts. PhishDestroy first flagged it on 2026-10-08, and as of 2026-10-19 the site was still online and serving a redirect. The live page carries the title "The Jet Finder | Private Jet Sales, Charter," which does not match the Google impersonation it was classified under.
How the scam works
Schemes using a Google business lure usually arrive as an urgent notice about a business profile, a suspended listing, an ad account problem or a verification step. The link sends the victim to a page that copies Google's look and asks them to sign in or confirm details. Anything typed there goes to the operator. That can include the Google account password, one-time codes and sometimes billing information. A hijacked account can hand over email, documents, ad spend and control of the company's public listing.
Evidence
Google Safe Browsing classifies the domain as social engineering, the category it uses for phishing. On VirusTotal, 17 of 92 engines flagged it on 2026-10-08, including BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, alphaMountain.ai, ADMINUSLabs, CyRadar and DNS8. Several major vendors reaching the same verdict independently makes it hard to dismiss as a single false positive. The domain also appears on the Phishunt blocklist and in four AlienVault OTX threat pulses.
Infrastructure
The domain was registered on 2026-03-07 through TuringSign Inc. d/b/a Cosmotown. That is roughly seven months before PhishDestroy detected it, so it sat registered for a long stretch before the phishing activity surfaced. Traffic is fronted by Cloudflare, with the address geolocated to Canada. Because Cloudflare acts as a proxy, the origin server behind it is hidden.
What to do
If you entered a Google password on this site, change it immediately from a device you trust. Sign out all other sessions and review recent security activity and connected apps in your Google account. Turn on two-factor authentication, preferably with a security key or authenticator app, and change the password anywhere you reused it. Business owners should check their business profile and ad accounts for new managers, changed details or unexpected charges. If you entered card details, contact your card issuer. Defenders should block the domain at DNS and web proxies and search mail logs for messages linking to it.
{
"Sophos": "phishing and fraud",
"Webroot": "Phishing and Other Frauds",
"alphaMountain.ai": "Personal Sites/Blogs, Phishing (alphaMountain.ai)",
"Forcepoint ThreatSeeker": "phishing and other frauds"
}
DOM Analysisanalyzed 2026年10月9日score 100/1003 brand signals
Submitted URLhttps://googlebusiness.xyz/
Favicon Hash
案件 ID
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Certificate fingerprint550be9849d4de7c747a464a0e4b5cdcbae6d149b2bda017e8af403d774c14ecfCertificate names · 2 SANs
*.googlebusiness.xyz
googlebusiness.xyz
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-10-21 10:29:36 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-21 10:29:36 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.
Recorded subdomains19
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
1a07f04f-e59f-4aa5-a0b2-676bc4213bfe.googlebusiness.xyzDomain record
1ac4e9d3-b560-41eb-9be8-36891e990e03.googlebusiness.xyzDomain record
35964e5d-dd22-4481-8b33-1cb951734f39.googlebusiness.xyzDomain record
4fbb406d-fd1b-44f6-8bfc-58197b5d59e1.googlebusiness.xyzDomain record
6eb0c87352ec.googlebusiness.xyzDomain record
74559214-f302-4806-82d3-2120a1e022f2.googlebusiness.xyzDomain record
7a219667-e55c-4ba2-8812-a5185343fc28.googlebusiness.xyzDomain record
admin.googlebusiness.xyzDomain record
aftkpblog.googlebusiness.xyzDomain record
ahnsjbpd.googlebusiness.xyzDomain record
api.googlebusiness.xyzDomain record
app.googlebusiness.xyzDomain record
dc-mx.6eb0c87352ec.googlebusiness.xyzDomain record
www.4fbb406d-fd1b-44f6-8bfc-58197b5d59e1.googlebusiness.xyzDomain record
www.6eb0c87352ec.googlebusiness.xyzDomain record
www.74559214-f302-4806-82d3-2120a1e022f2.googlebusiness.xyzDomain record
www.admin.googlebusiness.xyzDomain record
www.aftkpblog.googlebusiness.xyzDomain record
www.api.googlebusiness.xyzDomain record
The original observation time is not recorded for these hostnames.
技术 · 2 identified
H
HSTS
安全
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
我应该立即采取什么措施？
紧急
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
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?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(US)
