Loading...
Statistics
Advertisement

Initiative | SCHLÃœSSELMENSCH e.V. | Wir vermitteln Patenschaften ...
www.what-should-we-do.org/
Initiative | SCHLÃœSSELMENSCH e.V. -

What-should-we-do.org

Domain is redirected to: Initiative-schluesselmensch.org
Advertisement
What-should-we-do.org is hosted in Germany . What-should-we-do.org uses HTTPS protocol. Number of used technologies: 11. First technologies: CSS, Html, Html5, Number of used javascripts: 29. First javascripts: Jquery.js, Upload.js, Jquery.validate.js, Number of used analytics tools: 0. Number of used plugins, modules: 1. Its server type is: Apache. Its CMS is: Wordpress.

Technologies in use by What-should-we-do.org

Technology

Number of occurences: 11
  • CSS
  • Html
  • Html5
  • Iframe
  • Javascript
  • jQuery
  • jQuery Cookie
  • jQuery Validate
  • jQuery UI
  • Php
  • Pingback

Advertisement

Javascripts

Number of occurences: 29
  • jquery.js
  • upload.js
  • jquery.validate.js
  • swfupload.js
  • swfupload.queue.js
  • swfupload-all.js
  • handlers.min.js
  • jquery.cookie.js
  • jquery.remodal.js
  • weaverjslib.min.js
  • jquery.ui.core.min.js
  • jquery.ui.widget.min.js
  • jquery.ui.mouse.min.js
  • jquery.ui.resizable.min.js
  • jquery.ui.draggable.min.js
  • jquery.ui.button.min.js
  • jquery.ui.position.min.js
  • jquery.ui.dialog.min.js
  • jquery.ui.tabs.min.js
  • jquery.form.min.js
  • thickbox.js
  • underscore.min.js
  • shortcode.min.js
  • media-upload.min.js
  • jquery.ui.effect.min.js
  • jquery.ui.effect-pulsate.min.js
  • jquery.ui.effect-highlight.min.js
  • utils.min.js
  • editor.min.js

Content Management System

Number of occurences: 1
  • Wordpress

Server Type

  • Apache

Used plugins, modules

Number of plugins and modules: 1
  • sp client document manager

Conversion rate optimization

visitors Clickable call number Not founded!
visitors Conversion form (contact form, subcriber) Not founded!
visitors Clickable email Not founded!
visitors CTA (call to action) button Not founded!
visitors List Founded!
visitors Image Not founded!
visitors Enhancement Not founded!
visitors Responsive website Founded!
visitors Facebook sharing Not founded!
visitors Google+ sharing Not founded!
visitors Twitter sharing Not founded!
visitors Linkedin sharing Not founded!
visitors Blog on the webiste Not founded!

HTTPS (SSL) - What-should-we-do.org

SSL certificate

    • name: /OU=Domain Control Validated/OU=Hosted by Alfahosting GmbH/OU=PositiveSSL Wildcard/CN=*.alfahosting-server.de
    • subject:
      • OU:
        • 0: Domain Control Validated
        • 1: Hosted by Alfahosting GmbH
        • 2: PositiveSSL Wildcard
      • CN: *.alfahosting-server.de
    • hash: 106f7d13
    • issuer:
      • C: GB
      • ST: Greater Manchester
      • L: Salford
      • O: COMODO CA Limited
      • CN: COMODO RSA Domain Validation Secure Server CA
    • version: 2
    • serialNumber: 162537403823597637267999238811244445824
    • validFrom: 151005000000Z
    • validTo: 170222235959Z
    • validFrom_time_t: 1444003200
    • validTo_time_t: 1487807999
    • extensions:
      • authorityKeyIdentifier: keyid:90:AF:6A:3A:94:5A:0B:D8:90:EA:12:56:73:DF:43:B4:3A:28:DA:E7
      • subjectKeyIdentifier: 39:45:34:98:FB:80:C2:AC:57:D6:FB:ED:2D:FD:ED:C4:E2:65:4A: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:*.alfahosting-server.de, DNS:alfahosting-server.de

Meta - What-should-we-do.org

Number of occurences: 5
  • Name:
    Content:
  • Name: viewport
    Content: width=device-width, initial-scale=1.0, maximum-scale=2.0, user-scalable=yes
  • Name: generator
    Content: WordPress 3.5.1
  • Name: description
    Content: Initiative | SCHLÃœSSELMENSCH e.V. -
  • Name: keywords
    Content: Initiative | SCHLÃœSSELMENSCH e.V. blog, Initiative | SCHLÃœSSELMENSCH e.V.

Server / Hosting

  • IP: 109.237.140.6
  • Latitude: 51.30
  • Longitude: 9.49
  • Country: Germany

Rname

  • cns1.alfahosting.info
  • cns2.alfahosting.info
  • cns3.alfahosting.info
  • mail.what-should-we-do.org

Target

  • hostmaster.alfahosting.de

HTTP Header Response

HTTP/1.1 302 Found Date: Tue, 23 Aug 2016 13:18:02 GMT Server: Apache Location: http://initiative-schluesselmensch.org/ Content-Length: 298 Content-Type: text/html; charset=iso-8859-1 X-Cache: MISS from s_wx1123 X-Cache-Lookup: MISS from s_wx1123:80 Via: 1.1 s_wx1123 (squid/3.5.16) Connection: keep-alive HTTP/1.1 200 OK Date: Tue, 23 Aug 2016 13:18:03 GMT Server: Apache X-Pingback: http://initiative-schluesselmensch.org/xmlrpc.php Accept-Ranges: none Vary: Accept-Encoding Content-Type: text/html; charset=UTF-8 X-Cache: MISS from s_wx1123 X-Cache-Lookup: MISS from s_wx1123:80 Transfer-Encoding: chunked Via: 1.1 s_wx1123 (squid/3.5.16) Connection: keep-alive

DNS

host: what-should-we-do.org
  1. class: IN
  2. ttl: 10800
  3. type: A
  4. ip: 109.237.140.6
host: what-should-we-do.org
  1. class: IN
  2. ttl: 86400
  3. type: NS
  4. target: cns1.alfahosting.info
host: what-should-we-do.org
  1. class: IN
  2. ttl: 86400
  3. type: NS
  4. target: cns2.alfahosting.info
host: what-should-we-do.org
  1. class: IN
  2. ttl: 86400
  3. type: NS
  4. target: cns3.alfahosting.info
host: what-should-we-do.org
  1. class: IN
  2. ttl: 10800
  3. type: SOA
  4. mname: cns1.alfahosting.info
  5. rname: hostmaster.alfahosting.de
  6. serial: 2015082401
  7. refresh: 28800
  8. retry: 7200
  9. expire: 604800
  10. minimum-ttl: 10800
host: what-should-we-do.org
  1. class: IN
  2. ttl: 86400
  3. type: MX
  4. pri: 10
  5. target: mail.what-should-we-do.org

Common Typos/Mistakes

This list shows You some spelling mistakes at internet search for this domain.

www.hat-should-we-do.org, www.w hat-should-we-do.org, www. hat-should-we-do.org, www.what-should-we-do.org, www.hat-should-we-do.org, www.wdhat-should-we-do.org, www.dhat-should-we-do.org, www.wfhat-should-we-do.org, www.fhat-should-we-do.org, www.wghat-should-we-do.org, www.ghat-should-we-do.org, www.wbhat-should-we-do.org, www.bhat-should-we-do.org, www.wat-should-we-do.org, www.wheat-should-we-do.org, www.weat-should-we-do.org, www.whdat-should-we-do.org, www.wdat-should-we-do.org, www.whcat-should-we-do.org, www.wcat-should-we-do.org, www.whuat-should-we-do.org, www.wuat-should-we-do.org, www.whjat-should-we-do.org, www.wjat-should-we-do.org, www.what-should-we-do.org, www.wat-should-we-do.org, www.whbat-should-we-do.org, www.wbat-should-we-do.org, www.whgat-should-we-do.org, www.wgat-should-we-do.org, www.wht-should-we-do.org, www.whaot-should-we-do.org, www.whot-should-we-do.org, www.whapt-should-we-do.org, www.whpt-should-we-do.org, www.wha9t-should-we-do.org, www.wh9t-should-we-do.org, www.what-should-we-do.org, www.wht-should-we-do.org, www.whait-should-we-do.org, www.whit-should-we-do.org, www.whaut-should-we-do.org, www.whut-should-we-do.org, www.wha-should-we-do.org, www.whatq-should-we-do.org, www.whaq-should-we-do.org, www.whata-should-we-do.org, www.whaa-should-we-do.org, www.what -should-we-do.org, www.wha -should-we-do.org, www.whatw-should-we-do.org, www.whaw-should-we-do.org, www.whate-should-we-do.org, www.whae-should-we-do.org, www.whatz-should-we-do.org, www.whaz-should-we-do.org, www.whatx-should-we-do.org, www.whax-should-we-do.org, www.whatc-should-we-do.org, www.whac-should-we-do.org, www.whatshould-we-do.org, www.what-tshould-we-do.org, www.whattshould-we-do.org, www.what-gshould-we-do.org, www.whatgshould-we-do.org, www.what-hshould-we-do.org, www.whathshould-we-do.org, www.what-ushould-we-do.org, www.whatushould-we-do.org, www.what-jshould-we-do.org, www.whatjshould-we-do.org, www.what-xshould-we-do.org, www.whatxshould-we-do.org, www.what-sshould-we-do.org, www.whatsshould-we-do.org, www.what-ashould-we-do.org, www.whatashould-we-do.org, www.what-should-we-do.org, www.whatshould-we-do.org, www.what- should-we-do.org, www.what should-we-do.org, www.what-hould-we-do.org, www.what-sehould-we-do.org, www.what-ehould-we-do.org, www.what-swhould-we-do.org, www.what-whould-we-do.org, www.what-sdhould-we-do.org, www.what-dhould-we-do.org, www.what-sxhould-we-do.org, www.what-xhould-we-do.org, www.what-sfhould-we-do.org, www.what-fhould-we-do.org, www.what-sghould-we-do.org, www.what-ghould-we-do.org, www.what-sthould-we-do.org, www.what-thould-we-do.org, www.what-sould-we-do.org, www.what-sheould-we-do.org, www.what-seould-we-do.org, www.what-shdould-we-do.org, www.what-sdould-we-do.org, www.what-shcould-we-do.org, www.what-scould-we-do.org, www.what-shuould-we-do.org, www.what-suould-we-do.org, www.what-shjould-we-do.org, www.what-sjould-we-do.org, www.what-should-we-do.org, www.what-sould-we-do.org, www.what-shbould-we-do.org, www.what-sbould-we-do.org, www.what-shgould-we-do.org, www.what-sgould-we-do.org, www.what-shuld-we-do.org, www.what-shobuld-we-do.org, www.what-shbuld-we-do.org, www.what-shohuld-we-do.org, www.what-shhuld-we-do.org, www.what-shoguld-we-do.org, www.what-shguld-we-do.org, www.what-shojuld-we-do.org, www.what-shjuld-we-do.org, www.what-shomuld-we-do.org, www.what-shmuld-we-do.org, www.what-sho uld-we-do.org, www.what-sh uld-we-do.org, www.what-shovuld-we-do.org, www.what-shvuld-we-do.org, www.what-shold-we-do.org, www.what-shouwld-we-do.org, www.what-showld-we-do.org, www.what-shoueld-we-do.org, www.what-shoeld-we-do.org, www.what-shousld-we-do.org, www.what-shosld-we-do.org, www.what-shouald-we-do.org, www.what-shoald-we-do.org, www.what-shoud-we-do.org, www.what-shoulud-we-do.org, www.what-shouud-we-do.org, www.what-shoul8d-we-do.org, www.what-shou8d-we-do.org, www.what-shoul9d-we-do.org, www.what-shou9d-we-do.org, www.what-shouljd-we-do.org, www.what-shoujd-we-do.org, www.what-shoul0d-we-do.org, www.what-shou0d-we-do.org, www.what-shoulmd-we-do.org, www.what-shoumd-we-do.org, www.what-shoulpd-we-do.org, www.what-shoupd-we-do.org, www.what-shoulod-we-do.org, www.what-shouod-we-do.org, www.what-shoul-we-do.org, www.what-shouldt-we-do.org, www.what-shoult-we-do.org, www.what-shouldg-we-do.org, www.what-shoulg-we-do.org, www.what-shouldb-we-do.org, www.what-shoulb-we-do.org, www.what-shouldx-we-do.org, www.what-shoulx-we-do.org, www.what-shoulds-we-do.org, www.what-shouls-we-do.org, www.what-shouldf-we-do.org, www.what-shoulf-we-do.org, www.what-shouldv-we-do.org, www.what-shoulv-we-do.org, www.what-shouldy-we-do.org, www.what-shouly-we-do.org, www.what-shouldz-we-do.org, www.what-shoulz-we-do.org, www.what-shoulda-we-do.org, www.what-shoula-we-do.org, www.what-shoulde-we-do.org, www.what-shoule-we-do.org, www.what-shouldr-we-do.org, www.what-shoulr-we-do.org,

Other websites we recently analyzed

  1. Gross Barmen Resort Namibia
    GrossBarmen.com - The online guide to Namibia: safaris, adventure tours, hunting, fishing, tourism directory and information, bookings and car rental
    France - 164.132.190.162
    Server software: nginx/1.9.12
    Technology: Html
    Number of meta tags: 6
  2. Home - EGGVP - European Group for Generic Veterinary Products
    Belgium - 77.241.83.203
    Server software: Apache
    Technology: CSS, Html, Javascript
    Number of Javascript: 3
    Number of meta tags: 4
  3. katescloset.com
    Scottsdale (United States) - 50.63.202.42
    Server software:
    Technology: Html, Html5, Iframe, Php
  4. datacentrum Host-telecom.com
    Полный спектр телекоммуникационных услуг. Виртуальные серверы VPS/VDS, аренда серверов - dedicated, размещение серверов - colocation, услуги датацентра, телефония. Надежно, доступно удобно.
    Czech Republic - 193.161.84.108
    Server software: Apache/2.2.16 (Unix) PHP/5.2.14
    Technology: Carousel, CSS, Html, Javascript, jQuery, Php, Google Analytics
    Number of Javascript: 3
    Number of meta tags: 7
  5. |
    Japan - 211.1.232.2
    Server software: Apache
    Technology: Html, Javascript
    Number of Javascript: 1
    Number of meta tags: 1
  6. 微信二维码收银系统—微信支付,微信收银,二维码收款,支付宝收银台,微信卡券
    Hangzhou (China) - 115.29.32.241
    Server software: Apache/2.4.7 (Win32) OpenSSL/0.9.8y PHP/5.3.28
    Technology: CSS, Html, Javascript, Php
    Number of Javascript: 1
    Number of meta tags: 2
  7. gld4.com
    Nürnberg (Germany) - 213.239.207.145
    Server software: nginx/1.10.0
    Technology: CSS, Google Font API, Html, Javascript
    Number of Javascript: 4
    Number of meta tags: 3
  8. mhdw.net,您正在访问的域名可以转让!
    域名出售,域名转让,域名交易
    Ottawa (Canada) - 47.90.20.17
    Server software: Microsoft-IIS/7.5
    Technology: CSS, Html, Php
    Number of Javascript: 2
    Number of meta tags: 3
  9. londonolympicsonlineshop.com
    Germany - 217.160.223.135
    Server software: Apache
    Technology: Html
    Number of meta tags: 1
  10. MOJUHLER
    Canada - 23.227.38.69
    G Analytics ID: UA-57198619-1
    Server software: nginx
    Technology: CSS, Html, Html5, Javascript, Php, SVG, Google Analytics, Shopify
    Number of Javascript: 5
    Number of meta tags: 3

Check Other Websites