Haolifaye.com was registered on xin net technology corporation on 24 March 2006.
The site is almost absent on social networks.
The site receives 1,140 visitors every month, which put its worth at around $ approximately.
The website has a good alexa rank of 2,965,605.
The site is hosted in China by CHINANET Guangdong province network.
The domain for the website was purchased through xin net technology corporation on 24 March 2006 (11 years ago) and will expire in 4 months 2 days.
Alexa Rank 2,965,605
Visitors 30 daily
Approx. Yearly Revenue $113
Text lanuage None
Family safe text Yes
The report was last updated on May 08, 2016.
If its not up to date, please click the update button for the same.
Social Network Presence
Following statistics represent haolifaye.com activity on various social networks.
Find out about the infrastructure of haolifaye.com, e.g. how the website works, what hardware and software it uses etc.
Data Communication Division, China Telecom, China
Email hosted by
Web Hosting Provider
CHINANET Guangdong province network
Site Generating Software
SSL Certificate Issuer
Domain Registered by
xin net technology corporation
These records can help to identify the owners of haolifaye.com. You can contact the admins through the email present in these records.
24 March 2006
24 March 2017
Domain Name: HAOLIFAYE.COM
Registrar: XIN NET TECHNOLOGY CORPORATION
Sponsoring Registrar IANA ID: 120
Whois Server: whois.paycenter.com.cn
Name Server: NS19.XINCACHE.COM
Name Server: NS20.XINCACHE.COM
Status: ok Updated Date: 25-mar-2016
Creation Date: 24-mar-2006
Expiration Date: 24-mar-2017
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 Data Communication Division, China Telecom, China
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 haolifaye.com, it could be because the site was offline when the report was created!