495
Summary
- // typical exposure
- Anomalous (rarely legitimately open) — intecourier is an undocumented IANA name reservation with no known protocol, product, or deployment pattern and a zero-observed-open scan reading, so a responsive 495/tcp has no legitimate reason to be reachable from the public internet.
- // analyst note
- an open port 495/tcp has no documented legitimate use — investigate rather than assume routine traffic.
- // if you see it open
- No CVE or named malware family is documented for 495/tcp as of an August 2026 search. auditmypc.com's own verdict line for this port reads no virus/trojan association (a sourced negative, not derived from its template disclaimer text). With no documented protocol or product and a zero-observed-open scan reading, an open 495/tcp has no legitimate expected use and should be treated as anomalous and investigated.
About port 495/tcp.
Port 495/tcp is registered with IANA under the name intecourier, but the registration is a bare name reservation — no RFC, protocol specification, or vendor documentation describes what the service actually does — so a responsive port 495/tcp is not a recognized production service and should not be expected on the public internet.
IANA's service-names-port-numbers registry lists 495 as intecourier on both TCP and UDP, assigned to Steve Favor, with the Reference, registration-date, and modification-date fields all blank. The description field simply repeats the service name and adds no further detail about the protocol's origin or purpose.
As of an August 2026 search, no vendor manual, product page, blog post, or forum thread was found describing an application that generates traffic on port 495. Generic port-lookup aggregator sites (SpeedGuide, GRC Port Authority, AuditMyPC) all reproduce only the bare IANA label with no elaboration or first-hand traffic observation.
The repo's nmap-services extract (this site's own tooling) records an open-frequency of 0.000362 for 495/udp and exactly 0.000000 for 495/tcp — a real sampled reading, not an absence of data — meaning the assignment exists in the registry but nothing in the scan corpus shows the TCP side actually answering in the wild.
- IANA assignment
intecourier— description field identical to the service name (no further text); reference (blank — no RFC cited); assignee[Steve_Favor]; dual-registered 495/tcp + 495/udp [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry intecourier 495/tcp, the IANA Service Name and Transport Protocol Port Number Registry intecourier 495/udp- Range class
- well-known (0–1023) [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry intecourier 495/tcp
- Prevalence
- nmap-services open-frequency 495/tcp = 0.000000 (sampled, not observed open); 495/udp ≈ 0.000362 [Confirmed] — this site's own tooling
- Related ports
- none identified as a paired or companion service [Unknown]
Primary use
name reservation only; no protocol spec or documented product found using it
Other/unofficial uses
none found; port-lookup aggregator sites reproduce only the bare IANA label with no elaboration
Security implications
no CVE or named malware family documented for 495/tcp; auditmypc.com's own verdict for the port is "no virus/trojan," a sourced negative
Typically seen on
no known deployment pattern identified; treat an open 495/tcp as anomalous [Unknown]
- Analyst note
- an open port 495/tcp has no documented legitimate use — investigate rather than assume routine traffic.
About port 495/udp.
Port 495/udp is registered with IANA under the service name intecourier, but no RFC, protocol specification, or public documentation describes what the service actually does — so there is no basis for treating it as safe or expected on the public internet, and a responsive host should be investigated rather than assumed benign.
The IANA Service Name and Transport Protocol Port Number Registry lists intecourier as dual-registered on 495/tcp and 495/udp, assignee Steve Favor, with a blank reference/RFC field and no registration date recorded — a bare name-only entry rather than a documented protocol.
Beyond that formal registration, nothing about intecourier appears in RFC or vendor literature. Searches for the service name alongside "port 495" surface only generic port-lookup aggregator pages (SpeedGuide, adminsub.net, tcp-udp-ports.com) that restate the IANA listing without naming any software, client, or observed protocol behavior.
nmap-services records an open-frequency of 0.000362 for 495/udp, versus essentially 0 for 495/tcp — UDP is the transport occasionally seen open in scans, even though both transports carry the same formal registration. Given the near-total absence of documentation, that low, real-world frequency is consistent with a port that is rarely, if ever, legitimately in use.
- IANA assignment
intecourier— description "intecourier" (no expanded text given); reference (blank); assignee Steve_Favor; dual-registered 495/tcp + 495/udp [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry intecourier 495/udp- Range class
- system/well-known (0–1023) [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry intecourier 495/udp
- Prevalence
- nmap-services open-frequency 495/udp = 0.000362; 495/tcp = 0 [Confirmed] — this site's own tooling
- Related ports
- 495/tcp (same
intecourierdual registration)
Primary use
Unknown — no RFC or protocol specification found for intecourier beyond the bare IANA name registration
Other/unofficial uses
none identified; no vendor, client, or forum sighting of software using this port surfaced as of an August 2026 search [Unknown]
Security implications
no CVE tied to port 495 recorded in NVD as of Aug 2026; auditmypc.com's port-495 page returned no usable content, so no malware/trojan verdict is available from that source
Typically seen on
Unknown — no documented deployments found
- Analyst note
- A responsive 495/udp cannot be explained by any documented protocol or known software; because prevalence is near-zero, treat unexpected traffic here as anomalous and worth investigating rather than assume legitimate use.
Service assignments.
| Name | Protocol | Description | Open frequency |
|---|---|---|---|
| intecourier | UDP | — | 0.04% |
| intecourier | TCP | — | 0.00% |
Service assignments from the IANA Service Name and Transport Protocol Port Number Registry, with open-frequency data from nmap-services.