docs-google.one is an Openai impersonation page detected by PhishDestroy on 2026-10-19. Risk: critical (98/100). Registrar: Porkbun. Status: Last known active. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. VirusTotal: 2/92 engines flag it. Do not enter credentials or connect a wallet.
Security engines reporting a detection: 2. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 72H+ 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@porkbun.com.
The latest stored availability evidence still shows the domain reachable; 3 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.
docs-google.one is a phishing site that pretends to be a Google Docs page. It targets users of Google services by attempting to harvest their login credentials. PhishDestroy first recorded the domain on 2026-10-19. The site is still alive but its content was unreachable when last checked on 2026-10-19.
How the scam works
The page displays an empty document titled “Untitled Document” and immediately asks the visitor to sign in with a Google account. The login form is a replica of Google’s authentication page, so entered usernames, passwords and any two‑factor codes are captured by the attackers. With those credentials the criminals can access the victim’s Google account, email, Drive files and any linked services.
Evidence
VirusTotal flagged the domain in 2 of 92 scanners, with CRDF and Gridinsoft reporting it as malicious. PhishDestroy, MetaMask and SEAL have added the domain to their blocklists, and three OTX pulses reference it. The low number of detections still confirms its phishing nature.
Infrastructure
The domain was registered on 2026-10-15 through Porkbun, only four days before PhishDestroy’s first sighting. It is hosted behind Cloudflare’s network (IP 162.159.143.30) in Canada, which masks the true server location. The TLS certificate is issued by Google Trust Services / WE1, giving the site a legitimate‑looking HTTPS lock.
What to do
Anyone who entered a Google username, password or 2FA code on docs-google.one should immediately change their Google password and enable or refresh two‑factor authentication. Review recent account activity and revoke any unknown third‑party app permissions. Security teams should block the domain at the DNS and proxy level, add it to phishing blocklists, and monitor for any credential‑stuffing attempts using harvested accounts.
No. PhishDestroy classifies docs-google.one as an Openai impersonation page (risk: critical, 98/100); it was first detected on 2026-10-19. VirusTotal: 2/92 engines flag it. Treat the site as unsafe.
Is docs-google.one safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on docs-google.one. 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 docs-google.one?
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 15, 2026 (7d · Very New!)—Expires Oct 15, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 19, 2026
DOM Analysisanalyzed Oct 19, 2026score 98/1001 brand signal
Submitted URLhttp://docs-google.one/
Favicon Hash
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
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.
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:27:33 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-22 10:27:33 UTClast content: 2026-10-22 10:27:33 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 · 1 identified
Cloudflare
CDN
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · docs-google.one
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.
Content matches6
Same favicon hash or the same page title as this host.
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 docs-google.one)
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.
(US)
