Port Database Request/Suggestion

[OlivrClothesoff]

Loving your Port Database. I wasn't sure where to post this.

Is there anyway the data can be put into a table format? Searching and clicking on each link can be tedious. Having all the ports in a table would benefit Data Analytics and Reporting as well.

Thanks!

[Philip]

Thanks for the good comments about the database Oliver, it has been compiled over many years of research, adding information, including other available sources and user contributions as well, making it one of the most complete ports databases online.

There is a table format for some subsets of the ports..
Commonly open ports: https://www.speedguide.net/ports_common.php
Vulnerable ports: https://www.speedguide.net/ports_sg.php
Is something like that what you had in mind?

We don't want to make the full database available in easily downloadable format, it would just give it away to all kinds of questionable/stale websites around the web that provide no original work, we prefer to keep it in house and updated regularly. It is also huge (nearly 20,000 rows when we include other sources like IANA, Sans, Nmap, etc.), so not suitable for web viewing as a whole.

The current setup is easily searchable by port (lower "jump to" combo box), provides links to related ports where applicable, etc. If you'd like us to improve the UI for ease of use we would definitely consider it, short of making the whole database easily downloadable.

Thanks for understanding.

[OlivrClothesoff]

Thanks for the good comments about the database Oliver, it has been compiled over many years of research, adding information, including other available sources and user contributions as well, making it one of the most complete ports databases online.

There is a table format for some subsets of the ports..
Commonly open ports: https://www.speedguide.net/ports_common.php
Vulnerable ports: https://www.speedguide.net/ports_sg.php
Is something like that what you had in mind?

We don't want to make the full database available in easily downloadable format, it would just give it away to all kinds of questionable/stale websites around the web that provide no original work, we prefer to keep it in house and updated regularly. It is also huge (nearly 20,000 rows when we include other sources like IANA, Sans, Nmap, etc.), so not suitable for web viewing as a whole.

The current setup is easily searchable by port (lower "jump to" combo box), provides links to related ports where applicable, etc. If you'd like us to improve the UI for ease of use we would definitely consider it, short of making the whole database easily downloadable.

Thanks for understanding.

Yes, that's understandable. Those two tables were sort of what I had in mind. I think a good example would be a Wiki page where most data are put into a table format. I could use a tool such as PowerBI, Tableau, Splunk, etc to extract the data from the Site and use it for Reporting/Analytics. Your data will still be kept in house and updated regularly but would be used by tools such as those mentioned to essentially import the data.

Here is an example using PowerBI: https://docs.microsoft.com/en-us/pow...connect-to-web

Let me know if that makes sense.

Thanks!

[OlivrClothesoff]

Any feedback on this?

[Philip]

We haven't decided how to improve on this yet. Vulnerable ports are already available in table format.

We are not ready to make an exportable format for the full data, and even if we do it would have to be with some type of licensing terms for commercial use.

[ibmsecurity]

What about a REST API so we can query ports and know dynamically for what it is used (normal usage + malware for example). Ease of licensing with idk 10$ for 1000 credits and 1 credit for 1 query or something.

[Philip]

A REST API may work, thank you for the constructive suggestion.