Olympic2020-tokyo.com

Olympic2020-tokyo.com is hosted in Japan / Osaka . Olympic2020-tokyo.com uses HTTPS protocol. Number of used technologies: 8. First technologies: CSS, Font Awesome, Html, Number of used javascripts: 5. First javascripts: Jquery.js, Jquery-migrate.min.js, Javascript.js, Number of used analytics tools: 1. First analytics tools: Google Analytics, Its server type is: Apache. Its CMS is: Wordpress.

Technologies in use by Olympic2020-tokyo.com

Technology

Number of occurences: 8

CSS
Font Awesome
Html
Html5
Javascript
jQuery
Php
Pingback

Javascripts

Number of occurences: 5

jquery.js
jquery-migrate.min.js
javascript.js
wp-embed.min.js

Content Management System

Number of occurences: 1

Wordpress

Analytics

Number of occurences: 1

Google Analytics

Server Type

Apache

Social

Number of occurences: 1

Facebook Box

Conversion rate optimization
Clickable call number	Not founded!
Conversion form (contact form, subcriber)	Not founded!
Clickable email	Not founded!
CTA (call to action) button	Not founded!
List	Founded!
Image	Not founded!
Enhancement	Not founded!
Responsive website	Founded!
Facebook sharing	Not founded!
Google+ sharing	Not founded!
Twitter sharing	Not founded!
Linkedin sharing	Not founded!
Blog on the webiste	Not founded!

HTTPS (SSL) - Olympic2020-tokyo.com

SSL certificate

name: /OU=Domain Control Validated/OU=CoreSSL DV Wildcard/CN=*.xserver.jp
subject:
- OU:
  - 0: Domain Control Validated
  - 1: CoreSSL DV Wildcard
- CN: *.xserver.jp
hash: 80b9d75f
issuer:
- C: JP
- ST: OSAKA
- L: OSAKA
- O: SecureCore
- CN: SecureCore RSA DV CA
version: 2
serialNumber: 136166883431988471781193497564807190705
validFrom: 151201000000Z
validTo: 190117235959Z
validFrom_time_t: 1448928000
validTo_time_t: 1547769599
extensions:
- authorityKeyIdentifier: keyid:87:B2:E6:D0:DF:DF:0C:E3:2D:97:D2:24:08:A9:50:8F:27:0B:90:69
- subjectKeyIdentifier: 91:7E:F0:6F:A2:62:FA:E9:D0:85:52:EE:61:7D:07:D3:83:85:51:89
- keyUsage: Digital Signature, Key Encipherment
- basicConstraints: CA:FALSE
- extendedKeyUsage: TLS Web Server Authentication, TLS Web Client Authentication
- certificatePolicies: Policy: 1.3.6.1.4.1.6449.1.2.2.50 CPS: https://cps.securecore-ca.com Policy: 2.23.140.1.2.1
- crlDistributionPoints: Full Name: URI:http://crl.securecore-ca.com/SecureCoreRSADVCA.crl
- authorityInfoAccess: CA Issuers - URI:http://crt.securecore-ca.com/SecureCoreRSADVCA.crt OCSP - URI:http://ocsp.securecore-ca.com
- subjectAltName: DNS:*.xserver.jp, DNS:xserver.jp

Meta - Olympic2020-tokyo.com

Number of occurences: 11

Name:
Content: no
Name: viewport
Content: width=1280, maximum-scale=1, user-scalable=yes
Name: twitter:card
Content: summary
Name: twitter:description
Content: ã‚ªãƒªãƒ³ãƒ”ãƒƒã‚¯ã®æ´å²ã‚„å¹´è¡¨ã€æ´ä»£ã®ä¸–ç•Œè¨˜éŒ²ã®ä¸€è¦§
Name: twitter:title
Content: æ±äº¬äº”è¼ª å¹´è¡¨ã¨æ´ä»£ä¸–ç•Œè¨˜éŒ²ã®ä¸€è¦§
Name: twitter:url
Content: http://olympic2020-tokyo.com
Name: twitter:image
Content: http://olympic2020-tokyo.com/wp-content/themes/simplicity-child/screenshot.png
Name: twitter:domain
Content: olympic2020-tokyo.com
Name: description
Content: ã™ãåˆ†ã‹ã‚‹2020å¹´æ±äº¬äº”è¼ªã®ã¾ã¨ã‚æƒ…å ±ã€‚æ´å²å¹´è¡¨ã‚„ä¸–ç•Œè¨˜éŒ²ä¸€è¦§
Name: keywords
Content: æ±äº¬äº”è¼ª,æ´å²,å¹´è¡¨,æ´ä»£è¨˜éŒ²
Name: generator
Content: WordPress 4.5.3

Server / Hosting

IP: 157.112.189.9
Latitude: 34.69
Longitude: 135.52
Country: Japan
City: Osaka

Rname

ns4.xserver.jp
ns1.xserver.jp
ns5.xserver.jp
ns2.xserver.jp
ns3.xserver.jp
olympic2020-tokyo.com

Target

root.sv0.xserver.jp

HTTP Header Response

HTTP/1.1 301 Moved Permanently Date: Sat, 23 Jul 2016 18:05:47 GMT Server: Apache Location: http://olympic2020-tokyo.com/ Cache-Control: max-age=1 Expires: Sat, 23 Jul 2016 18:05:48 GMT Vary: Accept-Encoding,User-Agent Content-Length: 0 Content-Type: text/html; charset=UTF-8 X-Cache: MISS from s_hp65 X-Cache-Lookup: MISS from s_hp65:80 Via: 1.1 s_hp65 (squid/3.5.19) Connection: keep-alive HTTP/1.1 200 OK Date: Sat, 23 Jul 2016 18:05:49 GMT Server: Apache Link: ; rel="https://api.w.org/" Cache-Control: max-age=1 Expires: Sat, 23 Jul 2016 18:05:50 GMT Vary: Accept-Encoding,User-Agent Content-Type: text/html; charset=UTF-8 X-Cache: MISS from s_hp65 X-Cache-Lookup: MISS from s_hp65:80 Transfer-Encoding: chunked Via: 1.1 s_hp65 (squid/3.5.19) Connection: keep-alive