Minibarber.com was registered on hichina zhicheng technology ltd. on 13 July 2015.
The site is almost absent on social networks.
The site receives 2,460 visitors every month, which put its worth at around $ approximately.
The website has a good alexa rank of 1,553,746.
The domain for the website was purchased through hichina zhicheng technology ltd. on 13 July 2015 (1 year ago) and will expire in 10 months 17 days.
Alexa Rank 1,553,746
Visitors 70 daily
Approx. Monthly Revenue $19
Text lanuage None
Family safe text Yes
The report was last updated on December 19, 2015.
If its not up to date, please click the update button for the same.
Social Network Presence
Following statistics represent minibarber.com activity on various social networks.
Find out about the infrastructure of minibarber.com, e.g. how the website works, what hardware and software it uses etc.
Email hosted by
Web Hosting Provider
Site Generating Software
SSL Certificate Issuer
Domain Registered by
hichina zhicheng technology ltd.
These records can help to identify the owners of minibarber.com. You can contact the admins through the email present in these records.
13 July 2015
13 July 2016
Whois Server Version 2.0
Domain Name: MINIBARBER.COM
Registrar: HICHINA ZHICHENG TECHNOLOGY LTD.
Sponsoring Registrar IANA ID: 420
Whois Server: grs-whois.hichina.com
Name Server: DNS10.HICHINA.COM
Name Server: DNS9.HICHINA.COM
Status: ok Updated Date: 13-jul-2015
Creation Date: 13-jul-2015
Expiration Date: 13-jul-2016
For more information on Whois status codes, please visit
The Registry database contains ONLY .COM, .NET, .EDU domains and
No match for domain "minibarber.com".
Find out all the details about the IP address used by the website, including the nameservers and IP location.
No IP information found for the website!!
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 minibarber.com, it could be because the site was offline when the report was created!