Why Can I Not Ping My Domain

General | Updated March 2026

If the ping command does not respond when you ping your domain, this is normal. Our servers have ICMP (ping) disabled at the firewall level as a security measure. A blocked ping does not mean your website is down or that there is a problem with your hosting.

In This Guide

Why Ping Is Disabled
How to Check If Your Site Is Up
Verifying DNS Is Pointing Correctly
Using Traceroute Instead
Common Misconceptions

Quick Answer

Ping is Blocked by Design

ICMP ping is disabled at the firewall to prevent ping flood attacks
Your website can be fully accessible even when ping is blocked
Use a browser or an online tool to check if your site is up

01. Why Ping Is Disabled

ICMP ping is disabled on our servers as a security measure. Ping flood attacks (sending thousands of ICMP packets per second) are a common denial-of-service technique, and network reconnaissance tools use ICMP to probe servers for information. Blocking ICMP at the firewall reduces the attack surface without affecting website functionality, email delivery, or any other hosting service.

This is standard practice across the web hosting industry. Most shared and managed hosting providers block ICMP by default.

02. How to Check If Your Site Is Up

Since ping won't work, use these methods instead:

Open your domain in a browser - The simplest test. If your site loads, the server is up and your DNS is working correctly.

Ultra Web Hosting Up or Down checker - Our tool at upordown.ultrawebhosting.com checks your domain from an external location. If the server responds to HTTP requests, your site is up even though ping is blocked.

Command line HTTP check - Use curl to test without opening a browser:

# Check for an HTTP response (works even when ping is blocked)
curl -Is https://yourdomain.com | head -5

A HTTP/2 200 response means your site is up and responding normally.

03. Verifying DNS Is Pointing Correctly

If your site isn't loading in a browser either, the issue may be DNS rather than server availability. Check that your domain resolves to the correct IP:

# Check what IP your domain resolves to
nslookup yourdomain.com

# Or use dig
dig yourdomain.com +short

The IP returned should match your server's IP (shown in your cPanel left sidebar or welcome email). If it points to the wrong IP or returns no results, your nameservers may not be set correctly. See our DNS propagation guide.

You can also use our DNS Lookup tool to check your domain's DNS records from an external location.

04. Using Traceroute Instead

If you need to diagnose network routing issues (slow connections, intermittent access), use traceroute with TCP instead of ICMP:

# TCP traceroute to port 80 (HTTP) - works even with ICMP blocked
traceroute -T -p 80 yourdomain.com

# On Windows, use tracert (uses ICMP, will stop at the firewall)
# Instead, use: curl -o /dev/null -w "time_total: %{time_total}\n" https://yourdomain.com

TCP traceroute uses HTTP connections instead of ICMP packets, so it can reach the server even though ping is blocked.

05. Common Misconceptions

"Ping timeout means the server is down" - Not true. Ping is blocked at the firewall. The web server, email, FTP, and all other services can be running perfectly while ping shows "Request timed out."

"I need ping to test my site" - Ping tests ICMP connectivity, not web server availability. An HTTP check (curl -Is) or a browser test is a more accurate measure of whether your site works for visitors.

"My monitoring tool says the server is down" - If your monitoring tool uses ICMP ping, it will always report the server as down. Configure it to use HTTP/HTTPS monitoring instead. Most monitoring services (UptimeRobot, Pingdom, etc.) support HTTP checks.

If your website genuinely isn't loading (not just failing to ping) and DNS is pointing to our servers, check if your IP is blocked by the firewall using our firewall unblock guide, or open a support ticket.