Ping IP and Port - Check if the host is publicly accessible on the internet

Your Public IPv4: 216.73.216.90

Common Ports: 80 (HTTP), 443 (HTTPS), 22 (SSH), 21 (FTP), 3389 (RDP), 3306 (MySQL), 5432 (PostgreSQL)

Troubleshooting: Why Can't You Ping a Port?

If you're trying to ping a port and it's not responding, don't panic! There are several reasons why this might be happening, and we'll guide you through the steps to diagnose and fix the issue.

1. Check Local Accessibility First

Before assuming an external issue, test whether the port is accessible within your local network. A great tool for this is PsPing, a utility developed by Microsoft that allows you to test connectivity to a specific port.

How to Use PsPing to Test Local Connectivity

  1. Download PsPing:
    • Go to the official Microsoft page and download PsPing.
  2. Run the Command Prompt (CMD) as Administrator:
    • Press Win + R, type cmd, and press Enter.
    • Navigate to the directory where you downloaded PsPing.
  3. Test Port Accessibility:
    • Type the command: psping [IP_Address]:[Port]
    • Example: If your server's IP is 192.168.1.10 and you want to check port 443 (HTTPS), enter: psping 192.168.1.10:443
  4. Analyze the Output:
    • If you receive a successful response, the port is accessible locally. If the request times out, something in your network (firewall, ISP restrictions, or router settings) is blocking the connection.

2. Make Sure Your Firewall, ISP, or Server Isn't Blocking Requests

Your firewall, Internet Service Provider (ISP), or server settings might be blocking external connections.

Steps to Ensure Open Access

  • Check Your Firewall Settings:
    • On Windows, open Windows Defender Firewall → Go to Advanced Settings → Look for Inbound Rules. Ensure that your specific port is allowed through the firewall.
  • Verify ISP Restrictions:
    • Some ISPs block incoming requests on ports like 80, 443, 25, 3389. Call your ISP and ask if they restrict inbound traffic to your port.
  • Confirm Your Hosting Provider's Rules:
    • If you're on a shared hosting service or VPS, check with your provider. Some hosting companies block incoming pings for security reasons.

3. Are You Using a Domain Name? Check DNS Propagation

If you recently set up or changed your domain name, it might not be accessible yet due to DNS propagation delays.

Understanding DNS Propagation

  • When you update a domain's IP address, it takes time for the update to propagate across global DNS servers. Normally, this happens within a few minutes, but in some cases, it can take up to 48-72 hours.

What You Can Do

  • Use an IP Address Instead of a Domain Name: Instead of example.com, try directly pinging your server's IP.

4. Make Sure Your Server Accepts Requests from Brazil

Our service operates from Brazil, so if you're testing a port from another country and it's failing, it might be due to regional restrictions.

How to Ensure Brazilian IPs Can Access Your Server

  1. Whitelist Brazilian IPs in Your Firewall:
  2. Check Geo-Blocking Policies:
    • If your server is configured to reject traffic from certain regions, update the settings to allow Brazilian requests.
  3. Confirm ISP or Hosting Provider Restrictions:
    • Some hosting services block traffic from specific countries. Contact your provider to lift any regional restrictions.

Final Tips for Ensuring Open Ports

  • 🔹 Test Ports Periodically – Network settings and ISP rules can change over time.
  • 🔹 Check Server Logs – Your web server (Apache, Nginx, etc.) might have logs explaining connection failures.
  • 🔹 Software updates – Security updates might close ports unintentionally, so always check your configurations.