Howtobeabodyguard.net

Howtobeabodyguard.net is hosted in United States / Houston . Howtobeabodyguard.net uses HTTPS protocol. Number of used technologies: 6. First technologies: CSS, Html, Html5, Number of used javascripts: 3. First javascripts: Jquery.js, Jquery-migrate.min.js, Functions.js, Number of used analytics tools: 0. Its server type is: nginx/1.10.1. Its CMS is: Wordpress.

Technologies in use by Howtobeabodyguard.net

Technology

Number of occurences: 6

CSS
Html
Html5
jQuery
Php
Pingback

Javascripts

Number of occurences: 3

jquery.js
jquery-migrate.min.js
functions.js

Content Management System

Number of occurences: 1

Wordpress

Server Type

nginx/1.10.1

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) - Howtobeabodyguard.net

SSL certificate

name: /OU=Domain Control Validated/OU=Hosted by HostGator.com, LLC./OU=PositiveSSL Wildcard/CN=*.websitewelcome.com
subject:
- OU:
  - 0: Domain Control Validated
  - 1: Hosted by HostGator.com, LLC.
  - 2: PositiveSSL Wildcard
- CN: *.websitewelcome.com
hash: b86b2c33
issuer:
- C: GB
- ST: Greater Manchester
- L: Salford
- O: COMODO CA Limited
- CN: COMODO RSA Domain Validation Secure Server CA
version: 2
serialNumber: 73802823338622261546480845931487065049
validFrom: 151016000000Z
validTo: 181015235959Z
validFrom_time_t: 1444953600
validTo_time_t: 1539647999
extensions:
- authorityKeyIdentifier: keyid:90:AF:6A:3A:94:5A:0B:D8:90:EA:12:56:73:DF:43:B4:3A:28:DA:E7
- subjectKeyIdentifier: 11:37:8F:56:DC:AF:E0:18:CB:07:A7:02:00:3C:DE:8C:B8:11:F4:3A
- 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:*.websitewelcome.com, DNS:websitewelcome.com

Meta - Howtobeabodyguard.net

Number of occurences: 3

Name:
Content:
Name: viewport
Content: width=device-width
Name: generator
Content: WordPress 3.8.15

Server / Hosting

IP: 192.185.147.101
Latitude: 29.83
Longitude: -95.47
Country: United States
City: Houston

Rname

ns727.websitewelcome.com
ns728.websitewelcome.com
howtobeabodyguard.net

Target

jalno1.aol.com

HTTP Header Response

HTTP/1.1 301 Moved Permanently Server: nginx/1.10.1 Date: Fri, 02 Sep 2016 21:17:10 GMT Content-Type: text/html; charset=UTF-8 Content-Length: 0 X-Pingback: http://howtobeabodyguard.net/xmlrpc.php Location: http://howtobeabodyguard.net/ X-Cache: MISS from s_wx1011 X-Cache-Lookup: MISS from s_wx1011:80 Via: 1.1 s_wx1011 (squid/3.5.20) Connection: keep-alive HTTP/1.1 200 OK Server: nginx/1.10.1 Date: Fri, 02 Sep 2016 21:17:11 GMT Content-Type: text/html; charset=UTF-8 X-Pingback: http://howtobeabodyguard.net/xmlrpc.php X-Cache: MISS from s_wx1011 X-Cache-Lookup: MISS from s_wx1011:80 Transfer-Encoding: chunked Via: 1.1 s_wx1011 (squid/3.5.20) Connection: keep-alive