Trauringe-montfort22.de

Trauringe-montfort22.de is hosted in Germany . Trauringe-montfort22.de uses HTTPS protocol. Number of used technologies: 9. First technologies: CSS, Gravatar, Html, Number of used javascripts: 14. First javascripts: Jquery.js,qver=...JPNMRNN.js, Jquery-migrate....NjdU8Wl.js, Jquery.fitvids....wz9XLHY.js, Number of used analytics tools: 1. First analytics tools: WordPress Stats, Number of used plugins, modules: 1. Its server type is: Apache. Its CMS is: Wordpress.

Technologies in use by Trauringe-montfort22.de

Technology

Number of occurences: 9

CSS
Gravatar
Html
Html5
Javascript
jQuery
PageSpeed Module
Php
Pingback

Javascripts

Number of occurences: 14

jquery.js,qver=1.11.3.pagespeed.jm.zixJPNMRNN.js
jquery-migrate.min.js,qver=1.2.1.pagespeed.jm.mhpNjdU8Wl.js
jquery.fitvids.js,qver=1.1.pagespeed.jm.fWUwz9XLHY.js
devicepx-jetpack.js
gprofiles.js
wp-content,_plugins,_jetpack,_modules,_wpgroho.js,qver==4.4.2+wp-content,_themes,_blackwalnut,_js,_transform.js,qver==20150420+wp-content,_themes,_blackwalnut,_js,_functions.js,qver==20150206+wp-includes,_js,_masonry.min.js,qver==3.1.2.pagespeed.jc.193vULD-N1.js
e-201619.js

Content Management System

Number of occurences: 1

Wordpress

Analytics

Number of occurences: 1

WordPress Stats

Server Type

Apache

Powered by

PleskLin

Used plugins, modules

Number of plugins and modules: 1

jetpack

Conversion rate optimization
Clickable call number	Not founded!
Conversion form (contact form, subcriber)	Not 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) - Trauringe-montfort22.de

SSL certificate

name: /OU=Domain Control Validated/OU=PositiveSSL Wildcard/CN=*.dogado.de
subject:
- OU:
  - 0: Domain Control Validated
  - 1: PositiveSSL Wildcard
- CN: *.dogado.de
hash: ef1ee26e
issuer:
- C: GB
- ST: Greater Manchester
- L: Salford
- O: COMODO CA Limited
- CN: COMODO RSA Domain Validation Secure Server CA
version: 2
serialNumber: 232024019729092545589976475122430230988
validFrom: 150402000000Z
validTo: 160402235959Z
validFrom_time_t: 1427932800
validTo_time_t: 1459641599
extensions:
- authorityKeyIdentifier: keyid:90:AF:6A:3A:94:5A:0B:D8:90:EA:12:56:73:DF:43:B4:3A:28:DA:E7
- subjectKeyIdentifier: 73:AC:F7:CA:4F:73:55:18:44:F5:A3:32:17:FE:02:A3:64:21:C7:BC
- 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:*.dogado.de, DNS:dogado.de

Meta - Trauringe-montfort22.de

Number of occurences: 6

Name:
Content: de_DE
Name: viewport
Content: width=device-width,initial-scale=1
Name: google-site-verification
Content: 8Co6mCnQ8KyYxAQt0BfRQmXkiMF-28T5rfTPlBhiT94
Name: generator
Content: WordPress 4.4.2
Name: twitter:card
Content: summary
Name: msapplication-TileImage
Content: http://trauringe-montfort22.de/wp-content/uploads/2015/09/cropped-menu-270x270.png

Server / Hosting

IP: 128.127.66.50
Latitude: 51.30
Longitude: 9.49
Country: Germany

Rname

dns01.providerbox.de
dns02.providerbox.de
dns03.providerbox.de
mail.trauringe-montfort22.de

Target

dnsadmin.providerbox.de

HTTP Header Response

HTTP/1.1 200 OK Date: Sat, 14 May 2016 13:53:58 GMT Server: Apache Link: ; rel="https://api.w.org/", ; rel=shortlink X-Powered-By: PleskLin Vary: Accept-Encoding Cache-Control: max-age=0, no-cache Content-Type: text/html; charset=UTF-8 X-Cache: MISS from s_bd41 X-Cache-Lookup: MISS from s_bd41:80 Via: 1.1 s_bd41 (squid/3.5.19) Connection: keep-alive