Candacestravelblog.com

Candacestravelblog.com is hosted in United States / Provo . Candacestravelblog.com uses HTTPS protocol. Number of used technologies: 9. First technologies: CSS, Feedburner, Gravatar, Number of used javascripts: 8. First javascripts: Jquery.js, Jquery-migrate.min.js, Commentluv.js, Number of used analytics tools: 1. First analytics tools: WordPress Stats, Number of used plugins, modules: 4. Its server type is: nginx/1.8.1. Its CMS is: Wordpress.

Technologies in use by Candacestravelblog.com

Technology

Number of occurences: 9

CSS
Feedburner
Gravatar
Html
Html5
Javascript
jQuery
Php
Pingback

Javascripts

Number of occurences: 8

jquery.js
jquery-migrate.min.js
commentluv.js
bl.js
devicepx-jetpack.js
gprofiles.js
wpgroho.js
e-201617.js

Content Management System

Number of occurences: 1

Wordpress

Analytics

Number of occurences: 1

WordPress Stats

Server Type

nginx/1.8.1

Used plugins, modules

Number of plugins and modules: 4

commentluv
jetpack
wpgroho.js?ver=4.3.3 http:
widgets

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	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) - Candacestravelblog.com

SSL certificate

name: /OU=Domain Control Validated/OU=Hosted by BlueHost.Com, INC/OU=PositiveSSL Wildcard/CN=*.bluehost.com
subject:
- OU:
  - 0: Domain Control Validated
  - 1: Hosted by BlueHost.Com, INC
  - 2: PositiveSSL Wildcard
- CN: *.bluehost.com
hash: b00471fb
issuer:
- C: GB
- ST: Greater Manchester
- L: Salford
- O: COMODO CA Limited
- CN: COMODO RSA Domain Validation Secure Server CA
version: 2
serialNumber: 275919344465328667035358918366332841359
validFrom: 150313000000Z
validTo: 180312235959Z
validFrom_time_t: 1426204800
validTo_time_t: 1520899199
extensions:
- authorityKeyIdentifier: keyid:90:AF:6A:3A:94:5A:0B:D8:90:EA:12:56:73:DF:43:B4:3A:28:DA:E7
- subjectKeyIdentifier: 29:B6:2F:A5:A8:41:C7:45:BE:86:84:10:E9:26:A7:94:67:64:BC:73
- 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:*.bluehost.com, DNS:bluehost.com

Meta - Candacestravelblog.com

Number of occurences: 7

Name:
Content: http://www.candacestravelblog.com/?s={s}
Name: viewport
Content: width=device-width, initial-scale=1
Name: description
Content: Traveling the world, one corner at a time...
Name: alexaVerifyID
Content: Pvx4IOoLCoDkv8i8-in1qdnsIoI
Name: msvalidate.01
Content: 618CAEFDAE013328A417C602FC87F580
Name: google-site-verification
Content: c31BZy9Cprqfgdm5F7nHMFVC3DY4N3x2y9npwUBMIZQ
Name: generator
Content: WordPress 4.3.3

Server / Hosting

IP: 66.147.244.193
Latitude: 40.22
Longitude: -111.61
Country: United States
City: Provo

Rname

ns2.bluehost.com
ns1.bluehost.com
mail.candacestravelblog.com

Target

root.box693.bluehost.com

HTTP Header Response

HTTP/1.1 301 Moved Permanently Server: nginx/1.8.1 Date: Mon, 25 Apr 2016 23:23:30 GMT Content-Type: text/html; charset=UTF-8 Connection: keep-alive X-Pingback: http://www.candacestravelblog.com/xmlrpc.php Location: http://www.candacestravelblog.com/ Vary: Accept-Encoding X-Cacheable: YES X-Served-From-Cache: Yes HTTP/1.1 200 OK Server: nginx/1.8.1 Date: Mon, 25 Apr 2016 23:23:30 GMT Content-Type: text/html; charset=UTF-8 Connection: keep-alive X-Pingback: http://www.candacestravelblog.com/xmlrpc.php Link: ; rel=shortlink Vary: Accept-Encoding X-Cacheable: YES X-Served-From-Cache: Yes