whatportis.com
suggest an edit →

Port 702IRIS

IRIS (Internet Registry Information Service) over BEEP is a protocol designed to facilitate the distributed query and management of Internet registry data. It operates over the Blocks Extensible Exchange Protocol (BEEP), providing structured, standardized access to network and user information, supporting automation, and interoperability between network registries. This service aids organizations and ISPs in managing IP allocations, domain registrations, and maintaining registry accuracy..

inNetwork Services
transport
tcp

single transport

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
4/10

caution

lookups
6,192

rank 808 of 993 · top 81%

Technical Details

what runs on :702

IRIS (Internet Registry Information Service), defined by RFC 3981 and operating over BEEP as per RFC 3983, is aimed at delivering a successor to legacy WHOIS services. BEEP (Blocks Extensible Exchange Protocol) is a generic application protocol framework designed to simplify the development of new protocols. By leveraging BEEP, IRIS provides extensible, flexible mechanisms to manage and query registry information through a structured XML format.

The protocol supports a variety of operations around Internet resource data, including querying domain names, IP addresses, autonomous systems, and other registry objects. Its use of structured XML schemas allows for more precise, machine-readable data exchanges compared to the unstructured WHOIS protocol. IRIS supports internationalization and introduces authentication capabilities natively, enhancing the ability to regulate data visibility and enforce registry policies.

Operational deployment of IRIS over port 702 enables registries, ISPs, and network operators to automate queries, synchronize data updates, and develop interoperable tools that facilitate the maintenance of accurate and accessible Internet resource records across distributed environments.

Security Information

exposure of :702

risk score

4/ 10caution

worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.

network services averages 3.9 across 604 ports — this one sits 0.1 above.

in transit

cleartext

credentials and payloads are readable by anyone on path

assignment

official

registered with iana for this service — scanners fingerprint it by number

reachable over

tcp

every listening transport is another surface to filter at the edge

security overview

Common Vulnerabilities:

  • Unauthorized disclosure of sensitive registry data due to improper access controls
  • Exploitation of the service as an information source for reconnaissance in cyberattacks
  • Weak authentication implementations potentially allowing spoofing or unauthorized data alteration if authentication features are not correctly enforced
  • Exploitation of underlying BEEP protocol weaknesses, such as improper framing or resource exhaustion attacks

Common Mitigations:

  • Enforce strong authentication and authorization policies on all IRIS queries
  • Restrict registry data access to authorized users and employ role-based controls
  • Regularly monitor and audit access logs for suspicious activity
  • Implement transport layer encryption (e.g., TLS over BEEP session) to protect data integrity and confidentiality, even if the default is unencrypted
  • Patch and update IRIS/BEEP implementations to address known vulnerabilities and follow secure coding best practices
  • Rate-limit queries to prevent abuse or denial-of-service conditions

Related Ports

all 604 in network services →

the 8 most looked-up other ports in network services — 604 ports carry that label.

portservicerisk
:9080Groove RPCcaution
:6543Jetnetcaution
:5938TeamViewercaution
:8291Winbox MikroTik Admincaution
:3233WhiskerControl Protocolcaution
:3268Microsoft Global Catalog (GC)caution
:135Microsoft EPMAPcaution
:3128Tatsoft Default HTTP Proxycaution

risk mix of the 8 listed

  • caution100%

0 of 8 encrypted