whatportis.com
suggest an edit →

Port 700Extensible Provisioning Protocol

Extensible Provisioning Protocol (EPP) is a flexible application layer protocol designed for reliable and secure communications between Internet domain name registrars and registries. Standardized in RFC 5734, it facilitates operations such as domain registration, management, and transfer. EPP primarily uses XML over TCP for structured data exchange and has become the industry standard for automated provisioning within domain name systems..

inWeb ServicesNetwork Services
transport
tcp

single transport

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
4/10

caution

lookups
6,419

rank 789 of 993 · top 79%

Technical Details

what runs on :700

  • Overview: Extensible Provisioning Protocol (EPP) operates at the application layer, utilizing XML messages transmitted over TCP connections—typically on port 700. It provides a standardized, extensible framework that enables registrars to automate interactions with domain registries for domain name management tasks.

  • Protocol Specifications: EPP defines command and response formats encoded in XML compliant with RFC 5734. It supports fundamental provisioning operations such as register, renew, transfer, delete, and update of domain objects, as well as management of contact and host objects. TCP is preferred due to its reliability, ensuring transactional integrity during communications.

  • Extensibility: The protocol includes extension mechanisms that allow registries to introduce custom commands without breaking compatibility, making it adaptable for diverse registry needs. While EPP itself does not enforce encryption or authentication, it is typically implemented over secure channels like TLS to safeguard data during transmission.

Security Information

exposure of :700

risk score

4/ 10caution

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

web services averages 3.9 across 112 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:

    • Cleartext Transmission: Without encryption, EPP sessions can be susceptible to eavesdropping, allowing attackers to intercept sensitive registrar data.
    • Brute-Force Attacks: If authentication is weak, attackers could gain unauthorized access to registry systems.
    • Replay Attacks: Attackers might capture and replay legitimate EPP commands to manipulate domain records.

  • Mitigations:

    • Use of TLS: Encrypt all EPP traffic via TLS, as recommended in RFC 5734, to prevent interception and tampering.
    • Strong Authentication: Implement multi-factor or certificate-based authentication schemes.
    • Session Controls: Employ mechanisms to detect replayed or duplicated commands.
    • Rate Limiting and Monitoring: Monitor for unusual activity and limit the rate of connection attempts to prevent brute-force attempts.
    • Access Controls: Restrict access to whitelisted IPs and enforce role-based permissions within the EPP system.

Related Ports

all 112 in web services →

the 8 most looked-up other ports in web services — 112 ports carry that label.

portservicerisk
:8888Sun Answerbook & Alt HTTPcaution
:8000Intel Remote Desktop / Alternate HTTP Portsafe
:8888NewsEDGEcaution
:8888HTTP Alternative Portcaution
:8888GNUmp3d Streaming HTTPcaution
:9080Groove RPCcaution
:8881Atlasz Secure Servercaution
:80HTTPcaution

risk mix of the 8 listed

  • safe13%
  • caution88%

0 of 8 encrypted