Futurehealthcaretoday.com

Futurehealthcaretoday.com is hosted in United States / Chicago . Futurehealthcaretoday.com uses HTTPS protocol. Number of used technologies: 9. First technologies: CSS, Google Font API, Html, Number of used javascripts: 13. First javascripts: Jquery.js, Jquery-migrate.min.js, Jquery.form.js, Number of used analytics tools: 0. Number of used plugins, modules: 8. Its server type is: nginx. Its CMS is: Wordpress.

Technologies in use by Futurehealthcaretoday.com

Technology

Number of occurences: 9

CSS
Google Font API
Html
Html5
Javascript
jQuery
Php
Pingback
SVG

Javascripts

Number of occurences: 13

jquery.js
jquery-migrate.min.js
jquery.form.js
waypoints.min.js
jquery.fitvids.js
slick.min.js
frontend.js
addthis_widget.js
jquery.form.min.js
scripts.js
sidebar-automizer.js
jquery.royalslider.min.js
wp-embed.min.js

Content Management System

Number of occurences: 1

Wordpress

Server Type

nginx

Social

Number of occurences: 1

Add This

Used plugins, modules

Number of plugins and modules: 8

accesspress social icons
contact form 7
sidebarautomizer
wysija newsletters
stylish top author widget
feedburner form
display authors widget
addthis

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

SSL certificate

name: /CN=futurehealthcaretoday.com
subject:
- CN: futurehealthcaretoday.com
hash: 866e512e
issuer:
- C: US
- O: Let's Encrypt
- CN: Let's Encrypt Authority X3
version: 2
serialNumber: 324216504601267393948681071291319525630027
validFrom: 170220062000Z
validTo: 170521062000Z
validFrom_time_t: 1487571600
validTo_time_t: 1495347600
signatureTypeSN: RSA-SHA256
signatureTypeLN: sha256WithRSAEncryption
signatureTypeNID: 668
extensions:
- keyUsage: Digital Signature, Key Encipherment
- extendedKeyUsage: TLS Web Server Authentication, TLS Web Client Authentication
- basicConstraints: CA:FALSE
- subjectKeyIdentifier: 8D:9D:A4:D2:01:F0:75:8D:AC:B8:93:50:0D:48:11:AF:44:D1:74:47
- authorityKeyIdentifier: keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
- authorityInfoAccess: OCSP - URI:http://ocsp.int-x3.letsencrypt.org/ CA Issuers - URI:http://cert.int-x3.letsencrypt.org/
- subjectAltName: DNS:futurehealthcaretoday.com, DNS:www.futurehealthcaretoday.com
- certificatePolicies: Policy: 2.23.140.1.2.1 Policy: 1.3.6.1.4.1.44947.1.1.1 CPS: http://cps.letsencrypt.org User Notice: Explicit Text: This Certificate may only be relied upon by Relying Parties and only in accordance with the Certificate Policy found at https://letsencrypt.org/repository/

Meta - Futurehealthcaretoday.com

Number of occurences: 8

Name:
Content: Future Healthcare Today
Name: viewport
Content: width=device-width, initial-scale=1, maximum-scale=1
Name: description
Content: Telehealth best practices for health care delivery and innovation
Name: robots
Content: noodp
Name: twitter:card
Content: summary
Name: twitter:description
Content: Telehealth best practices for health care delivery and innovation
Name: twitter:title
Content: Future Healthcare Today - Telehealth best practices for health care delivery and innovation
Name: generator
Content: WordPress 4.7.2

Server / Hosting

IP: 77.104.162.56
Latitude: 41.81
Longitude: -87.69
Country: United States
City: Chicago

Rname

ns1.usm17.siteground.biz
ns2.usm17.siteground.biz
futurehealthcaretoday.com

Target

dnsadmin.usm17.siteground.biz

HTTP Header Response

HTTP/1.1 301 Moved Permanently Server: nginx Date: Wed, 22 Feb 2017 16:55:06 GMT Content-Type: text/html; charset=iso-8859-1 Content-Length: 242 Location: https://futurehealthcaretoday.com/ X-Proxy-Cache: MISS X-Cache: MISS from s_hv999 Via: 1.1 s_hv999 (squid/3.5.23) Connection: keep-alive HTTP/1.1 200 Connection established HTTP/1.1 200 OK Server: nginx Date: Wed, 22 Feb 2017 16:55:09 GMT Content-Type: text/html; charset=UTF-8 Transfer-Encoding: chunked Connection: keep-alive Vary: Cookie Link: ; rel="https://api.w.org/" Host-Header: 192fc2e7e50945beb8231a492d6a8024 X-Proxy-Cache: MISS