Howsthatcupofjoe.com

Howsthatcupofjoe.com is hosted in Japan / Tokyo . Howsthatcupofjoe.com uses HTTPS protocol. Number of used technologies: 6. First technologies: Google Font API, Html, Html5, Number of used javascripts: 8. First javascripts: Jquery.js, Jquery-migrate.min.js, Navigation.js, Number of used analytics tools: 0. Its server type is: nginx/1.7.5. Its CMS is: Wordpress.

Technologies in use by Howsthatcupofjoe.com

Technology

Number of occurences: 6

Google Font API
Html
Html5
jQuery
Php
Pingback

Javascripts

Number of occurences: 8

jquery.js
jquery-migrate.min.js
navigation.js
featured-content.js
header.js
search.js
posts.js
skip-link-focus-fix.js

Content Management System

Number of occurences: 1

Wordpress

Server Type

nginx/1.7.5

Powered by

PHP/5.4.45

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

SSL certificate

name: /OU=Domain Control Validated/OU=EssentialSSL Wildcard/CN=*.mbsrv.net
subject:
- OU:
  - 0: Domain Control Validated
  - 1: EssentialSSL Wildcard
- CN: *.mbsrv.net
hash: 099de621
issuer:
- C: GB
- ST: Greater Manchester
- L: Salford
- O: COMODO CA Limited
- CN: COMODO RSA Domain Validation Secure Server CA
version: 2
serialNumber: 44946050782386232546974542710114304542
validFrom: 160515000000Z
validTo: 170714235959Z
validFrom_time_t: 1463270400
validTo_time_t: 1500076799
extensions:
- authorityKeyIdentifier: keyid:90:AF:6A:3A:94:5A:0B:D8:90:EA:12:56:73:DF:43:B4:3A:28:DA:E7
- subjectKeyIdentifier: 93:A5:C8:4B:78:13:95:E5:E3:61:CC:4B:0C:4A:36:4A:38:9E:F2:E4
- 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.7 CPS: https://secure.comodo.com/CPS Policy: 2.23.140.1.2.1
- crlDistributionPoints: Full Name: URI:http://crl.comodoca.com/COMODORSADomainValidationSecureServerCA.crl
- authorityInfoAccess: CA Issuers - URI:http://crt.comodoca.com/COMODORSADomainValidationSecureServerCA.crt OCSP - URI:http://ocsp.comodoca.com
- subjectAltName: DNS:*.mbsrv.net, DNS:mbsrv.net

Meta - Howsthatcupofjoe.com

Number of occurences: 3

Name:
Content:
Name: viewport
Content: width=device-width, initial-scale=1
Name: generator
Content: WordPress 3.9.1

Server / Hosting

IP: 36.3.107.181
Latitude: 35.69
Longitude: 139.75
Country: Japan
City: Tokyo

Rname

ns26.mbsrv.net
ns25.mbsrv.net
howsthatcupofjoe.com

Target

root.s118.mbsrv.net

HTTP Header Response

HTTP/1.1 200 OK Server: nginx/1.7.5 Date: Thu, 18 Aug 2016 19:36:21 GMT Content-Type: text/html; charset=UTF-8 X-Powered-By: PHP/5.4.45 X-Frame-Options: SAMEORIGIN X-Cache: MISS from s_ub9 X-Cache-Lookup: MISS from s_ub9:80 Transfer-Encoding: chunked Via: 1.1 s_ub9 (squid/3.5.20) Connection: keep-alive