Cutchoguenewsuffolkhistory.org

Cutchoguenewsuffolkhistory.org is hosted in United States / Provo . Cutchoguenewsuffolkhistory.org uses HTTPS protocol. Number of used technologies: 9. First technologies: CSS, Google Font API, Html, Number of used javascripts: 35. First javascripts: Jquery.js, Jquery-migrate.min.js, Core.min.js, Number of used analytics tools: 0. Number of used plugins, modules: 6. Its server type is: nginx/1.10.1. Its CMS is: Wordpress.

Technologies in use by Cutchoguenewsuffolkhistory.org

Technology

Number of occurences: 9

CSS
Google Font API
Html
Html5
Javascript
jQuery
jQuery UI
Php
Pingback

Javascripts

Number of occurences: 35

jquery.js
jquery-migrate.min.js
core.min.js
widget.min.js
position.min.js
mouse.min.js
sortable.min.js
datepicker.min.js
menu.min.js
wp-a11y.min.js
autocomplete.min.js
resizable.min.js
draggable.min.js
button.min.js
dialog.min.js
events-manager.js
modernizr.js
mag-popup.js
jquery.collagePlus.min.js
jquery.elastislide.min.js
srizon.custom.min.js
selectmenu.min.js
main.js
skip-links.js
jquery.fitvids.js
global.js
responsive-menu.js
jquery.bxslider.min.js
site.js
hoverIntent.min.js
superfish.min.js
superfish.args.min.js
wp-embed.min.js
google-maps-builder.min.js
map-icons.js

Content Management System

Number of occurences: 1

Wordpress

Server Type

nginx/1.10.1

Used plugins, modules

Number of plugins and modules: 6

events manager
srizon facebook album
wp fullcalendar
google maps builder
simple social icons
timeline

Conversion rate optimization
Clickable call number	Not founded!
Conversion form (contact form, subcriber)	Founded!
Clickable email	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) - Cutchoguenewsuffolkhistory.org

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 - Cutchoguenewsuffolkhistory.org

Number of occurences: 4

Name:
Content: http://www.cutchoguenewsuffolkhistory.org/
Name: description
Content: Preserving history
Name: robots
Content: noodp,noydir
Name: viewport
Content: width=device-width, initial-scale=1

Server / Hosting

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

Rname

ns2.bluehost.com
ns1.bluehost.com
mail.cutchoguenewsuffolkhistory.org

Target

root.box1145.bluehost.com

HTTP Header Response

HTTP/1.1 200 OK Server: nginx/1.10.1 Date: Fri, 22 Jul 2016 04:34:30 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