Statistics

Heatherprettymanblog.com

Heatherprettymanblog.com is hosted in United States / Provo . Heatherprettymanblog.com uses HTTPS protocol. Number of used technologies: 10. First technologies: CSS, Feedburner, Font Awesome, Number of used javascripts: 6. First javascripts: Jquery.js, Jquery-migrate.min.js, Underscore.min.js, Number of used analytics tools: 1. First analytics tools: Google Analytics, Number of used plugins, modules: 3. Its server type is: nginx/1.10.1. Its CMS is: Wordpress.

Technologies in use by Heatherprettymanblog.com

Technology

Number of occurences: 10

CSS
Feedburner
Font Awesome
Google Font API
Html
Html5
Javascript
jQuery
Php
Pingback

Javascripts

Number of occurences: 6

jquery.js
jquery-migrate.min.js
underscore.min.js
smartfaq.min.js
1463615494_script.js
wp-embed.min.js

Content Management System

Number of occurences: 1

Wordpress

Analytics

Number of occurences: 1

Google Analytics

Server Type

nginx/1.10.1

CDN

Number of occurences: 1

BootstrapCDN

Used plugins, modules

Number of plugins and modules: 3

smart faq
wordpress simple paypal shopping cart
easy columns

Google Analytics ID

UA-11542588-5

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	Not 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) - Heatherprettymanblog.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 - Heatherprettymanblog.com

Number of occurences: 5

Name:
Content: 545568325
Name: pinterest
Content: nohover
Name: description
Content: Heather Prettyman is a premier Sacramento wedding and portrait photographer.
Name: keywords
Content: sacramento wedding photography, sacramento portrait photographer, heather prettyman, yelp, arden hills wedding photo, saratoga wedding photography, villa montalvo wedding photo
Name: generator
Content: WordPress 4.5.3

Server / Hosting

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

Rname

ns2.bluehost.com
ns1.bluehost.com
heatherprettymanblog.com

Target

root.box382.bluehost.com

HTTP Header Response

HTTP/1.1 200 OK Server: nginx/1.10.1 Date: Sat, 20 Aug 2016 17:22:29 GMT Content-Type: text/html; charset=utf8 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Set-Cookie: PHPSESSID=8v7k119797el9sqf1f5bof6p90; path=/ Vary: Accept-Encoding X-Cache: MISS from s_wx1011 X-Cache-Lookup: MISS from s_wx1011:80 Transfer-Encoding: chunked Via: 1.1 s_wx1011 (squid/3.5.20) Connection: keep-alive