Google secures GoogleDrive.com and updates name servers
Google already owns GDrive.com, but it's unlikely that will be the final name of the service. Like Gmail is technically "Google Mail", the real name for GDrive will likely be "Google Drive". So that got me wondering about the domain "GoogleDrive.com".
Context & Ripple Effects
A week after GDrive references surfaced in Google Apps, the company has quietly picked up GoogleDrive.com and pointed its name servers at its own infrastructure — following the same playbook documented in ResourceShelf's 2006 roundup of Google's steady domain-name acquisitions. Google already holds GDrive.com, but the Gmail precedent — technically "Google Mail" — suggests the eventual consumer brand would be "Google Drive", which would make this week's pickup the matching domain.
First-order effects
- Google now controls both plausible names for a consumer storage service, closing off a parked-domain or typosquat position on GoogleDrive.com before any product exists to defend.
- The name-server update puts the domain under Google's own infrastructure, the usual preparatory step before a property goes live.
Second-order effects
- Domain watchers now have a concrete timing tell: if GDrive ships, the branding question ("GDrive" vs "Google Drive") resolves by watching which of the two domains activates first — and rivals in online storage get an early signal of Google's entry.
- The move pressures other web companies to sweep up brand-plus-product domains well ahead of launches, since leaving them unregistered invites exactly this kind of speculation.
Third-order effects
- DNS records become a de facto public pre-announcement channel for large web companies — product roadmaps leaking through registrar data rather than press releases, and analysts reading name-server changes the way they once read trademark filings.
The trend: Web platforms are accumulating product-name domains years ahead of launch, turning registrar activity into an early-warning signal for where they intend to compete.