Free traffic, earnings, ip, location, rankings report for h.hatena.ne.jp

h.hatena.ne.jp snoop summary

This is a free and comprehensive report about h.hatena.ne.jp. h.hatena.ne.jp is hosted in on a server with an IP address of The website h.hatena.ne.jp is expected to be earning an estimated $0 USD on a daily basis. If h.hatena.ne.jp was to be sold it would possibly only be worth $10 USD (the typical cost of the registration fee for the domain name). According to our google pagerank analysis, the url h.hatena.ne.jp currently has a pagerank of /10. h.hatena.ne.jp possibly receives an estimated 0 unique visitors every day - this website is not very popular.

h.hatena.ne.jp information and statistics

Website / Domain: h.hatena.ne.jp
Website IP:
Alexa Rank: 17,836,828
Google Index: View h.hatena.ne.jp Google Links
Yahoo Index: View h.hatena.ne.jp Yahoo Links
Bing Index: View h.hatena.ne.jp Bing Links
History: View h.hatena.ne.jp on WayBackMachine

h.hatena.ne.jp traffic and earnings

Purchase/Sale Value: $10 USD
Daily Revenue: $0 USD
Monthly Revenue: $0 USD
Yearly Revenue: $0 USD
Daily Unique Visitors: 0
Monthly Unique Visitors: 0
Yearly Unique Visitors: 0
Note: All traffic and earnings values are estimates only.

h.hatena.ne.jp alexa traffic graph (12 month period)

H.hatena.ne.jp Alexa Traffic Graph

h.hatena.ne.jp whois information

1. JPRS WHOIS database includes the following type of information in
TYPE Description
DOM Domain Information
HOST Host Information
CONTACT Contact Information [only for Organization-type .JP domain names]
2. How to get the information:
STRING Broad search over the all types (if available)
To restrict the search to a certain type of information:
TYPE STRING See above for types of information
To obtain related information:
^STRING Displays the information that refers the STRING [only for .JP domain names]
3. Use of the information you obtain from JPRS WHOIS is restricted to
a purely network operation purposes.
*Notice* If you had an intention to search for gTLD domain-related
information and see this message, it is possible that JPRS WHOIS wasn't
the right server to specify. In that case, you might be able to re-try
your search via InterNIC WHOIS.