Statistics

Besprechungs-Protokoll

www.besprechungsprotokoll.com/

Besprechungsprotokolle sind direkt gefÃ¼hrte Notizen Ã¼ber die Diskussionen und Entscheidungen bzw. Aktionen, die wÃ¤hrend des Meetings stattgefunden haben ...

Besprechungsprotokoll.com

Conversion Technology Metas Server

Besprechungsprotokoll.com is hosted in United States / Scottsdale . Besprechungsprotokoll.com uses HTTPS protocol. Number of used technologies: 5. First technologies: CSS, Html, Html5, Number of used javascripts: 4. First javascripts: Lightbox.js, Html5.js, Jquery-1.7.min.js, Number of used analytics tools: 1. First analytics tools: Google Analytics, Its server type is: Apache.

Technologies in use by Besprechungsprotokoll.com

Technology

Number of occurences: 5

CSS
Html
Html5
Javascript
Php

Javascripts

Number of occurences: 4

lightbox.js
html5.js
jquery-1.7.min.js
addthis_widget.js

Analytics

Number of occurences: 1

Google Analytics

Server Type

Apache

Social

Number of occurences: 1

Add This

Google Analytics ID

UA-34040935-3

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

SSL certificate

name: /OU=Domain Control Validated/CN=matchwaredomains.com
subject:
- OU: Domain Control Validated
- CN: matchwaredomains.com
hash: 67f5be25
issuer:
- C: US
- ST: Arizona
- L: Scottsdale
- O: GoDaddy.com, Inc.
- OU: http://certs.godaddy.com/repository/
- CN: Go Daddy Secure Certificate Authority - G2
version: 2
serialNumber: 1252436496304277
validFrom: 140623133005Z
validTo: 170725214204Z
validFrom_time_t: 1403530205
validTo_time_t: 1501018924
extensions:
- basicConstraints: CA:FALSE
- extendedKeyUsage: TLS Web Server Authentication, TLS Web Client Authentication
- keyUsage: Digital Signature, Key Encipherment
- crlDistributionPoints: Full Name: URI:http://crl.godaddy.com/gdig2s1-80.crl
- certificatePolicies: Policy: 2.16.840.1.114413.1.7.23.1 CPS: http://certificates.godaddy.com/repository/
- authorityInfoAccess: OCSP - URI:http://ocsp.godaddy.com/ CA Issuers - URI:http://certificates.godaddy.com/repository/gdig2.crt
- authorityKeyIdentifier: keyid:40:C2:BD:27:8E:CC:34:83:30:A2:33:D7:FB:6C:B3:F0:B4:2C:80:CE
- subjectAltName: DNS:matchwaredomains.com, DNS:www.matchwaredomains.com, DNS:www.workbreakdownstructure.com
- subjectKeyIdentifier: 94:D9:35:D9:5E:59:5D:6F:B6:26:90:BB:14:3A:92:D4:34:D2:A2:FF

Meta - Besprechungsprotokoll.com

Number of occurences: 6

Name: Description
Content: Besprechungsprotokolle sind direkt gefÃ¼hrte Notizen Ã¼ber die Diskussionen und Entscheidungen bzw. Aktionen, die wÃ¤hrend des Meetings stattgefunden haben. Es gibt drei verschiedene Typen von Besprechungsprotokollen, auf die wir spÃ¤ter nÃ¤her eingehen werden. In jedem Fall ist es nÃ¶tig, schon vor der eigentlichen Besprechung einen ProtokollfÃ¼hrer zu bestimmen. Spezielle Typen von Meetings (Ausschusssitzungen, Vorstandssitzungen etc.) erfordern spezielle Elemente, die eingebunden werden mÃ¼ssen sowie spezielle Ã¤uÃŸere Formen, an die man sich halten muss. Es ist wichtig, all dies bereits vor dem Meeting zu klÃ¤ren.
Name: Keywords
Content: meeting-protokolle, meeting-protokoll-beispiele
Name: title
Content: Besprechungs-Protokoll
Name:
Content: text/html; charset=utf-8
Name: robots
Content: INDEX,FOLLOW,NOODP
Name: viewport
Content: initial-scale=1.0, maximum-scale=1.0, user-scalable=no, width=device-width

Server / Hosting

IP: 50.62.39.12
Latitude: 33.61
Longitude: -111.89
Country: United States
City: Scottsdale

Rname

ns11.domaincontrol.com
ns12.domaincontrol.com
mailstore1.secureserver.net
smtp.secureserver.net

Target

dns.jomax.net

HTTP Header Response

HTTP/1.1 200 OK Date: Sun, 07 Aug 2016 23:18:49 GMT Server: Apache Vary: Accept-Encoding Content-Type: text/html X-Cache: MISS from s_fl343 X-Cache-Lookup: MISS from s_fl343:80 Transfer-Encoding: chunked Via: 1.1 s_fl343 (squid/3.5.9) Connection: keep-alive