Ozarkfitnesslawsuit.com

Ozarkfitnesslawsuit.com is hosted in United States / Scottsdale . Ozarkfitnesslawsuit.com uses HTTPS protocol. Number of used technologies: 11. First technologies: CSS, Google Font API, Gravatar, Number of used javascripts: 18. First javascripts: Jquery.js, Jquery-migrate.min.js, Flowplayer.min.js, Number of used analytics tools: 1. First analytics tools: WordPress Stats, Number of used plugins, modules: 6. Its server type is: Apache/2.4.23. Its CMS is: Wordpress.

Technologies in use by Ozarkfitnesslawsuit.com

Technology

Number of occurences: 11

CSS
Google Font API
Gravatar
Html
Html5
Iframe
Javascript
jQuery
Php
Pingback
SVG

Javascripts

Number of occurences: 18

jquery.js
jquery-migrate.min.js
flowplayer.min.js
photon.js
devicepx-jetpack.js
gprofiles.js
wpgroho.js
imagesloaded.min.js
masonry.min.js
jquery.masonry.min.js
functions.js
wp-embed.min.js
postmessage.js
jquery.jetpack-resize.js
jquery.inview.js
queuehandler.js
sharing.js
e-201639.js

Content Management System

Number of occurences: 1

Wordpress

Analytics

Number of occurences: 1

WordPress Stats

Server Type

Apache/2.4.23

Powered by

PHP/5.4.45

Used plugins, modules

Number of plugins and modules: 6

easy video player
jetpack
photon
wpgroho.js?ver=4.6.1 http:
likes
sharedaddy

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

SSL certificate

name: /C=US/ST=Arizona/L=Scottsdale/O=Special Domain Services, LLC./CN=*.prod.iad2.secureserver.net
subject:
- C: US
- ST: Arizona
- L: Scottsdale
- O: Special Domain Services, LLC.
- CN: *.prod.iad2.secureserver.net
hash: c6d19db4
issuer:
- C: US
- ST: Arizona
- L: Scottsdale
- O: Starfield Technologies, Inc.
- OU: http://certs.starfieldtech.com/repository/
- CN: Starfield Secure Certificate Authority - G2
version: 2
serialNumber: 16522704787133396204
validFrom: 150120175838Z
validTo: 180120175838Z
validFrom_time_t: 1421776718
validTo_time_t: 1516471118
extensions:
- basicConstraints: CA:FALSE
- extendedKeyUsage: TLS Web Server Authentication, TLS Web Client Authentication
- keyUsage: Digital Signature, Key Encipherment
- crlDistributionPoints: Full Name: URI:http://crl.starfieldtech.com/sfig2s2-0.crl
- certificatePolicies: Policy: 2.16.840.1.114414.1.7.23.2 CPS: http://certificates.starfieldtech.com/repository/
- authorityInfoAccess: OCSP - URI:http://ocsp.starfieldtech.com/ CA Issuers - URI:http://certificates.starfieldtech.com/repository/sfig2.crt
- authorityKeyIdentifier: keyid:25:45:81:68:50:26:38:3D:3B:2D:2C:BE:CD:6A:D9:B6:3D:B3:66:63
- subjectAltName: DNS:*.prod.iad2.secureserver.net, DNS:prod.iad2.secureserver.net
- subjectKeyIdentifier: C6:B5:9A:C6:B2:84:51:1C:E4:8A:55:F1:9F:2B:9A:45:39:FB:F9:C8

Meta - Ozarkfitnesslawsuit.com

Number of occurences: 4

Name:
Content: http://www.ozarkfitnesslawsuit.com
Name: viewport
Content: width=device-width
Name: generator
Content: WordPress 4.6.1
Name: msapplication-TileImage
Content: http://i1.wp.com/www.ozarkfitnesslawsuit.com/wp-content/uploads/2016/01/cropped-Banner_High.jpg?fit=270%2C270

Server / Hosting

IP: 107.180.51.102
Latitude: 33.61
Longitude: -111.89
Country: United States
City: Scottsdale

Rname

ns10.domaincontrol.com
ns09.domaincontrol.com
mail.ozarkfitnesslawsuit.com

Target

dns.jomax.net

HTTP Header Response

HTTP/1.1 200 OK Date: Mon, 26 Sep 2016 21:34:25 GMT Server: Apache/2.4.23 X-Powered-By: PHP/5.4.45 Link: ; rel="https://api.w.org/", ; rel=shortlink Set-Cookie: wordpress_clef_state=KUhaE9e7P9FFPlvJg74q3Mhf; expires=Tue, 27-Sep-2016 21:34:32 GMT; path=/; httponly Vary: Accept-Encoding,User-Agent Content-Type: text/html; charset=UTF-8 X-Cache: MISS from s_ub13 Transfer-Encoding: chunked Via: 1.1 s_ub13 (squid/3.5.20) Connection: keep-alive