Whathappenedtofood.org

Whathappenedtofood.org is hosted in United States / Chesterfield . Whathappenedtofood.org uses HTTPS protocol. Number of used technologies: 9. First technologies: CSS, Google Font API, Html, Number of used javascripts: 12. First javascripts: Jquery.js, Jquery-migrate.min.js, Jquery.tools.min.js, Number of used analytics tools: 0. Number of used plugins, modules: 1. Its server type is: Apache. Its CMS is: Wordpress.

Technologies in use by Whathappenedtofood.org

Technology

Number of occurences: 9

CSS
Google Font API
Html
Html5
Javascript
jQuery
Php
Pingback
Shortcodes

Javascripts

Number of occurences: 12

jquery.js
jquery-migrate.min.js
jquery.tools.min.js
frontend-builder-global-functions.js
jquery.mobile.custom.min.js
custom.js
jquery.fitvids.js
waypoints.min.js
jquery.magnific-popup.js
frontend-builder-scripts.js
wp_footer.js
wp-embed.min.js

Content Management System

Number of occurences: 1

Wordpress

Server Type

Apache

Used plugins, modules

Number of plugins and modules: 1

footnotes

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) - Whathappenedtofood.org

SSL certificate

name: /C=US/ST=Delaware/L=Welmington/O=SureSupport LLC/CN=*.s463.sureserver.com/emailAddress=webmaster@sureserver.com
subject:
- C: US
- ST: Delaware
- L: Welmington
- O: SureSupport LLC
- CN: *.s463.sureserver.com
- emailAddress: webmaster@sureserver.com
hash: 28ebd3e1
issuer:
- C: IL
- O: StartCom Ltd.
- OU: Secure Digital Certificate Signing
- CN: StartCom Class 2 Primary Intermediate Server CA
version: 2
serialNumber: 1883247238896700
validFrom: 150211023002Z
validTo: 170210234227Z
validFrom_time_t: 1423621802
validTo_time_t: 1486770147
extensions:
- basicConstraints: CA:FALSE
- keyUsage: Digital Signature, Key Encipherment, Key Agreement
- extendedKeyUsage: TLS Web Client Authentication, TLS Web Server Authentication
- subjectKeyIdentifier: 10:A0:8C:94:F0:EF:29:E1:C6:A6:E7:57:92:38:19:83:F2:C0:96:44
- authorityKeyIdentifier: keyid:11:DB:23:45:FD:54:CC:6A:71:6F:84:8A:03:D7:BE:F7:01:2F:26:86
- subjectAltName: DNS:*.s463.sureserver.com, DNS:sureserver.com, DNS:s463.sureserver.com, DNS:mysql.admin.s463.sureserver.com, DNS:mysql5.admin.s463.sureserver.com
- certificatePolicies: Policy: 2.23.140.1.2.2 Policy: 1.3.6.1.4.1.23223.1.2.3 CPS: http://www.startssl.com/policy.pdf User Notice: Organization: StartCom Certification Authority Number: 1 Explicit Text: This certificate was issued according to the Class 2 Validation requirements of the StartCom CA policy, reliance only for the intended purpose in compliance of the relying party obligations.
- crlDistributionPoints: Full Name: URI:http://crl.startssl.com/crt2-crl.crl
- authorityInfoAccess: OCSP - URI:http://ocsp.startssl.com/sub/class2/server/ca CA Issuers - URI:http://aia.startssl.com/certs/sub.class2.server.ca.crt
- issuerAltName: URI:http://www.startssl.com/

Meta - Whathappenedtofood.org

Number of occurences: 4

Name:
Content:
Name: generator
Content: WordPress 4.5.4
Name: viewport
Content: width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=0
Name: msapplication-TileImage
Content: http://www.whathappenedtofood.org/wp-content/uploads/2015/11/cropped-WHTF-icon-02-270x270.png

Server / Hosting

IP: 64.14.78.33
Latitude: 38.65
Longitude: -90.53
Country: United States
City: Chesterfield

Rname

ns1.s463.sureserver.com
ns2.s463.sureserver.com
mail.whathappenedtofood.org

Target

hostmaster.whathappenedtofood.org

HTTP Header Response

HTTP/1.1 200 OK Date: Tue, 20 Sep 2016 17:14:10 GMT Server: Apache Link: ; rel="https://api.w.org/", ; rel=shortlink Content-Type: text/html; charset=UTF-8 X-Cache: MISS from s_bd43 Transfer-Encoding: chunked Via: 1.1 s_bd43 (squid/3.5.20) Connection: keep-alive