Runningforkicksandgiggles.com

Runningforkicksandgiggles.com is hosted in United States / Provo . Runningforkicksandgiggles.com uses HTTPS protocol. Number of used technologies: 11. First technologies: CSS, Feedburner, Google Font API, Number of used javascripts: 22. First javascripts: Jquery.js, Jquery-migrate.min.js, Devicepx-jetpack.js, Number of used analytics tools: 2. First analytics tools: Google Analytics, WordPress Stats, Number of used plugins, modules: 6. Its server type is: nginx/1.10.1. Its CMS is: Wordpress.

Technologies in use by Runningforkicksandgiggles.com

Technology

Number of occurences: 11

CSS
Feedburner
Google Font API
Gravatar
Html
Iframe
Javascript
jQuery
jQuery Cycle
Php
Pingback

Javascripts

Number of occurences: 22

jquery.js
jquery-migrate.min.js
devicepx-jetpack.js
gprofiles.js
wpgroho.js
jquery.imagesloaded.js
jquery.masonry.min.js
jquery.cycle.min.js
jquery.fitvids.js
navigation.js
footer-scripts-light.js
drop-downs.min.js
facebook-embed.js
twitter-timeline.js
wp-embed.min.js
postmessage.js
jquery.jetpack-resize.js
jquery.inview.js
queuehandler.js
AlpinePhotoTiles_script.js
sharing.js
e-201629.js

Content Management System

Number of occurences: 1

Wordpress

Analytics

Number of occurences: 2

Google Analytics
WordPress Stats

Server Type

nginx/1.10.1

Social

Number of occurences: 1

Facebook Box

Used plugins, modules

Number of plugins and modules: 6

jetpack
alpine photo tile for instagram
facebook button plugin
wpgroho.js?ver=4.5.3 http:
likes
sharedaddy

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

Number of occurences: 4

Name:
Content: en_US
Name: viewport
Content: width=device-width,initial-scale=1
Name: generator
Content: WordPress 4.5.3
Name: template
Content: Oxygen 0.6.0

Server / Hosting

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

Rname

ns2.bluehost.com
ns1.bluehost.com
mail.runningforkicksandgiggles.com

Target

dnsadmin.box756.bluehost.com

HTTP Header Response

HTTP/1.1 200 OK Server: nginx/1.10.1 Date: Fri, 22 Jul 2016 16:17:16 GMT Content-Type: text/html; charset=UTF-8 Link: ; rel="https://api.w.org/", ; rel=shortlink Vary: Accept-Encoding X-Cache: MISS from s_sr109 X-Cache-Lookup: MISS from s_sr109:80 Transfer-Encoding: chunked Via: 1.1 s_sr109 (squid/3.5.14) Connection: keep-alive