Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
Title | |
Description | N/A |
Keywords | N/A |
WebSite | typepad.jp |
Host IP | 104.18.137.190 |
Location | United States |
Site | Rank |
US$980,614
Last updated:
typepad.jp has Semrush global rank of 10,793,555. typepad.jp has an estimated worth of US$ 980,614, based on its estimated Ads revenue. typepad.jp receives approximately 113,148 unique visitors each day. Its web server is located in United States, with IP address 104.18.137.190. According to SiteAdvisor, typepad.jp is safe to visit. |
Purchase/Sale Value | US$980,614 |
Daily Ads Revenue | US$906 |
Monthly Ads Revenue | US$27,156 |
Yearly Ads Revenue | US$325,866 |
Daily Unique Visitors | 7,544 |
Note: All traffic and earnings values are estimates. |
Host | Type | TTL | Data |
typepad.jp. | A | 299 | IP: 104.18.137.190 |
typepad.jp. | A | 299 | IP: 104.18.139.190 |
typepad.jp. | A | 299 | IP: 104.18.136.190 |
typepad.jp. | A | 299 | IP: 104.18.138.190 |
typepad.jp. | A | 299 | IP: 104.18.140.190 |
typepad.jp. | NS | 86400 | NS Record: noah.ns.cloudflare.com. |
typepad.jp. | NS | 86400 | NS Record: roxy.ns.cloudflare.com. |
typepad.jp. | MX | 300 | MX Record: 10 mail.typepad.com. |
typepad.jp. | TXT | 300 | TXT Record: google-site-verification=AGVH5sQOZzuhEaTQJ-Nfg76RjUBN1J2X7r2F-N1wBS8 |
HTTP/1.1 301 Moved Permanently Date: Thu, 21 Oct 2021 00:09:04 GMT Connection: keep-alive Cache-Control: max-age=3600 Expires: Thu, 21 Oct 2021 01:09:04 GMT Location: https://typepad.jp/ Server: cloudflare CF-RAY: 6a16414b8b302c84-ORD HTTP/2 404 date: Thu, 21 Oct 2021 00:09:04 GMT content-type: text/html; charset=iso-8859-1 x-cacheable: NO:Not Cacheable accept-ranges: bytes x-varnish: 3740144296 age: 0 via: 1.1 varnish cf-cache-status: DYNAMIC expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct" server: cloudflare cf-ray: 6a16414bcc35495d-STL |
Cannot process your search request. Service currently unavailable due to incoming of a large amount of requests. Try again later. |