Whattodotomorrow.com

Whattodotomorrow.com is hosted in United States / San Francisco . Whattodotomorrow.com uses HTTPS protocol. Number of used technologies: 9. First technologies: CSS, Google Font API, Gravatar, Number of used javascripts: 6. First javascripts: Gprofiles.js, Wpgroho.js, Jquery.autoresize.js, Number of used analytics tools: 1. First analytics tools: ComScore, Number of used plugins, modules: 0. Its server type is: nginx. Its CMS is: Wordpress.

Technologies in use by Whattodotomorrow.com

Technology

Number of occurences: 9

CSS
Google Font API
Gravatar
Html
Html5
Javascript
Php
Pingback
Shortcodes

Javascripts

Number of occurences: 6

gprofiles.js
wpgroho.js
jquery.autoresize.js
script.js
widgets.js
w.js

Content Management System

Number of occurences: 1

Wordpress

Analytics

Number of occurences: 1

comScore

Server Type

nginx

Social

Number of occurences: 1

Twitter Button

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

SSL certificate

name: /CN=tls.automattic.com
subject:
- CN: tls.automattic.com
hash: 6338c477
issuer:
- C: US
- O: Let's Encrypt
- CN: Let's Encrypt Authority X3
version: 2
serialNumber: 327887929292381445689299903257194850772573
validFrom: 160404130800Z
validTo: 160703130800Z
validFrom_time_t: 1459775280
validTo_time_t: 1467551280
extensions:
- keyUsage: Digital Signature, Key Encipherment
- extendedKeyUsage: TLS Web Server Authentication, TLS Web Client Authentication
- basicConstraints: CA:FALSE
- subjectKeyIdentifier: B1:77:95:4C:E6:A8:2B:5C:E5:F7:24:E6:52:1F:95:C8:0C:CC:75:B6
- authorityKeyIdentifier: keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
- authorityInfoAccess: OCSP - URI:http://ocsp.int-x3.letsencrypt.org/ CA Issuers - URI:http://cert.int-x3.letsencrypt.org/
- subjectAltName: DNS:tls.automattic.com, DNS:whatthehallelujah.com, DNS:whatthehealthblog.com, DNS:whattheheartholds.com, DNS:whattheheckbec.com, DNS:whattheheckishezbollah.com, DNS:whattheheckofthat.com, DNS:whattheheckvideo.com, DNS:whatthehellhappenedblog.com, DNS:whatthehellisthis.net, DNS:whatthehellshouldiwatchonnetflixuk.com, DNS:whatthehelsinki.com, DNS:whattheinterrobang.com, DNS:whatthekel.me, DNS:whatthekippy.com, DNS:whattheladyloves.com, DNS:whatthelaw.org, DNS:whatthemom.com, DNS:whatthepenisdid.com, DNS:whatthesaintsdidnext.com, DNS:whattheschnell.com, DNS:whattheshelll.com, DNS:whattheshoot.nl, DNS:whattheteacherwears.com, DNS:whatthetravelersaw.me, DNS:whatthetwenties.com, DNS:whatthewhothehowthe.com, DNS:whattheworldcallsromance.com, DNS:whattheworldtaughtme.com, DNS:whatthey.com, DNS:whattheyarenttellingyou.net, DNS:whattheysayatcda.com, DNS:whatthousandsknowandmillionsdont.com, DNS:whattinaloves.com, DNS:whattocooktonight.com, DNS:whattododublin.org, DNS:whattodoinbarcelona.net, DNS:whattodointhegardenhood.com, DNS:whattodotomorrow.com, DNS:whattodowhenitrains.com, DNS:whattodowhensomeonehasdied.com, DNS:whattodowitha22.com, DNS:whattoeatamsterdam.com, DNS:whattoeatdc.com, DNS:whattoeatwheninrome.com, DNS:whattoexpectwhenyouarenotexpectingblog.com, DNS:whattohavefordinnertonight.com, DNS:whattoreadtoyourkids.com, DNS:whattoreadyourkids.com, DNS:whattowatchnext.co, DNS:whatupplayer.com
- certificatePolicies: Policy: 2.23.140.1.2.1 Policy: 1.3.6.1.4.1.44947.1.1.1 CPS: http://cps.letsencrypt.org User Notice: Explicit Text: This Certificate may only be relied upon by Relying Parties and only in accordance with the Certificate Policy found at https://letsencrypt.org/repository/

Meta - Whattodotomorrow.com

Number of occurences: 8

Name:
Content: en_US
Name: viewport
Content: width=device-width, initial-scale=1
Name: generator
Content: WordPress.com
Name: twitter:site
Content: @wordpressdotcom
Name: application-name
Content: What To Do Tomorrow...
Name: msapplication-window
Content: width=device-width;height=device-height
Name: msapplication-task
Content: name=WordPress.com Forums;action-uri=http://forums.wordpress.com/;icon-uri=https://s2.wp.com/i/favicon.ico
Name: title
Content: What To Do Tomorrow... on WordPress.com

Server / Hosting

IP: 192.0.78.25
Latitude: 37.75
Longitude: -122.42
Country: United States
City: San Francisco

Rname

ns1.wordpress.com
ns3.wordpress.com
ns2.wordpress.com
smtp.secureserver.net
mailstore1.secureserver.net

Target

hostmaster.wordpress.com

HTTP Header Response

HTTP/1.1 301 Moved Permanently Server: nginx Date: Tue, 31 May 2016 01:37:41 GMT Content-Type: text/html Content-Length: 178 Location: https://whattodotomorrow.com/ X-ac: 3.fra _dca X-Cache: MISS from s_xt13 X-Cache-Lookup: MISS from s_xt13:80 Via: 1.1 s_xt13 (squid/3.5.13) Connection: keep-alive HTTP/1.1 200 Connection established HTTP/1.1 200 OK Server: nginx Date: Tue, 31 May 2016 01:37:42 GMT Content-Type: text/html; charset=UTF-8 Connection: keep-alive Strict-Transport-Security: max-age=86400 Vary: Accept-Encoding Vary: Cookie X-hacker: If you're reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header. Link: ; rel=shortlink X-ac: 3.fra _dca