The Broadband Guide
search advanced
 forgot password?

Port 1330 Details

known port assignments and vulnerabilities
threat/application/port search:
Port(s) Protocol Service Details Source
1330 tcp,udp streetperfect StreetPerfect IANA
1 records found
jump to:
previous next

« back to SG Ports

External Resources
SANS Internet Storm Center: port 1330

Well Known Ports: 0 through 1023.
Registered Ports: 1024 through 49151.
Dynamic/Private : 49152 through 65535.

TCP ports use the Transmission Control Protocol. TCP is the most commonly used protocol on the Internet and any TCP/IP network. Whereas the IP protocol deals only with packets, TCP enables two hosts to establish a connection and exchange streams of data. TCP guarantees delivery of data and that packets will be delivered in the same order in which they were sent. Guaranteed communication/delivery is the key difference between TCP and UDP.

UDP ports use the Datagram Protocol, a communications protocol for the Internet network, transport, and session layers. Like TCP (Transmission Control Protocol), UDP is used with IP (the Internet Protocol) and makes possible the transmission of datagrams from one computer to applications on another computer, but unlike TCP, UDP is connectionless and does not guarantee reliable communication; it's up to the application that received the message to process any errors and verify correct delivery. UDP is often used with time-sensitive applications, such as audio/video streaming, where dropping some packets is preferable to waiting for delayed data.

Please use the "Add Comment" button below to provide additional information or comments about port 1330.
  User Reviews/Comments:
by anonymous - 2011-06-21 14:10
StreetPerfect is used to check postal codes with addresses, for example if the client gives the postal code, the server will return the address, not sure if you give it the address and it will return the postal code or not. Looks like we are using either StreetPerfect 9 or 6. Hard to tell. Unfortunately, the network traffic isn't very network friendly. In the first frame to the server there is a bunch of header info and then a postal code and then another 45 frames of spaces, giving a total of almost 70k from the client to the server, not including return ACK's. The response is just as bad with 46 frames, in the same case, 45 of those frames are spaces and pushing almost another 70k without return ACK's. So, that is almost 140k of data for something that could likely be done with a few frames in each direction. This complete transaction, including the initial TCP setup, the ACK's and the FIN/ACK sequence at the end, it consumed a total of over 142k.

I suspect that when this protocol was written/designed for this application network friendliness wasn't at the top of their list. I think they could likely form the header to include the number of records in the data, in both directions. Other then StreetPerfect having alot of overhead as I mentioned above, it does seem to work very well. I gave this app a Poor rating because of its extreme lack of network friendliness.
Print this document top
News Glossary of Terms FAQs Polls Cool Links SpeedGuide Teams SG Premium Services SG Gear Store
Registry Tweaks Broadband Tools Downloads/Patches Broadband Hardware SG Ports Database Security Default Passwords User Stories
Broadband Routers Wireless Firewalls / VPNs Software Hardware User Reviews
Broadband Security Editorials General User Articles Quick Reference
Broadband Forums General Discussions
Advertising Awards Link to us Server Statistics Helping SG About