Whatwouldjesuslike.com

Whatwouldjesuslike.com is hosted in United States / San Francisco . Whatwouldjesuslike.com uses HTTPS protocol. Number of used technologies: 10. First technologies: CSS, Google Font API, Gravatar, Number of used javascripts: 4. First javascripts: Gprofiles.js, Wpgroho.js, 725X1342.skimlinks.js, Number of used analytics tools: 2. First analytics tools: ComScore, Facebook Retargeting, Its server type is: nginx. Its CMS is: Wordpress.

Technologies in use by Whatwouldjesuslike.com

Technology

Number of occurences: 10

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

Javascripts

Number of occurences: 4

gprofiles.js
wpgroho.js
725X1342.skimlinks.js
w.js

Content Management System

Number of occurences: 1

Wordpress

Analytics

Number of occurences: 2

comScore
Facebook Retargeting

Advertise

Number of occurences: 1

Skimlinks

Server Type

nginx

Social

Number of occurences: 1

Facebook Box

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) - Whatwouldjesuslike.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: 281582458367581725224137748637629353974901
validFrom: 160725121600Z
validTo: 161023121600Z
validFrom_time_t: 1469448960
validTo_time_t: 1477224960
extensions:
- keyUsage: Digital Signature, Key Encipherment
- extendedKeyUsage: TLS Web Server Authentication, TLS Web Client Authentication
- basicConstraints: CA:FALSE
- subjectKeyIdentifier: BA:F1:9A:AA:52:EF:13:F2:CC:75:61:93:EA:F4:13:56:DD:B3:04:76
- 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:blog.whatusersdo.com, DNS:tls.automattic.com, DNS:whatif.coop, DNS:whatinthejoel.com, DNS:whatisbrewing.net, DNS:whatiskirbydoing.com, DNS:whatkeddyeats.com, DNS:whatrivawore.com, DNS:whats-yourstory-blog.com, DNS:whatsarahsaidblog.com, DNS:whatsbubbling.uk, DNS:whatsfitness.de, DNS:whatsheseamstolove.com, DNS:whatshouldidotodaysite.com, DNS:whatsnextafter40.com, DNS:whatsthemostoriginalthingicanhaveasmydomainname.com, DNS:whatsthetrends.com, DNS:whatsupanddown.org, DNS:whatsupqueen.com, DNS:whatsyour2cent.com, DNS:whattheycannotsee.com, DNS:whatwouldjesuslike.com, DNS:whatyousaykay.com, DNS:whatyoushouldknowaboutcredit.com, DNS:whbft.org, DNS:wheelangel.com, DNS:wheelercopywriting.com, DNS:www.whatif.coop, DNS:www.whatinthejoel.com, DNS:www.whatisbrewing.net, DNS:www.whatiskirbydoing.com, DNS:www.whatkeddyeats.com, DNS:www.whatrivawore.com, DNS:www.whats-yourstory-blog.com, DNS:www.whatsarahsaidblog.com, DNS:www.whatsbubbling.uk, DNS:www.whatsfitness.de, DNS:www.whatsheseamstolove.com, DNS:www.whatshouldidotodaysite.com, DNS:www.whatsnextafter40.com, DNS:www.whatsthemostoriginalthingicanhaveasmydomainname.com, DNS:www.whatsthetrends.com, DNS:www.whatsupanddown.org, DNS:www.whatsupqueen.com, DNS:www.whatsyour2cent.com, DNS:www.whattheycannotsee.com, DNS:www.whatwouldjesuslike.com, DNS:www.whatyousaykay.com, DNS:www.whatyoushouldknowaboutcredit.com, DNS:www.whbft.org, DNS:www.wheelangel.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 - Whatwouldjesuslike.com

Number of occurences: 14

Name:
Content: https://www.facebook.com/WordPresscom
Name: viewport
Content: width=device-width, initial-scale=1
Name: google-site-verification
Content: RPwbcuOJCzC_4YvtexyAkCIdAtC7ucRudyyO4fcNOBY
Name: generator
Content: WordPress.com
Name: twitter:site
Content: @wwjesuslike
Name: twitter:image
Content: https://www.facebook.com/tr?w=1400
Name: twitter:card
Content: photo
Name: twitter:creator
Content: @wwjesuslike
Name: application-name
Content: What Would Jesus Like
Name: msapplication-window
Content: width=device-width;height=device-height
Name: msapplication-tooltip
Content: Faith ä¿¡ Hope æœ› Love æ„›
Name: msapplication-task
Content: name=WordPress.com è«–å£‡;action-uri=http://forums.wordpress.com/;icon-uri=https://s2.wp.com/i/favicon.ico
Name: title
Content: What Would Jesus Like | What Would Jesus Like åœ¨ WordPress.com
Name: description
Content: Social Evangelization Project "Faith, Hope & Love" â€¦

Server / Hosting

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

Rname

ns1.wordpress.com
ns2.wordpress.com
ns3.wordpress.com

Target

hostmaster.wordpress.com

HTTP Header Response

HTTP/1.1 301 Moved Permanently Server: nginx Date: Sun, 11 Sep 2016 03:41:30 GMT Content-Type: text/html Content-Length: 178 Location: https://www.whatwouldjesuslike.com/ X-ac: 3.fra _dca X-Cache: MISS from s_wx1123 Via: 1.1 s_wx1123 (squid/3.5.20) Connection: keep-alive HTTP/1.1 200 Connection established HTTP/1.1 301 Moved Permanently Server: nginx Date: Sun, 11 Sep 2016 03:41:30 GMT Content-Type: text/html Content-Length: 178 Connection: keep-alive Strict-Transport-Security: max-age=86400 Location: https://whatwouldjesuslike.com/ X-ac: 3.fra _dca HTTP/1.1 200 Connection established HTTP/1.1 200 OK Server: nginx Date: Sun, 11 Sep 2016 03:41:31 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.fra _dca