jsap.or.jp valuation and analysis
Robots.txt Information
| Robot | Path | Permission |
| GoogleBot | / | ✔ |
| BingBot | / | ✔ |
| BaiduSpider | / | ✔ |
| YandexBot | / | ✔ |
Meta Tags
| Title | |
| Description | N/A |
| Keywords | N/A |
Server Information
| WebSite | |
| Host IP | 219.163.46.178 |
| Location | Japan |
Related Websites
| Site | Rank |
More to Explore
jsap.or.jp Valuation
|
US$2,553,499
Last updated:
jsap.or.jp has Semrush global rank of 4,145,021. jsap.or.jp has an estimated worth of US$ 2,553,499, based on its estimated Ads revenue. jsap.or.jp receives approximately 294,635 unique visitors each day. Its web server is located in Japan, with IP address 219.163.46.178. According to SiteAdvisor, jsap.or.jp is safe to visit. |
Traffic & Worth Estimates
| Purchase/Sale Value | US$2,553,499 |
| Daily Ads Revenue | US$2,358 |
| Monthly Ads Revenue | US$70,713 |
| Yearly Ads Revenue | US$848,548 |
| Daily Unique Visitors | 19,643 |
| Note: All traffic and earnings values are estimates. | |
DNS Records
| Host | Type | TTL | Data |
| jsap.or.jp. | A | 1990 | IP: 219.163.46.178 |
| jsap.or.jp. | NS | 2000 | NS Record: dns2.broadline.ne.jp. |
| jsap.or.jp. | NS | 2000 | NS Record: dns1.broadline.ne.jp. |
| jsap.or.jp. | MX | 2000 | MX Record: 5 alt1.aspmx.l.google.com. |
| jsap.or.jp. | MX | 2000 | MX Record: 1 aspmx.l.google.com. |
| jsap.or.jp. | MX | 2000 | MX Record: 50 mail.jsap.or.jp. |
| jsap.or.jp. | MX | 2000 | MX Record: 10 aspmx2.googlemail.com. |
| jsap.or.jp. | MX | 2000 | MX Record: 50 mail2.jsap.or.jp. |
| jsap.or.jp. | TXT | 2000 | TXT Record: v=spf1 include:asp.cuenote.jp ip4:52.192.133.18 ip4:219.163.46.178 ip4:153.125.225.21 include:_spf.google.com ip4:199.255.192.0/22 ip4:199.127.232.0/22 ip4:54.240.0.0/18 ip4:69.169.224.0/20 include:spf.bserver.jp ~all |
| jsap.or.jp. | TXT | 2000 | TXT Record: ciscocidomainverification=3fc053b559b8cee59a42c3d2eb17afe96c7114c62123160ae7244fe0fb54df0f |
jsap.or.jp Whois Information
Cannot process your search request. Service currently unavailable due to incoming of a large amount of requests. Try again later. |