Burundi-tourisme.com

Burundi-tourisme.com is hosted in United Kingdom / Gloucester . Burundi-tourisme.com uses HTTPS protocol. Number of used technologies: 13. First technologies: CSS, Fancybox, Google Font API, Number of used javascripts: 24. First javascripts: Jquery.js, Jquery-migrate.min.js, Jquery.themepun...ins.min.js, Number of used analytics tools: 0. Number of used plugins, modules: 2. Its server type is: Apache. Its CMS is: Wordpress.

Technologies in use by Burundi-tourisme.com

Technology

Number of occurences: 13

CSS
Fancybox
Google Font API
Html
Html5
Iframe
Javascript
jQuery
jQuery Fancybox
jQuery UI
Php
Pingback
Revslider

Javascripts

Number of occurences: 24

jquery.js
jquery-migrate.min.js
jquery.themepunch.plugins.min.js
jquery.themepunch.revolution.min.js
jquery.form.min.js
scripts.js
jquery-ui.js
excanvas.js
scroolto.js
jquery.nicescroll.min.js
jquery.fancybox.js
jquery.fancybox-thumbs.js
jquery.inview.min.js
hoverIntent.js
superfish.min.js
tinynav.min.js
jquery.parallax-1.1.3.js
jquery.isotope.min.js
jquery.infinitescroll.min.js
settings.js
comment-reply.min.js
wp-embed.min.js

Content Management System

Number of occurences: 1

Wordpress

Server Type

Apache

Used plugins, modules

Number of plugins and modules: 2

revslider
contact form 7

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) - Burundi-tourisme.com

SSL certificate

name: /OU=Domain Control Validated/CN=premium.afriregister.com
subject:
- OU: Domain Control Validated
- CN: premium.afriregister.com
hash: ef0fd5f0
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: 13063773898816283057
validFrom: 151009205641Z
validTo: 161009205641Z
validFrom_time_t: 1444424201
validTo_time_t: 1476046601
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-136.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:premium.afriregister.com, DNS:www.premium.afriregister.com, DNS:afriregister.bi, DNS:afriregister.com, DNS:afriregister.rw, DNS:nyati.afriregister.co.ke
- subjectKeyIdentifier: AC:66:75:DF:12:4B:00:97:57:B2:E6:0E:73:9B:65:49:C8:59:4B:E8

Meta - Burundi-tourisme.com

Number of occurences: 4

Name:
Content:
Name: author
Content: nicDark
Name: viewport
Content: width=device-width, initial-scale=1.0
Name: generator
Content: WordPress 4.4.5

Server / Hosting

IP: 88.208.249.110
Latitude: 51.83
Longitude: -2.25
Country: United Kingdom
City: Gloucester

Rname

ns2.afriregister.bi
ns1.afriregister.bi
burundi-tourisme.com

Target

technical.afriregister.com

HTTP Header Response

HTTP/1.1 301 Moved Permanently Date: Wed, 05 Oct 2016 14:58:52 GMT Server: Apache X-Pingback: http://burundi-tourisme.com/xmlrpc.php Location: http://burundi-tourisme.com/ Content-Length: 0 Content-Type: text/html; charset=UTF-8 X-Cache: MISS from s_sh11 Via: 1.1 s_sh11 (squid/3.5.20) Connection: keep-alive HTTP/1.1 200 OK Date: Wed, 05 Oct 2016 14:58:53 GMT Server: Apache X-Pingback: http://burundi-tourisme.com/xmlrpc.php Link: ; rel="https://api.w.org/", ; rel=shortlink Content-Type: text/html; charset=UTF-8 X-Cache: MISS from s_sh11 Transfer-Encoding: chunked Via: 1.1 s_sh11 (squid/3.5.20) Connection: keep-alive