Destinationweddingrivieramaya.com

Destinationweddingrivieramaya.com is hosted in United States / Ashburn . Destinationweddingrivieramaya.com uses HTTPS protocol. Number of used technologies: 5. First technologies: CSS, Google Font API, Html, Number of used javascripts: 8. First javascripts: Jquery-latest.min.js, Customscript.js, Jquery.nivo.slider.pack.js, Number of used analytics tools: 0. Number of used plugins, modules: 0. Its server type is: openresty/1.7.4.1.

Technologies in use by Destinationweddingrivieramaya.com

Technology

Number of occurences: 5

CSS
Google Font API
Html
Javascript
jQuery

Javascripts

Number of occurences: 8

jquery-latest.min.js
customscript.js
jquery.nivo.slider.pack.js
Java_Box.js
Java_DynMenusSelectedCSS.js
ValidationFunctions.js
Java_DatePicker.js

Server Type

openresty/1.7.4.1

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

SSL certificate

name: /C=US/ST=California/L=San Jose/O=Adobe Systems Incorporated/CN=*.worldsecuresystems.com
subject:
- C: US
- ST: California
- L: San Jose
- O: Adobe Systems Incorporated
- CN: *.worldsecuresystems.com
hash: 7691ae77
issuer:
- C: US
- O: DigiCert Inc
- CN: DigiCert SHA2 Secure Server CA
version: 2
serialNumber: 3754971448869226611842954453383721446
validFrom: 160609000000Z
validTo: 170809120000Z
validFrom_time_t: 1465430400
validTo_time_t: 1502280000
extensions:
- authorityKeyIdentifier: keyid:0F:80:61:1C:82:31:61:D5:2F:28:E7:8D:46:38:B4:2C:E1:C6:D9:E2
- subjectKeyIdentifier: B2:07:F4:3F:79:6C:5C:D2:9B:B9:1D:03:F9:74:D9:EF:F4:D5:6D:95
- subjectAltName: DNS:*.worldsecuresystems.com, DNS:worldsecuresystems.com
- keyUsage: Digital Signature, Key Encipherment
- extendedKeyUsage: TLS Web Server Authentication, TLS Web Client Authentication
- crlDistributionPoints: Full Name: URI:http://crl3.digicert.com/ssca-sha2-g5.crl Full Name: URI:http://crl4.digicert.com/ssca-sha2-g5.crl
- certificatePolicies: Policy: 2.16.840.1.114412.1.1 CPS: https://www.digicert.com/CPS Policy: 2.23.140.1.2.2
- authorityInfoAccess: OCSP - URI:http://ocsp.digicert.com CA Issuers - URI:http://cacerts.digicert.com/DigiCertSHA2SecureServerCA.crt
- basicConstraints: CA:FALSE

Meta - Destinationweddingrivieramaya.com

Number of occurences: 2

Name:
Content: text/html; charset=utf-8
Name: viewport
Content: width=device-width, initial-scale=1, maximum-scale=1

Server / Hosting

IP: 54.236.189.61
Latitude: 39.03
Longitude: -77.48
Country: United States
City: Ashburn

Rname

ns01.brideappeal.com
ns02.brideappeal.com
ns03.brideappeal.com
mx.destinationweddingrivieramaya.com.cust.b.hostedemail.com

Target

admin.destinationweddingrivieramaya.com

HTTP Header Response

HTTP/1.1 200 OK Server: openresty/1.7.4.1 Date: Sun, 24 Jul 2016 16:00:50 GMT Content-Type: text/html; charset=utf-8 Content-Length: 9279 Cache-Control: private Set-Cookie: visitorDeviceClass=desktop; path=/ Set-Cookie: ASP.NET_SessionId=wisj1spacef4lfpghrhkpsds; path=/; HttpOnly X-FullPageCaching: Served Set-Cookie: visitorDeviceClass=desktop; path=/ Set-Cookie: ASP.NET_SessionId=wisj1spacef4lfpghrhkpsds; path=/; HttpOnly Set-Cookie: ANONID_FS1439948=24.07.2016 16:00:50.799; domain=destinationweddingrivieramaya.com; expires=Mon, 24-Jul-2017 16:00:50 GMT; path=/ Set-Cookie: ANONID1439948=d32d60cd-afd2-49eb-a03d-cf92cc3aaee6; domain=destinationweddingrivieramaya.com; expires=Mon, 24-Jul-2017 16:00:50 GMT; path=/ Set-Cookie: VISID1439948=53940ea1-54fc-45fb-b976-888af1782bbb#www.destinationweddingrivieramaya.com#24.07.2016 16:00:50.799; domain=destinationweddingrivieramaya.com; expires=Sun, 24-Jul-2016 16:30:50 GMT; path=/ X-Cache: MISS from s_sr109 X-Cache-Lookup: MISS from s_sr109:80 Via: 1.1 s_sr109 (squid/3.5.14) Connection: keep-alive