Havokhosting.com was registered on domain.com, llc on 05 December 2015.
The site is almost absent on social networks.
The site is hosted in United States by tw telecom holdings, inc..
The domain for the website was purchased through domain.com, llc on 05 December 2015 (1 year ago) and will expire in 10 months 22 days.
Text lanuage None
Family safe text Yes
The report was last updated on December 29, 2015.
If its not up to date, please click the update button for the same.
Social Network Presence
Following statistics represent havokhosting.com activity on various social networks.
Find out about the infrastructure of havokhosting.com, e.g. how the website works, what hardware and software it uses etc.
10475 Park Meadows Drive, Littleton, CO, United States
Email hosted by
Web Hosting Provider
tw telecom holdings, inc.
Site Generating Software
SSL Certificate Issuer
Domain Registered by
These records can help to identify the owners of havokhosting.com. You can contact the admins through the email present in these records.
05 December 2015
05 December 2017
Whois Server Version 2.0
Domain Name: HAVOKHOSTING.COM
Registrar: DOMAIN.COM, LLC
Sponsoring Registrar IANA ID: 886
Whois Server: whois.domain.com
Name Server: NS1.DOMAIN.COM
Name Server: NS2.DOMAIN.COM
Status: clientTransferProhibited Status: clientUpdateProhibited Updated Date: 05-dec-2015
Creation Date: 05-dec-2015
Expiration Date: 05-dec-2017
For more information on Whois status codes, please visit
The Registry database contains ONLY .COM, .NET, .EDU domains and
Maximum Daily connection limit reached. Lookup refused.
Find out all the details about the IP address used by the website, including the nameservers and IP location.
No. of IP Addresses 1
IP Location 10475 Park Meadows Drive, Littleton, CO, United States
Following are the links associated with the homepage of the website.
Following information represents the extra metadata sent by the website servers on requesting the homepage of the website.
No HTTP Headers were found for havokhosting.com, it could be because the site was offline when the report was created!