Okliq.com was registered on bizcn.com, inc. on 25 September 2015.
The site is almost absent on social networks.
0 google plus ones,
0 facebook likes.
The site receives 1,800 visitors every month, which put its worth at around $ approximately.
The website has a good alexa rank of 2,149,730.
The domain for the website was purchased through bizcn.com, inc. on 25 September 2015 (1 year ago) and will expire in 8 months 2 days.
Alexa Rank 2,149,730
Visitors 50 daily
Approx. Monthly Revenue $16
Text lanuage None
Family safe text Yes
The report was last updated on October 26, 2015.
If its not up to date, please click the update button for the same.
Social Network Presence
Following statistics represent okliq.com activity on various social networks.
Find out about the infrastructure of okliq.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
These records can help to identify the owners of okliq.com. You can contact the admins through the email present in these records.
25 September 2015
25 September 2016
Whois Server Version 2.0
Domain Name: OKLIQ.COM
Registrar: BIZCN.COM, INC.
Sponsoring Registrar IANA ID: 471
Whois Server: whois.bizcn.com
Name Server: F1G1NS1.DNSPOD.NET
Name Server: F1G1NS2.DNSPOD.NET
Status: clientDeleteProhibited Status: clientHold Status: clientTransferProhibited Updated Date: 26-oct-2015
Creation Date: 25-sep-2015
Expiration Date: 25-sep-2016
The Registry database contains ONLY .COM, .NET, .EDU domains and
For more information on Whois status codes, please visit
Too Many Connection!
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 okliq.com, it could be because the site was offline when the report was created!