Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
Title | |
Description | N/A |
Keywords | N/A |
WebSite | hokuriku-u.ac.jp |
Host IP | 202.209.208.35 |
Location | Japan |
Site | Rank |
US$329,999
Last updated:
hokuriku-u.ac.jp has Semrush global rank of 32,073,815. hokuriku-u.ac.jp has an estimated worth of US$ 329,999, based on its estimated Ads revenue. hokuriku-u.ac.jp receives approximately 38,077 unique visitors each day. Its web server is located in Japan, with IP address 202.209.208.35. According to SiteAdvisor, hokuriku-u.ac.jp is safe to visit. |
Purchase/Sale Value | US$329,999 |
Daily Ads Revenue | US$305 |
Monthly Ads Revenue | US$9,139 |
Yearly Ads Revenue | US$109,661 |
Daily Unique Visitors | 2,539 |
Note: All traffic and earnings values are estimates. |
Host | Type | TTL | Data |
hokuriku-u.ac.jp. | A | 86400 | IP: 202.209.208.35 |
hokuriku-u.ac.jp. | NS | 86400 | NS Record: ns1.dns.ne.jp. |
hokuriku-u.ac.jp. | NS | 86400 | NS Record: ns.rves.hokuriku-u.ac.jp. |
hokuriku-u.ac.jp. | NS | 86400 | NS Record: ns2.dns.ne.jp. |
hokuriku-u.ac.jp. | NS | 86400 | NS Record: husv01.hokuriku-u.ac.jp. |
hokuriku-u.ac.jp. | NS | 86400 | NS Record: husv02.hokuriku-u.ac.jp. |
hokuriku-u.ac.jp. | MX | 3600 | MX Record: 1 ASPMX.L.GOOGLE.COM. |
hokuriku-u.ac.jp. | MX | 3600 | MX Record: 5 ALT1.ASPMX.L.GOOGLE.COM. |
hokuriku-u.ac.jp. | MX | 3600 | MX Record: 5 ALT2.ASPMX.L.GOOGLE.COM. |
hokuriku-u.ac.jp. | MX | 3600 | MX Record: 10 ALT4.ASPMX.L.GOOGLE.COM. |
hokuriku-u.ac.jp. | MX | 3600 | MX Record: 10 ALT3.ASPMX.L.GOOGLE.COM. |
hokuriku-u.ac.jp. | TXT | 86400 | TXT Record: google-site-verification=T4f-B6MoCpfwxdhGgeH0li7UZteyz9guLG7NzU5cGzU |
hokuriku-u.ac.jp. | TXT | 86400 | TXT Record: v=spf1 include:_spf.google.com include:spf.protection.outlook.com ip4:202.209.208.59 ip4:202.209.208.41 ip4:202.209.208.42 ip4:103.3.2.150 ~all |
hokuriku-u.ac.jp. | TXT | 86400 | TXT Record: MS=ms68220766 |
Cannot process your search request. Service currently unavailable due to incoming of a large amount of requests. Try again later. |