Statistics

Turf Grass Organics

www.turfgrassorganics.com/

Turfgrass Organics was established to provide a permanent dedicated medium for providing information on an organic turfgrass management approach.

Turfgrassorganics.com

Conversion Technology Metas Server

Turfgrassorganics.com is hosted in United States / Provo . Turfgrassorganics.com uses HTTPS protocol. Number of used technologies: 10. First technologies: CSS, Gravatar, Html, Number of used javascripts: 10. First javascripts: Jquery.js, Jquery-migrate.min.js, Mc-validate.js, Number of used analytics tools: 2. First analytics tools: Google Analytics, WordPress Stats, Number of used plugins, modules: 4. Its server type is: nginx/1.10.1. Its CMS is: Wordpress.

Technologies in use by Turfgrassorganics.com

Technology

Number of occurences: 10

CSS
Gravatar
Html
Html5
Iframe
Javascript
jQuery
Php
Pingback
SVG

Javascripts

Number of occurences: 10

jquery.js
jquery-migrate.min.js
mc-validate.js
photon.js
editor.js
devicepx-jetpack.js
gprofiles.js
wpgroho.js
wp-embed.min.js
e-201637.js

Content Management System

Number of occurences: 1

Wordpress

Analytics

Number of occurences: 2

Google Analytics
WordPress Stats

Server Type

nginx/1.10.1

Used plugins, modules

Number of plugins and modules: 4

jetpack
bbpress
photon
wpgroho.js?ver=4.6.1 http:

Google Analytics ID

UA-75336426-1

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

Number of occurences: 5

Name:
Content: UserComments:0
Name: viewport
Content: width=device-width, initial-scale=1
Name: description
Content: Turfgrass Organics was established to provide a permanent dedicated medium for providing information on an organic turfgrass management approach.
Name: robots
Content: noodp, noydir
Name: google-site-verification
Content: qbAWJvTDAwC7RyENco-5Ve8S-hCBwyRubjU6VuWLHfw

Server / Hosting

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

Rname

ns1.bluehost.com
ns2.bluehost.com
mail.turfgrassorganics.com

Target

dnsadmin.box392.bluehost.com

HTTP Header Response

HTTP/1.1 200 OK Server: nginx/1.10.1 Date: Sat, 17 Sep 2016 02:50:25 GMT Content-Type: text/html; charset=UTF-8 Link: ; rel="https://api.w.org/", ; rel=shortlink Vary: Accept-Encoding X-Cache: MISS from s_wx1113 Transfer-Encoding: chunked Via: 1.1 s_wx1113 (squid/3.5.20) Connection: keep-alive