Bearhuntcontroversy.com

Bearhuntcontroversy.com is hosted in United States / San Francisco . Bearhuntcontroversy.com uses HTTPS protocol. Number of used technologies: 6. First technologies: CSS, Gravatar, Html, Number of used javascripts: 3. First javascripts: Gprofiles.js, Wpgroho.js, W.js, Number of used analytics tools: 1. First analytics tools: ComScore, Its server type is: nginx. Its CMS is: Wordpress.

Technologies in use by Bearhuntcontroversy.com

Technology

Number of occurences: 6

CSS
Gravatar
Html
Javascript
Php
Pingback

Javascripts

Number of occurences: 3

gprofiles.js
wpgroho.js
w.js

Content Management System

Number of occurences: 1

Wordpress

Analytics

Number of occurences: 1

comScore

Server Type

nginx

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	Not 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) - Bearhuntcontroversy.com

SSL certificate

name: /CN=tls.automattic.com
subject:
- CN: tls.automattic.com
hash: 6338c477
issuer:
- C: US
- O: Let's Encrypt
- CN: Let's Encrypt Authority X3
version: 2
serialNumber: 340865938475290992619734963353065516145982
validFrom: 160607125600Z
validTo: 160905125600Z
validFrom_time_t: 1465304160
validTo_time_t: 1473080160
extensions:
- keyUsage: Digital Signature, Key Encipherment
- extendedKeyUsage: TLS Web Server Authentication, TLS Web Client Authentication
- basicConstraints: CA:FALSE
- subjectKeyIdentifier: 0C:71:E2:BB:8E:B3:CE:6C:22:9C:54:EF:71:C0:D4:BB:FD:4E:A2:6A
- 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:bearhandsholistic.ca, DNS:bearhavenmama.com, DNS:bearheart.live, DNS:bearhillers.net, DNS:bearhousebeads.com, DNS:bearhugsandblueeyes.com, DNS:bearhuntcontroversy.com, DNS:bearinabackpack.com, DNS:bearingsbybsc.com, DNS:bearingthesword.com, DNS:bearinmindblog.com, DNS:bearistablog.org, DNS:bearister.me, DNS:bearkatlaw.com, DNS:bearkillers.com, DNS:bearlakemichigan49614.com, DNS:bearlakemonster.com, DNS:bearlaketownship.com, DNS:bearlaketownshipfiredepartment.com, DNS:bearlakevacation.com, DNS:bearloka.com, DNS:bearlovesdove.com, DNS:bearlyasound.com, DNS:bearlybliss.com, DNS:bearmediallc.com, DNS:tls.automattic.com, DNS:www.bearhammerinvestigations.com, DNS:www.bearhandsholistic.ca, DNS:www.bearhavenmama.com, DNS:www.bearheart.live, DNS:www.bearhillers.net, DNS:www.bearhousebeads.com, DNS:www.bearhugsandblueeyes.com, DNS:www.bearhuntcontroversy.com, DNS:www.bearinabackpack.com, DNS:www.bearingsbybsc.com, DNS:www.bearingthesword.com, DNS:www.bearinmindblog.com, DNS:www.bearistablog.org, DNS:www.bearister.me, DNS:www.bearkatlaw.com, DNS:www.bearkillers.com, DNS:www.bearlakemichigan49614.com, DNS:www.bearlakemonster.com, DNS:www.bearlaketownship.com, DNS:www.bearlaketownshipfiredepartment.com, DNS:www.bearlakevacation.com, DNS:www.bearloka.com, DNS:www.bearlovesdove.com, DNS:www.bearlyasound.com, DNS:www.bearlybliss.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 - Bearhuntcontroversy.com

Number of occurences: 11

Name:
Content: https://www.facebook.com/WordPresscom
Name: generator
Content: WordPress.com
Name: twitter:site
Content: @wordpressdotcom
Name: twitter:image
Content: https://bearhuntcontroversydotcom.files.wordpress.com/2013/06/740470_460006250728299_1971682471_o.jpg?w=1400
Name: twitter:card
Content: photo
Name: twitter:description
Content: Photo post.
Name: application-name
Content: bear hunt controversy
Name: msapplication-window
Content: width=device-width;height=device-height
Name: msapplication-task
Content: name=WordPress.com Forums;action-uri=http://forums.wordpress.com/;icon-uri=https://s2.wp.com/i/favicon.ico
Name: title
Content: | bear hunt controversy on WordPress.com
Name: description
Content: Â

Server / Hosting

IP: 192.0.78.24
Latitude: 37.75
Longitude: -122.42
Country: United States
City: San Francisco

Rname

ns3.wordpress.com
ns1.wordpress.com
ns2.wordpress.com

Target

hostmaster.wordpress.com

HTTP Header Response

HTTP/1.1 301 Moved Permanently Server: nginx Date: Fri, 01 Jul 2016 09:42:05 GMT Content-Type: text/html Content-Length: 178 Location: https://bearhuntcontroversy.com/ X-ac: 3.fra _dfw X-Cache: MISS from s_xt27 X-Cache-Lookup: MISS from s_xt27:80 Via: 1.1 s_xt27 (squid/3.5.6) Connection: keep-alive HTTP/1.1 200 Connection established HTTP/1.1 200 OK Server: nginx Date: Fri, 01 Jul 2016 09:42:06 GMT Content-Type: text/html; charset=UTF-8 Connection: keep-alive Strict-Transport-Security: max-age=86400 Vary: Accept-Encoding Vary: Cookie X-hacker: If you're reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header. Link: ; rel=shortlink X-ac: 3.fra _dfw