Journeytomyironman.com

Domain is redirected to: Journeytoironman.com

Journeytomyironman.com is hosted in United States / San Francisco . Journeytomyironman.com uses HTTPS protocol. Number of used technologies: 10. First technologies: CSS, Google Font API, Gravatar, Number of used javascripts: 7. First javascripts: Gprofiles.js, Wpgroho.js, Jquery.autoresize.js, Number of used analytics tools: 1. First analytics tools: ComScore, Its server type is: nginx. Its CMS is: Wordpress.

Technologies in use by Journeytomyironman.com

Technology

Number of occurences: 10

CSS
Google Font API
Gravatar
Html
Html5
Javascript
Php
Pingback
Shortcodes
SVG

Javascripts

Number of occurences: 7

gprofiles.js
wpgroho.js
jquery.autoresize.js
script.js
widgets.js
725X1342.skimlinks.js
w.js

Content Management System

Number of occurences: 1

Wordpress

Analytics

Number of occurences: 1

comScore

Advertise

Number of occurences: 1

Skimlinks

Server Type

nginx

Social

Number of occurences: 2

Facebook Box
Twitter Button

Conversion rate optimization
Clickable call number	Not founded!
Conversion form (contact form, subcriber)	Founded!
Clickable email	Not founded!
CTA (call to action) button	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) - Journeytomyironman.com

SSL certificate

name: /CN=tls.automattic.com
subject:
- CN: tls.automattic.com
hash: 6338c477
issuer:
- C: US
- O: Let's Encrypt
- CN: Let's Encrypt Authority X3
version: 2
serialNumber: 344122224929443351799535662945246401430075
validFrom: 160815134000Z
validTo: 161113134000Z
validFrom_time_t: 1471268400
validTo_time_t: 1479044400
extensions:
- keyUsage: Digital Signature, Key Encipherment
- extendedKeyUsage: TLS Web Server Authentication, TLS Web Client Authentication
- basicConstraints: CA:FALSE
- subjectKeyIdentifier: FB:31:F7:B6:72:1E:BB:16:38:37:EB:B0:ED:46:DE:75:89:CA:69:F6
- authorityKeyIdentifier: keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
- authorityInfoAccess: OCSP - URI:http://ocsp.int-x3.letsencrypt.org/ CA Issuers - URI:http://cert.int-x3.letsencrypt.org/
- subjectAltName: DNS:journeytolivertransplant.com, DNS:journeytolosemyself.com, DNS:journeytoloving.me, DNS:journeytomelove.com, DNS:journeytomyironman.com, DNS:journeytonapa.com, DNS:journeytonewyork.dk, DNS:journeytopenuel.com, DNS:journeytophilly.org, DNS:journeytoplanetx.com, DNS:journeytopointe.com, DNS:journeytorecovery.co, DNS:journeytorose.com, DNS:journeytosimple.com, DNS:journeytothebirkie.com, DNS:journeytotheboardroom.com, DNS:journeytothecenterofmystomach.com, DNS:journeytothehills.com, DNS:journeytothenarrative.com, DNS:journeytothepresent.com, DNS:journeytothespirit.com, DNS:journeytothetruthblog.com, DNS:journeytothirty.me, DNS:journeytovandiemensland.com, DNS:journeytowardjoy.com, DNS:tls.automattic.com, DNS:www.journeytolex.com, DNS:www.journeytolivertransplant.com, DNS:www.journeytolosemyself.com, DNS:www.journeytoloving.me, DNS:www.journeytomelove.com, DNS:www.journeytomyironman.com, DNS:www.journeytonapa.com, DNS:www.journeytonewyork.dk, DNS:www.journeytopenuel.com, DNS:www.journeytophilly.org, DNS:www.journeytoplanetx.com, DNS:www.journeytopointe.com, DNS:www.journeytorecovery.co, DNS:www.journeytorose.com, DNS:www.journeytosimple.com, DNS:www.journeytothebirkie.com, DNS:www.journeytotheboardroom.com, DNS:www.journeytothecenterofmystomach.com, DNS:www.journeytothehills.com, DNS:www.journeytothenarrative.com, DNS:www.journeytothepresent.com, DNS:www.journeytothespirit.com, DNS:www.journeytothetruthblog.com, DNS:www.journeytothirty.me, DNS:www.journeytovandiemensland.com
- certificatePolicies: Policy: 2.23.140.1.2.1 Policy: 1.3.6.1.4.1.44947.1.1.1 CPS: http://cps.letsencrypt.org User Notice: Explicit Text: This Certificate may only be relied upon by Relying Parties and only in accordance with the Certificate Policy found at https://letsencrypt.org/repository/

Meta - Journeytomyironman.com

Number of occurences: 11

Name:
Content: en_US
Name: viewport
Content: width=device-width, initial-scale=1
Name: generator
Content: WordPress.com
Name: twitter:site
Content: @wordpressdotcom
Name: theme-color
Content: #ffffff
Name: application-name
Content: Journey to my Ironman
Name: msapplication-window
Content: width=device-width;height=device-height
Name: msapplication-tooltip
Content: Why the Hell not?
Name: msapplication-task
Content: name=WordPress.com Forums;action-uri=http://forums.wordpress.com/;icon-uri=https://s2.wp.com/i/favicon.ico
Name: title
Content: Journey to my Ironman on WordPress.com
Name: description
Content: Why the Hell not?

Server / Hosting

IP: 192.0.78.24
Latitude: 37.75
Longitude: -122.42
Country: United States
City: San Francisco

Rname

ns3.wordpress.com
ns2.wordpress.com
ns1.wordpress.com
smtp-fwd.wordpress.com

Target

hostmaster.wordpress.com

HTTP Header Response

HTTP/1.1 301 Moved Permanently Server: nginx Date: Fri, 07 Oct 2016 06:13:38 GMT Content-Type: text/html Content-Length: 178 Location: https://www.journeytomyironman.com/ X-ac: 3.dfw _dfw X-Cache: MISS from s_sh11 Via: 1.1 s_sh11 (squid/3.5.20) Connection: keep-alive HTTP/1.1 200 Connection established HTTP/1.1 301 Moved Permanently Server: nginx Date: Fri, 07 Oct 2016 06:13:39 GMT Content-Type: text/html Content-Length: 178 Connection: keep-alive Strict-Transport-Security: max-age=86400 Location: https://journeytomyironman.com/ X-ac: 3.dfw _dfw HTTP/1.1 200 Connection established HTTP/1.1 301 Moved Permanently Server: nginx Date: Fri, 07 Oct 2016 06:13:39 GMT Content-Type: text/html; charset=utf-8 Transfer-Encoding: chunked Connection: keep-alive Strict-Transport-Security: max-age=86400 Vary: Cookie Location: http://journeytoironman.com/ X-ac: 3.dfw _dfw HTTP/1.1 301 Moved Permanently Server: nginx Date: Fri, 07 Oct 2016 06:13:40 GMT Content-Type: text/html Content-Length: 178 Location: https://journeytoironman.com/ X-ac: 3.dfw _dfw X-Cache: MISS from s_sh11 Via: 1.1 s_sh11 (squid/3.5.20) Connection: keep-alive HTTP/1.1 200 Connection established HTTP/1.1 200 OK Server: nginx Date: Fri, 07 Oct 2016 06:13:41 GMT Content-Type: text/html; charset=UTF-8 Transfer-Encoding: chunked Connection: keep-alive Strict-Transport-Security: max-age=86400 Vary: Accept-Encoding Vary: Cookie X-hacker: If you're reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header. Link: ; rel=shortlink X-ac: 3.dfw _dfw