database / contribute

Contribute to WhatPortIs

Add a port we’re missing. 2,125 entries so far, 0 of them sent in from this page — yours would be next. Correcting an entry that already exists is a different door: open the port and edit it in place.

submit port informationreviewed, then published

required fields0/8

What it is

the three lines every reader sees first.

port number*

a number between 0 and 65535

service name*

as engineers write it, not as marketing does.

brief*

the paragraph under the heading, and the line search results show.

common usage*

categories*

How it behaves

the facts the table columns and the risk meter are built from.

transport*

tcp

udp

sctp

assignment*

in transit*

risk of exposing it*

safe0–2 safe · 3–5 caution · 6–8 risk · 9–10 critical

The write-ups

optional, markdown supported — but an entry with real technical detail is the one that publishes without waiting.

technical write-up

security write-up

references

primary sources only — an rfc, the iana registry, a cve record or the vendor's own docs. anything promotional is rejected.

You, and how you know

this is what the reviewer reads first — name the rfc, the vendor doc or the capture you're working from.

how you know*

name*

email*

only used to contact you about this submission.

every submission is checked by a model for accuracy, relevance and spam. a clean, confident result publishes straight away; anything it isn't sure about waits for a maintainer. either way you'll see its answer on this page.

0/8 required

01state what you can verify—if you inferred it from a packet capture, say so in the notes.
02link the source—an rfc number or vendor doc url beats any amount of prose.
03cite security claims—cve identifiers for vulnerabilities, not general alarm.
04expect review—every submission is read by a reviewer before it is published — a confident, well-sourced one publishes on the spot.