sta.or.jp valuation and analysis
Robots.txt Information
| Robot | Path | Permission |
| GoogleBot | / | ✔ |
| BingBot | / | ✔ |
| BaiduSpider | / | ✔ |
| YandexBot | / | ✔ |
Meta Tags
| Title | DOMAIN |
| Description | hCEFu̐ݒ肪܂ l錴 hCEFu̐ݒ肪܂sĂȂB hCEFu̐ݒ肪܂fĂȂB(fɂ͐ԁ`24Ԃ邱Ƃ܂) hCEFuEDNS̐ݒ肪ĂB |
| Keywords | N/A |
Server Information
| WebSite | |
| Host IP | 150.95.9.156 |
| Location | Japan |
Related Websites
| Site | Rank |
More to Explore
sta.or.jp Valuation
|
US$2,123
Last updated: 2022-09-13 18:12:16
sta.or.jp has Semrush global rank of 0. sta.or.jp has an estimated worth of US$ 2,123, based on its estimated Ads revenue. sta.or.jp receives approximately 244 unique visitors each day. Its web server is located in Japan, with IP address 150.95.9.156. According to SiteAdvisor, sta.or.jp is safe to visit. |
Traffic & Worth Estimates
| Purchase/Sale Value | US$2,123 |
| Daily Ads Revenue | US$1 |
| Monthly Ads Revenue | US$58 |
| Yearly Ads Revenue | US$705 |
| Daily Unique Visitors | 16 |
| Note: All traffic and earnings values are estimates. | |
DNS Records
| Host | Type | TTL | Data |
| sta.or.jp. | A | 3600 | IP: 150.95.9.156 |
| sta.or.jp. | NS | 86400 | NS Record: 03.dnsv.jp. |
| sta.or.jp. | NS | 86400 | NS Record: 04.dnsv.jp. |
| sta.or.jp. | NS | 86400 | NS Record: 01.dnsv.jp. |
| sta.or.jp. | NS | 86400 | NS Record: 02.dnsv.jp. |
| sta.or.jp. | MX | 3600 | MX Record: 0 sta-or-jp.mail.protection.outlook.com. |
| sta.or.jp. | TXT | 3600 | TXT Record: v=spf1 include:spf.protection.outlook.com include:_spf.ex-pa.jp ~all |
| sta.or.jp. | TXT | 3600 | TXT Record: MS=ms19837613 |
HtmlToTextCheckTime:2022-09-13 18:12:16
| hCEFu̐ݒ肪܂ l錴 hCEFu̐ݒ肪܂sĂȂB hCEFu̐ݒ肪܂fĂȂB(fɂ͐ԁ`24Ԃ邱Ƃ܂) hCEFuEDNS̐ݒ肪ĂB |
HTTP Headers
HTTP/1.1 200 OK Date: Fri, 24 Dec 2021 05:59:50 GMT Server: Apache Last-Modified: Sat, 13 May 2017 17:36:04 GMT ETag: "2b9-54f6b41a14b8a" Accept-Ranges: bytes Content-Length: 697 Vary: Accept-Encoding,User-Agent Content-Type: text/html |
sta.or.jp Whois Information
Cannot process your search request. Service currently unavailable due to incoming of a large amount of requests. Try again later. |