Recent Nameserver Activity: SURGESERVERS.NET

Now displaying nameserver activity for surgeservers.net for the date of February 09, 2012.

Nameserver History

The domain surgeservers.net was registered on April 25, 2004, and we have nameserver history going back to March 26, 2005. It is listed as a nameserver for 1,687 domains and is listed as the primary nameserver for 1,686 domains, including:

  • 1,337 .COM domains
  • 157 .NET domains
  • 146 .ORG domains
  • 14 .INFO domains
  • 17 .BIZ domains
  • 15 .US domains

Nameserver Management

The domain owner for surgeservers.net is listed as Nine Dot Systems, which is associated with 271 domains.

Use Reverse WHOIS to find all domain names owned by this domain name owner.

Review historical hosting & historical Whois records for surgeservers.net at DomainTools.com.

Get the complete list of all 1,686 domain names hosted on surgeservers.net

Nameserver Hosts

The Nameserver surgeservers.net uses 2 unique addresses to provide its service. You can find information for all of these below.

  • NS2.SURGESERVERS.NET
  • IP Address
    67.215.247.94
    Location
    UNITED STATES
    Managed By
    SECURED PRIVATE NETWORK
    Domains
    1,688
  • NS1.SURGESERVERS.NET
  • IP Address
    173.208.152.227
    Location
    UNITED STATES
    Managed By
    JASON KUBERKA
    Domains
    1,687
Want to access this activity page for surgeservers.net later? Here's the Permalink for 02/09/2012 >

Domain Names Transferred Into SURGESERVERS.NET

Currently displaying 1 of 1 domain names transferred into surgeservers.net on February 9, 2012.
Download all surgeservers.net activity for February 9, 2012(.CSV)
Domain Name Transferred From
nantahala-farm.com ajtdesign.com
Download all surgeservers.net activity for February 9, 2012(.CSV)
Nameserver / Domain Name Ownership: Whois Search
Tell us a nameserver, domain name or IP address and we'll tell you all about its ownership.
© 2012 DomainTools, LLC All rights reserved. Any and all use of DailyChanges.com is subject to the conditions set out in our Terms of Service document.