Editing Network Solutions (section)

===Controversy over subdomain hijacking===
In April 2008, reports indicated that in addition to the aforementioned front-running practices, Network Solutions had begun exploiting an obscure provision of its [[end-user license agreement]] that permits it to use and advertise on its users' unassigned [[subdomain]]s, even despite the registration and private ownership of the top-level domain itself.<ref>{{cite news|title=Network Solutions Hijacking Unassigned Sub-Domains|url=https://techcrunch.com/2008/04/08/network-solutions-hijacking-unassigned-sub-domains/|work=techcrunch.com|access-date=2008-04-12}}</ref> The provision states: <blockquote>
'You also agree that any domain name directory, sub-directory, file name or path (e.g.) that does not resolve to an active web page on your Web site being hosted by Network Solutions, may be used by Network Solutions to place a "[[Domain parking|parking]]" page, "under construction" page, or other temporary page that may include promotions and advertisements for, and links to, Network Solutions' Web site...'"<ref>{{cite web|title=Service Agreement (Schedule A #11)|url=http://www.networksolutions.com/legal/static-service-agreement.jsp|publisher=networksolutions.com|access-date=2008-04-12}}</ref>
</blockquote>
[[Ars Technica]] has documented how to opt out of this scheme,<ref>{{cite web|title=Keeping Network Solutions from cashing in on your subdomains|url=https://arstechnica.com/news.ars/post/20080410-keeping-network-solutions-from-cashing-in-on-your-subdomains.html|website=[[Ars Technica]]|date=April 10, 2008 |access-date=2008-04-12}}</ref> but many{{who|date=June 2014}} private domain holders and privacy advocates cite the move as another step in Network Solutions' series of recent attempts to push the boundaries of profitability and responsibility in its domain practices.{{citation needed|date=June 2014}}<ref>{{cite web|title=Support and Services (Schedule A #11)|url=http://alldatalabs.com|publisher=alldatalabs.com|access-date=2016-01-04}}</ref>