Kentanblog.org valuation and analysis
Robots.txt Information
| Robot | Path | Permission |
| GoogleBot | / | ✔ |
| BingBot | / | ✔ |
| BaiduSpider | / | ✔ |
| YandexBot | / | ✔ |
Meta Tags
| Title | Ｋｅｎｔａｎ Ｂｌｏｇ |
| Description | WordPress関連・アフィリエイト・AFFINGER6の設定・カスタマイズ、無料ソフトの紹介、ブログを中心に、情報を発信していくサイトです。ブログ初心者ならではの視点で記事を書いています。 |
| Keywords | N/A |
Server Information
| WebSite | |
| Host IP | 118.27.122.185 |
| Location | Tokyo, Tokyo, Japan |
Related Websites
| Site | Rank |
More to Explore
Kentanblog.org Valuation
|
US$556,092
Last updated: Feb 13, 2023
Kentanblog.org has global traffic rank of 156,489. Kentanblog.org has an estimated worth of US$ 556,092, based on its estimated Ads revenue. Kentanblog.org receives approximately 20,313 unique visitors each day. Its web server is located in Tokyo, Tokyo, Japan, with IP address 118.27.122.185. According to SiteAdvisor, kentanblog.org is unknown to visit. |
Traffic & Worth Estimates
| Purchase/Sale Value | US$556,092 |
| Daily Ads Revenue | US$304 |
| Monthly Ads Revenue | US$9,141 |
| Yearly Ads Revenue | US$111,218 |
| Daily Unique Visitors | 20,313 |
| Note: All traffic and earnings values are estimates. | |
Traffic Ranks
| Global Rank | 156,489 |
| Delta (90 Days) | 0 |
| Most Popular In Country | N/A |
| Country Rank | N/A |
DNS Records
| Host | Type | TTL | Data |
| kentanblog.org | A | 3600 | IP: 118.27.122.185 |
| kentanblog.org | MX | 3600 | Priority: 10 Target: mail72.conoha.ne.jp. |
| kentanblog.org | NS | 3600 | Target: ns-a2.conoha.io. |
| kentanblog.org | NS | 3600 | Target: ns-a3.conoha.io. |
| kentanblog.org | NS | 3600 | Target: ns-a1.conoha.io. |
| kentanblog.org | TXT | 3600 | TXT: v=spf1 include:_spf.conoha.ne.jp ~all |
| kentanblog.org | SOA | 3600 | MNAME: ns-a1.conoha.io. RNAME: postmaster.kentanblog.org. Serial: 1672637859 Refresh: 3600 Retry: 600 Expire: 86400 Minimum TTL: 3600 |
HTTP Headers
HTTP/1.1 301 Moved Permanently Server: nginx Date: Mon, 13 Feb 2023 00:10:25 GMT Content-Type: text/html Content-Length: 162 Connection: keep-alive Location: https://kentanblog.org/ HTTP/2 200 server: nginx date: Mon, 13 Feb 2023 00:10:26 GMT content-type: text/html; charset=UTF-8 link: <https://kentanblog.org/wp-json/>; rel="https://api.w.org/", <https://kentanblog.org/wp-json/wp/v2/pages/1603>; rel="alternate"; type="application/json", <https://kentanblog.org/>; rel=shortlink x-xss-protection: 1; mode=block x-content-type-options: nosniff x-nginx-cache: EXPIRED |
Kentanblog.org Whois Information
Domain Name: kentanblog.org Registry Domain ID: f45455cec4d94fbdb6b05ebd5e1f3195-LROR Registrar WHOIS Server: http://whois.discount-domain.com Registrar URL: http://www.onamae.com Updated Date: 2022-07-01T15:53:21Z Creation Date: 2021-07-03T05:28:11Z Registry Expiry Date: 2023-07-03T05:28:11Z Registrar: GMO Internet, Inc. d/b/a Onamae.com Registrar IANA ID: 49 Registrar Abuse Contact Email: abuse@gmo.jp Registrar Abuse Contact Phone: +81.337709199 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registry Registrant ID: REDACTED FOR PRIVACY Registrant Name: REDACTED FOR PRIVACY Registrant Organization: Whois Privacy Protection Service by ConoHa Registrant Street: REDACTED FOR PRIVACY Registrant City: REDACTED FOR PRIVACY Registrant State/Province: Tokyo Registrant Postal Code: REDACTED FOR PRIVACY Registrant Country: JP Registrant Phone: REDACTED FOR PRIVACY Registrant Phone Ext: REDACTED FOR PRIVACY Registrant Fax: REDACTED FOR PRIVACY Registrant Fax Ext: REDACTED FOR PRIVACY Registry Admin ID: REDACTED FOR PRIVACY Admin Name: REDACTED FOR PRIVACY Admin Organization: REDACTED FOR PRIVACY Admin Street: REDACTED FOR PRIVACY Admin City: REDACTED FOR PRIVACY Admin State/Province: REDACTED FOR PRIVACY Admin Postal Code: REDACTED FOR PRIVACY Admin Country: REDACTED FOR PRIVACY Admin Phone: REDACTED FOR PRIVACY Admin Phone Ext: REDACTED FOR PRIVACY Admin Fax: REDACTED FOR PRIVACY Admin Fax Ext: REDACTED FOR PRIVACY Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Registry Tech ID: REDACTED FOR PRIVACY Tech Name: REDACTED FOR PRIVACY Tech Organization: REDACTED FOR PRIVACY Tech Street: REDACTED FOR PRIVACY Tech City: REDACTED FOR PRIVACY Tech State/Province: REDACTED FOR PRIVACY Tech Postal Code: REDACTED FOR PRIVACY Tech Country: REDACTED FOR PRIVACY Tech Phone: REDACTED FOR PRIVACY Tech Phone Ext: REDACTED FOR PRIVACY Tech Fax: REDACTED FOR PRIVACY Tech Fax Ext: REDACTED FOR PRIVACY Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Name Server: ns-a1.conoha.io Name Server: ns-a2.conoha.io Name Server: ns-a3.conoha.io DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ |