Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Some ports generate an error when browsing to them via Chrome (see this related question). Which ports are considered safe, and which are unsafe by default?

share|improve this question

3 Answers 3

up vote 29 down vote accepted

The following is a list of all of the restricted ports on Chrome:

  1,    // tcpmux
  7,    // echo
  9,    // discard
  11,   // systat
  13,   // daytime
  15,   // netstat
  17,   // qotd
  19,   // chargen
  20,   // ftp data
  21,   // ftp access
  22,   // ssh
  23,   // telnet
  25,   // smtp
  37,   // time
  42,   // name
  43,   // nicname
  53,   // domain
  77,   // priv-rjs
  79,   // finger
  87,   // ttylink
  95,   // supdup
  101,  // hostriame
  102,  // iso-tsap
  103,  // gppitnp
  104,  // acr-nema
  109,  // pop2
  110,  // pop3
  111,  // sunrpc
  113,  // auth
  115,  // sftp
  117,  // uucp-path
  119,  // nntp
  123,  // NTP
  135,  // loc-srv /epmap
  139,  // netbios
  143,  // imap2
  179,  // BGP
  389,  // ldap
  465,  // smtp+ssl
  512,  // print / exec
  513,  // login
  514,  // shell
  515,  // printer
  526,  // tempo
  530,  // courier
  531,  // chat
  532,  // netnews
  540,  // uucp
  556,  // remotefs
  563,  // nntp+ssl
  587,  // stmp?
  601,  // ??
  636,  // ldap+ssl
  993,  // ldap+ssl
  995,  // pop3+ssl
  2049, // nfs
  3659, // apple-sasl / PasswordServer
  4045, // lockd
  6000, // X11
  6665, // Alternate IRC [Apple addition]
  6666, // Alternate IRC [Apple addition]
  6667, // Standard IRC [Apple addition]
  6668, // Alternate IRC [Apple addition]
  6669, // Alternate IRC [Apple addition]

Source: Chrome source.

share|improve this answer
6  
And the Mozilla Firefox Unsafe Portslist for good measure: www-archive.mozilla.org/projects/netlib/… –  CoolAJ86 Jun 28 '12 at 21:37
    
Thanks, this was very helpful in figuring out why my ZNC server didn't appear to be working properly –  Hamy Jun 29 at 5:23

The reason it's called unsafe is not because it's unsafe to Chrome, it's because it's unsafe to those services, where an attacker may try to use Chrome as a proxy to attacking services on those ports. More explanation here:

http://jazzy.id.au/default/2012/08/23/why_does_chrome_consider_some_ports_unsafe.html

share|improve this answer

by default web services normally run on port 80 and SSL encrypted traffic runs on port 443 so these should be "safe" ports. This is typically known as "default ports" or "well known ports". "safe" seems to be a chrome-ism :)

"safe" is a bit meaningless though. If it runs on anouther port its more likely to be dodgy traffic, but just because its on port 80 dosent mean it wont install malware and etc on your pc.

share|improve this answer
    
There's no reason why traffic on non-default ports would be dodgy. For example non-default ports are used on unix machines where the web server is administered completely independently from the local administrator (unix restricts servers on ports <1024 to the system administrator). Such setups are very rare nowadays because the economic conditions of web hosting have changed, but there's nothing illegitimate about them. –  Gilles Sep 13 '10 at 18:16
1  
the above is true, but im not going to be clicking any urls that specify a port number. –  Sirex Sep 13 '10 at 22:06

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.