Tuesday, March 7, 2017

MVPS HOSTS File Update March 06-2017

The MVPS HOSTS file was recently updated [March 06-2017]
http://winhelp2002.mvps.org/hosts.htm

Note: Windows 10 users ... the HOSTS file installs with no issues ...

Download: hosts.zip (131 kb)
http://winhelp2002.mvps.org/hosts.zip

How To: Download and Extract the HOSTS file
http://winhelp2002.mvps.org/hosts2.htm

HOSTS File - Frequently Asked Questions
http://winhelp2002.mvps.org/hostsfaq.htm

Note: the "text" version (492 kb) makes a great resource for determining possible unwanted connections ...
http://winhelp2002.mvps.org/hosts.txt

Get notified when the MVPS HOSTS file is updated
http://winhelp2002.mvps.org/updates.htm

If you find the MVPS HOSTS file useful ... please consider a donation ...
http://winhelp2002.mvps.org/hosts.htm#donation

3 comments:

  1. RFC 952 states that the host file entries must be ASCII strings, which implies that the entire host file should be ASCII-encoded. The most recent version of your hosts file had two non-printing, non-ASCII characters (U+00A0 NO-BREAK SPACES) in the comment on line 10860, which will cause problems on some systems:

    # [Online S.a.s][AS12876][163.172.0.0-163.172.255.255]

    Could you please remove them, and ensure that your hosts files are ASCII-encoded in the future? (When internationalized domain names are required, presumably their Punycode conversions [ASCII A-labels, as specified in RFCs 3492 and 5891] could be used, right?) I'm told that recent versions of Microsoft Windows accepts "only ANSI and UTF-8 without BOM" encoded host files (although I have not verified this). Your hosts file are also being used on other operating systems, and they may be even more restrictive.

    Thank you for your work in maintaining this host file.

    ReplyDelete
    Replies
    1. Actually, the characters are not non-printing -- I meant to write that they are whitespace.

      Delete
  2. Thanks for the heads-up ... not sure how that happened. It has been corrected ...

    ReplyDelete