All-time bestest HTTP port EVAR

80   0 votes - 0 %
8080   2 votes - 33 %
443   0 votes - 0 %
8443   0 votes - 0 %
21   1 vote - 16 %
23   0 votes - 0 %
139   0 votes - 0 %
31337   0 votes - 0 %
65536   1 vote - 16 %
Any port in a (packet) storm   2 votes - 33 %
 
6 Total Votes
I spot the deliberate mistake in the poll by Herring (2.00 / 0) #1 Wed Apr 11, 2007 at 05:29:47 AM EST
I claim my five pounds. Only one of those is a standard port for HTTP.

WIPO: TCP Port 53. Without that, all else is useless.

You can't inspire people with facts
- Small Gods

heh by ucblockhead (2.00 / 0) #3 Wed Apr 11, 2007 at 07:18:35 AM EST
We had a bug the other day because a developer set the port to the zipcode (postal code for you furriners) which is "94***".
---
[ucblockhead is] useless and subhuman
[ Parent ]
TCP 53 by Merekat (2.00 / 0) #4 Wed Apr 11, 2007 at 07:55:56 AM EST
Do you have any idea how many people actually block that?

[ Parent ]
not everyone who should block udp 53 also? by LinDze (2.00 / 0) #5 Wed Apr 11, 2007 at 05:22:36 PM EST
To be fair I dont think any of our resolvers are using TCP 53. We dont want any customers trying to AXFR off our resolvers, and if the its a jumbo reply you can be sure its part of a DNS TXT DDOS 99.99% of the time.

-Lin Dze
Arbeit Macht Frei
[ Parent ]
heh by Merekat (4.00 / 1) #6 Wed Apr 11, 2007 at 11:29:43 PM EST
I operate in the type of network where that 0.01 percent is plausibly found and also primariy with authoritative rather than resolving DNS. Bit hard to provide secondary service when the primary has a silly firewall rule in the way, usually applied by someone who has no awareness of what is actually required on the network.

[ Parent ]
WIPO by Phage (2.00 / 0) #2 Wed Apr 11, 2007 at 05:42:03 AM EST
26000