Improve the search presence of your site

This post follows step by step adding your site to Google Search Console (formerly Google Webmaster Tools).

I verified my site using the Google Analytics method.

Step 1: Add all your website versions

It seems unnecessary, but they are serious about adding all variations (http/https www/non-www) and it is is required in order to set a preferred (www/non-www) version.

I added:

  • http://scottontechnology.com/
  • https://scottontechnology.com/
  • https://www.scottontechnology.com/
  • http://www.scottontechnology.com/

Step 2: Select your preferred version

I set the preferred version to

  • Display URLs as scottontechnology.com (the https:// version)

20150531-google-search-console-step2-display-urls-as-scottontechnology.com

Step 3: Select target country

  • Skipped this step

Step 4: Share access with co-workers

  • Skipped this step

Step 5: Submit a sitemap file

20150528-step-5-add-test-sitemap
Starting out: No sitemaps found for this site
20150528-step-5-1-add-test-sitemap
I tested the sitemap first
20150528-step-5-2-add-test-sitemap
Results of the sitemap test
20150528-step-5-3-add-test-sitemap
Next I submitted the sitemap
20150528-step-5-4-add-test-sitemap
After refreshing the page it shows the sitemap was processed but no other information for Issues, Items, Submitted, or Indexed
20150529-sitemaps
1 day later, on 5/29/15, 256 pages were submitted with 111 indexed and 65 images submitted with zero indexed

The worst SSL Labs Test Report

SSL Report: hmctsformfinder.justice.gov.uk (212.137.36.113)
Assessed on: Sun, 31 May 2015 05:16:06 UTC
SSL Report v1.18.1

20150531-ssllabs.com-f-rating-hmctsformfinder.justice.gov.uk

Run the test yourself: https://www.ssllabs.com/ssltest/analyze.html?d=hmctsformfinder.justice.gov.uk

 

(h/t) Paul Moore @Paul_Reviews on Twitter https://twitter.com/Paul_Reviews/status/604299891607621632

How to: Secure Chrome against Logjam

Update: Chrome 45 was released on 9/1/15 with a fix for the “logjam” vulnerability.  Use Chrome 45 or newer

Disable the following cipher suites

  • (0xcc15) TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256
  • (0xcc9e) TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
  • (0x0039) TLS_DHE_RSA_WITH_AES_256_CBC_SHA
  • (0x0033) TLS_DHE_RSA_WITH_AES_128_CBC_SHA

Until the Chrome 45 update, the easiest by far is to

Step 1:
Modify an existing (or create) a shortcut to Chrome.  Right click on the shortcut and select Properties

Step 2:
Add the following to the application Target:

It should look like this:
(Note: Target field is long and is split into two screenshots)

20150530-secure-chrome-logjam-step2-1

20150530-secure-chrome-logjam-step2

Step 3:
Click Apply or OK to save

Step 4:
Close all Chrome browser windows

Step 5:
Use the shortcut you just modified to re-open Chrome and verify these cipher suites have been disabled

Quick: https://weakdh.org/

20150605-secure-chrome-logjam-weakdh.org-step5

Detailed: https://www.ssllabs.com/ssltest/viewMyClient.html

(h/t) @eckes on twitter: https://twitter.com/eckes/status/604090760032559104

 

Reference

The fix is “on track to be included in Chrome 45”

 

Downloads

I zipped the Logjam safe shortcut from this tutorial.

If you used the standard installer your application path is %UserProfile%\AppData\Local\Google\Chrome\Application\chrome.exe

Download “Windows Default 32-bit Chrome (Logjam Safe) Shortcut” Google-Chrome-Logjam-Safe.zip – Downloaded 50 times – 1 KB

Google Chrome (Logjam Safe).lnk

  • MD5: 32D2342D138B66A3F458D66842038CA5
  • SHA1: CAB26DCFEF880D5D7422633A2732770CB6B0BB17

If you used the “offline installer” Chrome installs to “C:\Program Files (x86)\Google\Chrome\Application\chrome.exe”

Download “"Program Files (x86)" 32-bit Chrome (Logjam Safe) Shortcut” Chrome (Logjam Safe).lnk.zip – Downloaded 36 times – 1 KB

Chrome (Logjam Safe).lnk

  • MD5: C689CABE8887CD8187CAAFA395DBCF2B
  • SHA1: EE2E1D54BA3DF586406BB13CA3E35E41A130745B

Original content and screenshots on this page are licensed under a Creative Commons Attribution 3.0 License (http://creativecommons.org/licenses/by/3.0/us/)

How to: Secure Firefox against Logjam

Update: Firefox 39 was released on 7/2/15 with a fix for the logjam vulnerability (advisory on “logjam”). Use Firefox 39 or newer

Disable the following:

  • security.ssl3.dhe_rsa_aes_128_sha
  • security.ssl3.dhe_rsa_aes_256_sha

following are step by step instructions

How to: Secure Firefox against Logjam (until Firefox 39 is released)

Step 1:
Type “about:config” in the navigation bar

20150530-secure-firefox-logjam-step1

 

Step 2:
Continue through the warning screen by clicking “I’ll be careful, I promise!”

20150530-secure-firefox-logjam-step2

 

Step 3:
Search for “ssl3”

20150530-secure-firefox-logjam-step3

 

Step 4:
Disable the following (by double clicking or right clicking then “Toggle”)  Changes are saved automatically

  • security.ssl3.dhe_rsa_aes_128_sha
  • security.ssl3.dhe_rsa_aes_256_sha

20150530-secure-firefox-logjam-step4

 

Step 5:
Verify these cipher suites have been disabled

Quick: https://weakdh.org/

Before

20150530-secure-firefox-logjam-step0

After

20150530-secure-firefox-logjam-step5

 

Detailed: https://www.ssllabs.com/ssltest/viewMyClient.html

20150530-secure-firefox-logjam-ssltest-before

20150530-secure-firefox-logjam-ssltest-after

 

(h/t) http://techdows.com/2015/05/how-to-make-firefox-browser-safe-against-logjam-attack.html

Additional Information

Mozilla released (5/22/15) an add-on that changes these settings – https://addons.mozilla.org/mk/firefox/addon/disable-dhe/

Per Mozilla – Firefox 39 will include changes that will increase the minimum strength of keys to 1024 bits.

20150530-firefox-39

 

Content from Qualys licensed under a Creative Commons Attribution 3.0 License (http://creativecommons.org/licenses/by/3.0/us/).   Arrows and Before and After tags were added to screenshots of the original content.

Original content and screenshots on this page are licensed under a Creative Commons Attribution 3.0 License (http://creativecommons.org/licenses/by/3.0/us/)

Daily Links Friday 5/29/15

Daily Links Friday 5/29/15

Common crawlers or bots

Archive.org (Wayback Machine) user-agent:

  • archive.org_bot

Bing user-agents:

  • Bingbot
  • MSNBot
  • MSNBot-Media
  • AdIdxBot
  • BingPreview

Google user-agents:

  • Googlebot
  • Googlebot-News
  • Googlebot-Image
  • Googlebot-Video
  • Googlebot-Mobile
  • Mediapartners-Google
  • Adsbot-Google

References:

Archive.org – https://archive.org/details/archive.org_bot

Bing – http://www.bing.com/webmaster/help/which-crawlers-does-bing-use-8c184ec0

Google – from the Google Search Console robots.txt Tester20150528-googlebot

Listing of all Google bots20150528-all-google-bots