Table of Contents

Telenegar Port Check Tool

The Telenegar Port Check Tool is a network security utility designed to test whether specific TCP ports are open, filtered, or closed on a target IPv4 address.

It helps systems administrators, network engineers, and security teams verify server connectivity, audit firewall configurations, confirm service accessibility, and detect unauthorized open ports.


Tool Features & Input Parameters

The Port Check interface provides organized category presets and probe selection options to streamline service auditing:

Parameter Description Options / Examples
TARGET IPV4 ADDRESS The target IPv4 address to scan for open TCP ports. e.g., 216.239.38.120
SELECT A PORT TO CHECK Grouped service categories containing standard port presets. Categories: Web, Mail, Remote Access, FTP, DNS, Database, Oracle, Other
PROBE The remote geographical vantage point or probe location executing the TCP connection attempt. Falkenstein, Germany — Hetzner Online GmbH, domestic Iran probes, regional cloud nodes

Supported Port Presets & Service Categories

The tool categorizes standard network services into collapsible presets for quick selection:

Category Preset Option Name Port Description / Protocol
Web HTTP `80` Unencrypted Web Traffic
HTTPS `443` Encrypted Secure Web Traffic (TLS/SSL)
HTTP Alt `8080` Alternate HTTP / Proxy Port
HTTPS Alt `8443` Alternate HTTPS / Secure Web Portal
Mail SMTP `25` Simple Mail Transfer Protocol (MTA-to-MTA)
SMTP SSL `465` Implicit TLS SMTP
SMTP Submission `587` Client Email Submission (STARTTLS)
POP3 `110` Post Office Protocol v3
POP3 SSL `995` Encrypted POP3 over TLS/SSL
IMAP `143` Internet Message Access Protocol
IMAP SSL `993` Encrypted IMAP over TLS/SSL
Remote Access SSH `22` Secure Shell
Telnet `23` Unencrypted Remote Terminal
RDP `3389` Microsoft Remote Desktop Protocol
VNC `5900` Virtual Network Computing Remote Desktop
FTP FTP Data `20` File Transfer Protocol Data Channel
FTP `21` File Transfer Protocol Control Channel
FTPS `990` Implicit FTP over SSL
DNS DNS `53` Domain Name System (TCP Queries / Zone Transfers)
Database MySQL `3306` MySQL / MariaDB Database Server
MSSQL `1433` Microsoft SQL Server
PostgreSQL `5432` PostgreSQL Database Server
Redis `6379` Redis In-Memory Data Store
MongoDB `27017` MongoDB NoSQL Database
Oracle Oracle DB `1521` Oracle Database TNS Listener
Oracle DB SSL `2484` Encrypted Oracle Database TCPS Listener
WebLogic HTTP `7001` Oracle WebLogic Server HTTP
WebLogic HTTPS `7002` Oracle WebLogic Server HTTPS
WebLogic Admin `9001` Oracle WebLogic Server Administration Console
WebLogic Cluster `5556` Oracle WebLogic Server Node Manager / Cluster
Other LDAP `389` Lightweight Directory Access Protocol
LDAPS `636` Encrypted LDAP over SSL/TLS
NTP `123` Network Time Protocol

How to Perform a Port Check

# **Enter Target IPv4 Address:** Type the destination IPv4 address into the **TARGET IPV4 ADDRESS** field (e.g., ''216.239.38.120'').
# **Select Target Port:** Click on a service category (e.g., **Mail**, **Oracle**, or **Other**) to expand the list, then select the radio button for the desired service preset.
# **Select Probe Location:** Choose a remote probe from the **PROBE** dropdown menu (e.g., ''Falkenstein, Germany — Hetzner Online GmbH'') to test reachability from that location.
# **Execute Check:** Click the blue **Check Port** button to attempt a TCP connection. Use the **Clear** button to reset selected inputs.

Key Use Cases & Troubleshooting

1. Firewall & Security Group Auditing

Verify whether edge firewalls or security group rules correctly restrict external access to database ports (e.g., MySQL `3306`, MSSQL `1433`), directory services (`LDAP`/`LDAPS`), or enterprise application suites (`WebLogic`).

2. Email Server Infrastructure Verification

Validate client access and mail transfer ports (`25`, `465`, `587`, `993`) before configuring Mail Clients or enforcing MTA-STS.

3. Enterprise Oracle & WebLogic Environment Diagnostics

Audit accessibility for WebLogic application servers (`7001`/`7002`), administration portals (`9001`), and database listeners (`1521`/`2484`) across hybrid infrastructure.

4. Distinguishing Host Status from Port Status

If a host responds to a Ping Check but fails a Port Check, the host is online, but the target daemon is either stopped or blocked by a firewall rule.