Loading...
Statistics
Advertisement

We do the planning. You have the fun. - What Should We Doâ„¢
www.whatshouldwedo.com/
What Should We Do is the premier leisure activity recommendation, planning and booking service. We are on a mission to provide inspired, memorable and fully ...

Whatshouldwedo.com

Advertisement
Conversion Technology Metas Server
Whatshouldwedo.com is hosted in United States / Boardman . Whatshouldwedo.com uses HTTPS protocol. Number of used technologies: 8. First technologies: CSS, Html, Html5, Number of used javascripts: 7. First javascripts: Jquery.js, Polyfill.js, Globals.js, Number of used analytics tools: 2. First analytics tools: Google Analytics, New Relic, Its server type is: nginx/1.8.0. Its CMS is: Wordpress.

Technologies in use by Whatshouldwedo.com

Technology

Number of occurences: 8
  • CSS
  • Html
  • Html5
  • Javascript
  • jQuery
  • Php
  • Pingback
  • Schema.org

Advertisement

Javascripts

Number of occurences: 7
  • jquery.js
  • polyfill.js
  • globals.js
  • libs.js
  • scripts.js
  • mailchimp.js
  • wp-embed.js

Content Management System

Number of occurences: 1
  • Wordpress

Analytics

Number of occurences: 2
  • Google Analytics
  • New Relic

Server Type

  • nginx/1.8.0

Powered by

  • PHP/5.6.17

Google Analytics ID

  • UA-77568270-1

Conversion rate optimization
visitors Clickable call number Not founded!
visitors Conversion form (contact form, subcriber) Founded!
visitors Clickable email Founded!
visitors CTA (call to action) button 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) - Whatshouldwedo.com

SSL certificate

    • name: /OU=Domain Control Validated/OU=PositiveSSL Multi-Domain/CN=www.whatshouldwedo.com
    • subject:
      • OU:
        • 0: Domain Control Validated
        • 1: PositiveSSL Multi-Domain
      • CN: www.whatshouldwedo.com
    • hash: 65d7b7ce
    • issuer:
      • C: GB
      • ST: Greater Manchester
      • L: Salford
      • O: COMODO CA Limited
      • CN: COMODO RSA Domain Validation Secure Server CA
    • version: 2
    • serialNumber: 106834023125569851431831825015541599994
    • validFrom: 160413000000Z
    • validTo: 190413235959Z
    • validFrom_time_t: 1460505600
    • validTo_time_t: 1555199999
    • extensions:
      • authorityKeyIdentifier: keyid:90:AF:6A:3A:94:5A:0B:D8:90:EA:12:56:73:DF:43:B4:3A:28:DA:E7
      • subjectKeyIdentifier: 60:60:48:B3:3B:0E:30:60:2E:7A:6A:95:D6:15:0A:54:07:D4:99:6A
      • 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:www.whatshouldwedo.com, DNS:staging.whatshouldwedo.com

Meta - Whatshouldwedo.com

Number of occurences: 18
  • Name:
    Content: https://wswd-wordpress-production.s3.amazonaws.com/content/uploads/2016/05/wswd-social-share-small.jpg
  • Name: author
    Content: What Should We Doâ„¢
  • Name: HandheldFriendly
    Content: True
  • Name: viewport
    Content: width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no
  • Name: apple-mobile-web-app-title
    Content: We do the planning. You have the fun.
  • Name: application-name
    Content: What Should We Doâ„¢
  • Name: description
    Content: What Should We Do is the premier leisure activity recommendation, planning and booking service. We are on a mission to provide inspired, memorable and fully personalized leisure experiences.
  • Name: robots
    Content: noodp
  • Name: twitter:card
    Content: summary
  • Name: twitter:description
    Content: What Should We Do is the premier leisure activity recommendation, planning and booking service. We are on a mission to provide inspired, memorable and fully personalized leisure experiences.
  • Name: twitter:title
    Content: What Should We Do - Planning for Unique and Memorable Experiences
  • Name: twitter:site
    Content: @wswd_nyc
  • Name: twitter:image
    Content: https://wswd-wordpress-production.s3.amazonaws.com/content/uploads/2016/05/wswd-social-share-small.jpg
  • Name: twitter:creator
    Content: @tester
  • Name: generator
    Content: WordPress 4.5.2
  • Name: msapplication-TileImage
    Content: https://www.whatshouldwedo.com/content/uploads/2016/01/ms-icon-144.png
  • Name: msapplication-TileColor
    Content: #282828
  • Name: theme-color
    Content: #282828

Server / Hosting

  • IP: 54.186.125.31
  • Latitude: 45.87
  • Longitude: -119.69
  • Country: United States
  • City: Boardman

Rname

  • ns01.domaincontrol.com
  • ns02.domaincontrol.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

Target

  • dns.jomax.net

HTTP Header Response

HTTP/1.1 301 Moved Permanently Server: nginx/1.8.0 Date: Mon, 05 Sep 2016 11:44:34 GMT Content-Type: text/html Content-Length: 184 Location: https://www.whatshouldwedo.com/ X-Cache: MISS from s_ub9 X-Cache-Lookup: MISS from s_ub9:80 Via: 1.1 s_ub9 (squid/3.5.20) Connection: keep-alive HTTP/1.1 200 Connection established HTTP/1.1 200 OK Server: nginx/1.8.0 Date: Mon, 05 Sep 2016 11:44:36 GMT Content-Type: text/html; charset=UTF-8 Transfer-Encoding: chunked Connection: keep-alive X-Powered-By: PHP/5.6.17 Link: ; rel="https://api.w.org/" Link: ; rel=shortlink Cache-Control: store, must-revalidate, post-check=0, pre-check=0 X-UA-Compatible: IE=edge,chrome=1

DNS

host: whatshouldwedo.com
  1. class: IN
  2. ttl: 600
  3. type: A
  4. ip: 54.186.125.31
host: whatshouldwedo.com
  1. class: IN
  2. ttl: 3600
  3. type: NS
  4. target: ns01.domaincontrol.com
host: whatshouldwedo.com
  1. class: IN
  2. ttl: 3600
  3. type: NS
  4. target: ns02.domaincontrol.com
host: whatshouldwedo.com
  1. class: IN
  2. ttl: 3600
  3. type: SOA
  4. mname: ns01.domaincontrol.com
  5. rname: dns.jomax.net
  6. serial: 2016050200
  7. refresh: 28800
  8. retry: 7200
  9. expire: 604800
  10. minimum-ttl: 600
host: whatshouldwedo.com
  1. class: IN
  2. ttl: 3600
  3. type: MX
  4. pri: 5
  5. target: alt1.aspmx.l.google.com
host: whatshouldwedo.com
  1. class: IN
  2. ttl: 3600
  3. type: MX
  4. pri: 5
  5. target: alt2.aspmx.l.google.com
host: whatshouldwedo.com
  1. class: IN
  2. ttl: 3600
  3. type: MX
  4. pri: 1
  5. target: aspmx.l.google.com
host: whatshouldwedo.com
  1. class: IN
  2. ttl: 3600
  3. type: MX
  4. pri: 10
  5. target: aspmx2.googlemail.com
host: whatshouldwedo.com
  1. class: IN
  2. ttl: 3600
  3. type: MX
  4. pri: 10
  5. target: aspmx3.googlemail.com
host: whatshouldwedo.com
  1. class: IN
  2. ttl: 3600
  3. type: TXT
  4. txt: google-site-verification=qINwow5pUwg7Rf6OrULbQLWHBu-CwdoFzkw0unNr8WU
  5. entries: Array
host: whatshouldwedo.com
  1. class: IN
  2. ttl: 3600
  3. type: TXT
  4. txt: v=spf1 include:_spf.google.com include:servers.mcsv.net ~all
  5. entries: Array

Common Typos/Mistakes

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

www.hatshouldwedo.com, www.w hatshouldwedo.com, www. hatshouldwedo.com, www.whatshouldwedo.com, www.hatshouldwedo.com, www.wdhatshouldwedo.com, www.dhatshouldwedo.com, www.wfhatshouldwedo.com, www.fhatshouldwedo.com, www.wghatshouldwedo.com, www.ghatshouldwedo.com, www.wbhatshouldwedo.com, www.bhatshouldwedo.com, www.watshouldwedo.com, www.wheatshouldwedo.com, www.weatshouldwedo.com, www.whdatshouldwedo.com, www.wdatshouldwedo.com, www.whcatshouldwedo.com, www.wcatshouldwedo.com, www.whuatshouldwedo.com, www.wuatshouldwedo.com, www.whjatshouldwedo.com, www.wjatshouldwedo.com, www.whatshouldwedo.com, www.watshouldwedo.com, www.whbatshouldwedo.com, www.wbatshouldwedo.com, www.whgatshouldwedo.com, www.wgatshouldwedo.com, www.whtshouldwedo.com, www.whaotshouldwedo.com, www.whotshouldwedo.com, www.whaptshouldwedo.com, www.whptshouldwedo.com, www.wha9tshouldwedo.com, www.wh9tshouldwedo.com, www.whatshouldwedo.com, www.whtshouldwedo.com, www.whaitshouldwedo.com, www.whitshouldwedo.com, www.whautshouldwedo.com, www.whutshouldwedo.com, www.whashouldwedo.com, www.whatqshouldwedo.com, www.whaqshouldwedo.com, www.whatashouldwedo.com, www.whaashouldwedo.com, www.what shouldwedo.com, www.wha shouldwedo.com, www.whatwshouldwedo.com, www.whawshouldwedo.com, www.whateshouldwedo.com, www.whaeshouldwedo.com, www.whatzshouldwedo.com, www.whazshouldwedo.com, www.whatxshouldwedo.com, www.whaxshouldwedo.com, www.whatcshouldwedo.com, www.whacshouldwedo.com, www.whathouldwedo.com, www.whatsehouldwedo.com, www.whatehouldwedo.com, www.whatswhouldwedo.com, www.whatwhouldwedo.com, www.whatsdhouldwedo.com, www.whatdhouldwedo.com, www.whatsxhouldwedo.com, www.whatxhouldwedo.com, www.whatsfhouldwedo.com, www.whatfhouldwedo.com, www.whatsghouldwedo.com, www.whatghouldwedo.com, www.whatsthouldwedo.com, www.whatthouldwedo.com, www.whatsouldwedo.com, www.whatsheouldwedo.com, www.whatseouldwedo.com, www.whatshdouldwedo.com, www.whatsdouldwedo.com, www.whatshcouldwedo.com, www.whatscouldwedo.com, www.whatshuouldwedo.com, www.whatsuouldwedo.com, www.whatshjouldwedo.com, www.whatsjouldwedo.com, www.whatshouldwedo.com, www.whatsouldwedo.com, www.whatshbouldwedo.com, www.whatsbouldwedo.com, www.whatshgouldwedo.com, www.whatsgouldwedo.com, www.whatshuldwedo.com, www.whatshobuldwedo.com, www.whatshbuldwedo.com, www.whatshohuldwedo.com, www.whatshhuldwedo.com, www.whatshoguldwedo.com, www.whatshguldwedo.com, www.whatshojuldwedo.com, www.whatshjuldwedo.com, www.whatshomuldwedo.com, www.whatshmuldwedo.com, www.whatsho uldwedo.com, www.whatsh uldwedo.com, www.whatshovuldwedo.com, www.whatshvuldwedo.com, www.whatsholdwedo.com, www.whatshouwldwedo.com, www.whatshowldwedo.com, www.whatshoueldwedo.com, www.whatshoeldwedo.com, www.whatshousldwedo.com, www.whatshosldwedo.com, www.whatshoualdwedo.com, www.whatshoaldwedo.com, www.whatshoudwedo.com, www.whatshouludwedo.com, www.whatshouudwedo.com, www.whatshoul8dwedo.com, www.whatshou8dwedo.com, www.whatshoul9dwedo.com, www.whatshou9dwedo.com, www.whatshouljdwedo.com, www.whatshoujdwedo.com, www.whatshoul0dwedo.com, www.whatshou0dwedo.com, www.whatshoulmdwedo.com, www.whatshoumdwedo.com, www.whatshoulpdwedo.com, www.whatshoupdwedo.com, www.whatshoulodwedo.com, www.whatshouodwedo.com, www.whatshoulwedo.com, www.whatshouldtwedo.com, www.whatshoultwedo.com, www.whatshouldgwedo.com, www.whatshoulgwedo.com, www.whatshouldbwedo.com, www.whatshoulbwedo.com, www.whatshouldxwedo.com, www.whatshoulxwedo.com, www.whatshouldswedo.com, www.whatshoulswedo.com, www.whatshouldfwedo.com, www.whatshoulfwedo.com, www.whatshouldvwedo.com, www.whatshoulvwedo.com, www.whatshouldywedo.com, www.whatshoulywedo.com, www.whatshouldzwedo.com, www.whatshoulzwedo.com, www.whatshouldawedo.com, www.whatshoulawedo.com, www.whatshouldewedo.com, www.whatshoulewedo.com, www.whatshouldrwedo.com, www.whatshoulrwedo.com, www.whatshouldedo.com, www.whatshouldw edo.com, www.whatshould edo.com, www.whatshouldwcedo.com, www.whatshouldcedo.com, www.whatshouldwedo.com, www.whatshouldedo.com, www.whatshouldwdedo.com, www.whatshoulddedo.com, www.whatshouldwfedo.com, www.whatshouldfedo.com, www.whatshouldwgedo.com, www.whatshouldgedo.com, www.whatshouldwbedo.com, www.whatshouldbedo.com,

Other websites we recently analyzed

  1. aeftalentos.com.br
    Orlando (United States) - 138.128.174.242
    Server software: Apache
    Technology: Php
    Number of meta tags: 1
  2. votingpage.com
    Switzerland - 141.8.225.124
    Server software: Apache
    Technology: Html
  3. Flådestyring - Disponering - Ruteplanlægning - Track & Trace - Locus A/S
    Denmark - 195.178.15.133
    G Analytics ID: UA-50668723-1
    Server software: Apache
    Technology: CSS, Font Awesome, Html, Html5, Iframe, Javascript, jQuery Cookie, jQuery Cycle, jQuery Fancybox, jQuery UI, Google Analytics, Google Tagmanager
    Number of Javascript: 27
    Number of meta tags: 3
  4. REAL.RU.COM
    REAL.RU.COM - ДОМЕНЫ, ХОСТИНГ, ПРОДВИЖЕНИЕ
    Roubaix (France) - 151.80.22.84
    Server software: nginx/1.8.0
    Technology: CSS, Html, Javascript, jQuery, Php
    Number of Javascript: 7
    Number of meta tags: 3
  5. www.schuppner.de
    www.schuppner.de
    Germany - 81.88.34.176
    Server software: nginx/1.10.1
    Technology: CSS, Html, Iframe, Javascript, Php
    Number of meta tags: 3
  6. CVJM Norddeutschland e.V.
    Germany - 78.46.70.169
    G Analytics ID: UA-2014880-9
    Server software: nginx
    Technology: CSS, Fancybox, Html, Javascript, Php, Google Analytics
    Number of Javascript: 4
    Number of meta tags: 1
  7. syracusebankowned.com
    Beaverton (United States) - 198.145.30.66
    Server software: Microsoft-IIS/7.5
    Technology: CSS, Html, Html5, Javascript, jQuery, Swf Object
    Number of Javascript: 5
    Number of meta tags: 3
  8. George R. Coulter Plumbing & Heating Inc. - South Jersey
    South Jersey Plumber & Heating since 1994, specializing in Hot Water Heaters, Sump Pump, Leak Repair, Bathroom & Kitchen Remodel and Water Treatment.
    Scottsdale (United States) - 23.229.226.97
    G Analytics ID: UA-58121114-1
    Server software: Apache/2.4.12
    Technology: CSS, Google Font API, Html, Iframe, Javascript, jQuery, Google Analytics, Facebook Box
    Number of Javascript: 2
    Number of meta tags: 12
  9. Excelium Informatique. Dépannage informatique à Marseille
    Dépannage informatique, assistance et maintenance informatique à Marseille
    France - 213.186.33.83
    G Analytics ID: UA-57229171-1
    Server software: Apache
    Technology: CSS, Cufon, Html, Html5, Javascript, Php, Google Analytics
    Number of Javascript: 11
    Number of meta tags: 16
  10. Robert Menger GmbH - Kellerabdichtung | Bauwerksabdichtung | Außendämmung
    Wir sind spezialisiert auf Bauwerksabdichtung, nachträgliche Innen-Abdichtung, Abdichtungsarbeiten, Außendämmung und Bautrocknung. Bei feuchten Kellern und nassen Wänden können wir Ihnen helfen!
    Höst (Germany) - 80.237.132.166
    Server software: Apache
    Technology: AJAX Libraries API, CSS, Html, Javascript
    Number of Javascript: 8
    Number of meta tags: 8

Check Other Websites