Statistics

Data Recovery Guide | What To Do Next

www.stopasianelderabuse.org/

When faced with a data emergency, it's easy to become paralyzed and not know what to do next. Here's a look at data recovery for every type of system.

Stopasianelderabuse.org

Conversion Technology Metas Server

Stopasianelderabuse.org is hosted in United States / Provo . Stopasianelderabuse.org uses HTTPS protocol. Number of used technologies: 9. First technologies: CSS, Font Awesome, Html, Number of used javascripts: 24. First javascripts: Jquery.js, Jquery-migrate.min.js, In.js, Number of used analytics tools: 0. Number of used plugins, modules: 2. Its server type is: nginx/1.10.1. Its CMS is: Wordpress.

Technologies in use by Stopasianelderabuse.org

Technology

Number of occurences: 9

CSS
Font Awesome
Html
Iframe
Javascript
jQuery
Php
Pingback
SuperFish

Javascripts

Number of occurences: 24

jquery.js
jquery-migrate.min.js
in.js
jquery.form.min.js
scripts.js
superfish.js
jquery.matchHeight.js
slick.js
jquery.mmenu.oncanvas.js
jquery.mmenu.offcanvas.js
jquery.mmenu.navbars.js
jquery.mmenu.autoheight.js
jquery.fitvids.js
jquery.magnific-popup.js
wp-embed.min.js

Content Management System

Number of occurences: 1

Wordpress

Server Type

nginx/1.10.1

Social

Number of occurences: 3

Facebook Like button
Linkedin Share button
Twitter Button

Used plugins, modules

Number of plugins and modules: 2

contact form 7
social share boost

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

Number of occurences: 7

Name:
Content: Data Recovery Guide
Name: viewport
Content: width=device-width, initial-scale=1
Name: description
Content: When faced with a data emergency, it's easy to become paralyzed and not know what to do next. Here's a look at data recovery for every type of system.
Name: robots
Content: noodp
Name: twitter:card
Content: summary
Name: twitter:description
Content: When faced with a data emergency, it's easy to become paralyzed and not know what to do next. Here's a look at data recovery for every type of system.
Name: twitter:title
Content: Data Recovery Guide | What To Do Next

Server / Hosting

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

Rname

ns2.bluehost.com
ns1.bluehost.com
mail.stopasianelderabuse.org

Target

root.box1215.bluehost.com

HTTP Header Response

HTTP/1.1 200 OK Server: nginx/1.10.1 Date: Fri, 15 Jul 2016 21:24:33 GMT Content-Type: text/html; charset=UTF-8 Link: ; rel="https://api.w.org/" Set-Cookie: wfvt_482957794=57895491d27d7; expires=Fri, 15-Jul-2016 21:54:33 GMT; Max-Age=1800; path=/; httponly Vary: Accept-Encoding X-Cache: MISS from s_hp69 X-Cache-Lookup: MISS from s_hp69:80 Via: 1.1 s_hp69 (squid/3.5.19) Connection: keep-alive