Check your connection to SendPulse

If SendPulse loads slowly, shows errors, or won't start at all, the cause is usually the network between your computer and our server, such as your internet provider's route, packet loss, or delays in your region.

Let’s talk about how to run connection checks on Windows, macOS, and Linux.

Keep in mind that you should run these checks from the same network where the problem occurs. Use login.sendpulse.com for each check.

Check the connection

The ping command shows if the server is reachable, how long it takes to respond, and whether any packets are lost. It's the quickest check to start with.

Keep an eye on the summary. The statistics line should show Lost = 0 (0% loss), and the response time should stay stable. If you notice packet loss or unusually high response times, include the result in your support request.

On Windows

Open the Start menu, type cmd, and run Command Prompt.

Enter the command and press Enter.

ping login.sendpulse.com

To run a continuous check, add -t.

ping login.sendpulse.com -t

To stop the check, press Ctrl + C.

On macOS

Open Terminal, for example, using Spotlight. Press Cmd + Space, then type Terminal.

Enter the command and press Enter.

ping login.sendpulse.com

To stop the check, press Ctrl + C.

On Linux

Open Terminal, for example, by pressing Ctrl + Alt + T.

Enter the command and press Enter.

ping login.sendpulse.com

To stop the check, press Ctrl + C.

Check the route to the server

The traceroute command shows the entire path from your computer to our server and which intermediate node introduces delays or drops. It's a key check when SendPulse is unavailable or slow in a specific region.

If you see an asterisk (*) next to a node during the route check, this means that the node didn't respond to the request. If the trace breaks off at some node and doesn't reach the end, copy the result and send it to our support team.

Check if the trace reaches the destination server. If you see a sharp increase in time or multiple asterisks in a row closer to the end of the route, include the result in your support request.

On Windows

Open Command Prompt. The tracert tool is already built into Windows.

Enter the command and press Enter.

tracert login.sendpulse.com

On macOS

Open Terminal. The traceroute tool is already built into macOS.

Enter the command and press Enter.

traceroute login.sendpulse.com

To stop the check, press Ctrl + C.

On Linux

Open Terminal. If traceroute isn't installed, on Debian/Ubuntu, run:

sudo apt install traceroute

Once it’s installed, enter the command and press Enter.

traceroute login.sendpulse.com

To stop the check, press Ctrl + C.

Check for packet loss on the route

MTR combines ping and traceroute. It continuously checks every node on the route and shows exactly where and how many packets are lost. It's the most informative check, and the one support teams ask for most often. The tool isn't built into Windows or macOS, so you need to install it first.

Keep an eye on the Loss% column, which shows packet loss at each node. If loss appears and continues all the way to the last node, include the result in your support request.

On Windows

On Windows, use the WinMTR version. Download WinMTR from the official source, unzip the archive, and run WinMTR64.exe.

In the Host field, enter login.sendpulse.com and click Start. Let the check run for about 10–15 minutes to gather enough data, then click Stop.

Click Export Text and save the file to send it to support.

On macOS

Open Terminal. If you don't have the Homebrew Package Manager, install it by running:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Then, install MTR:

brew install mtr

Enter the command and press Enter. It requires admin rights and starts with sudo.

sudo mtr login.sendpulse.com

Let the check run for 10–15 minutes. Copy the result from Terminal or take a screenshot of the window, including the Loss% column. Then, stop it with Ctrl + C.

On Linux

Open Terminal and install MTR.

On Debian/Ubuntu, use:

sudo apt install mtr

On RHEL/CentOS/Fedora, use:

sudo yum install mtr

Then, enter the command and press Enter.

mtr -rw login.sendpulse.com

Check DNS

This check shows if login.sendpulse.com correctly resolves to the server IP address. If it doesn't, your DNS server or ISP may be causing the issue.

The nslookup and dig commands show which IP address the domain points to. nslookup is available on all systems and gives a short result, while dig works on macOS and Linux and shows more detail.

If the command runs successfully, you'll see an IP address in the Address line or ANSWER SECTION. If there's no IP address or you get an error, include the result in your support request.

On Windows

Open Command Prompt and enter the command.

nslookup login.sendpulse.com

On macOS

Open Terminal and enter the command.

dig login.sendpulse.com

You can also use nslookup login.sendpulse.com.

On Linux

Open Terminal and enter the command.

dig login.sendpulse.com

If the tool isn't available, install it with sudo apt install dnsutils or use nslookup login.sendpulse.com.

Check port 443

SendPulse runs over the secure port 443. This check shows if a firewall, antivirus, or your provider's network is blocking the connection.

A successful check returns succeeded or TcpTestSucceeded: True. If the result differs, a firewall, antivirus, or your internet provider may be blocking it. Include the result in your support request.

On Windows

Open PowerShell. For example, type PowerShell in the Start menu. Enter the command.

Test-NetConnection login.sendpulse.com -Port 443

If TcpTestSucceeded is True in the result, the port is available.

On macOS

Open Terminal and enter the command.

nc -vz login.sendpulse.com 443

On Linux

Open Terminal and enter the command.

nc -vz login.sendpulse.com 443

Check the server response time

This check shows how long each stage of the connection takes, including the DNS lookup, connection, secure connection, and loading. It's useful when SendPulse loads slowly.

Keep an eye on the Total line, which shows the overall response time. If it's high, or if one stage (DNS, Connect, TLS, or First Byte) is noticeably longer than the others, include the result in your support request.

On Windows

Open PowerShell and enter the command.

curl.exe -o NUL -s -w "DNS: %{time_namelookup}s`nConnect: %{time_connect}s`nTLS: %{time_appconnect}s`nFirst Byte: %{time_starttransfer}s`nTotal: %{time_total}s`n" https://login.sendpulse.com

On macOS

Open Terminal and enter the command.

curl -o /dev/null -s -w "DNS: %{time_namelookup}s\nConnect: %{time_connect}s\nTLS: %{time_appconnect}s\nFirst Byte: %{time_starttransfer}s\nTotal: %{time_total}s\n" https://login.sendpulse.com

On Linux

Open Terminal and enter the command.

curl -o /dev/null -s -w "DNS: %{time_namelookup}s\nConnect: %{time_connect}s\nTLS: %{time_appconnect}s\nFirst Byte: %{time_starttransfer}s\nTotal: %{time_total}s\n" https://login.sendpulse.com

Check the SSL/TLS connection

This check is useful if you get a secure connection error or a certificate error.

A browser-based connection check works on any operating system and requires no installation.

Go to https://login.sendpulse.com. Click the View site information icon to the left of the address bar.

With a secure connection, you'll see Connection is secure. To see the certificate details, click Certificate is valid.

If there's a security issue, a warning appears instead of Connection is secure, and the certificate may be marked as invalid. Take a screenshot of the warning and the certificate details, then send them to support.

If support asks for more details, run the check in the terminal. The command is the same on all systems, but the availability of the openssl tool depends on your operating system.

On Windows

The openssl tool isn't included with Windows by default.

To check the certificate in the terminal, install Git for Windows. Once it’s installed, open PowerShell and enter the command.

openssl s_client -connect login.sendpulse.com:443 -servername login.sendpulse.com

If the check session doesn't end on its own, end it manually by pressing Ctrl + C.

On macOS

The openssl tool is already built into macOS. Open Terminal and enter the command.

openssl s_client -connect login.sendpulse.com:443 -servername login.sendpulse.com

If the check session doesn't end on its own, end it manually by pressing Ctrl + C.

On Linux

The openssl tool is usually built into Linux. Open Terminal and enter the command.

openssl s_client -connect login.sendpulse.com:443 -servername login.sendpulse.com

If the check session doesn't end on its own, end it manually by pressing Ctrl + C.

Send the data to support

Copy the full results of each check and send them to support. Our team will analyze the data and suggest next steps. Providing more diagnostic data helps us resolve the issue faster.

Include the following in your request: the ping result, the traceroute result (tracert or traceroute), the MTR or WinMTR result, the port 443 check result, the response time result (curl), and a screenshot of any errors you see on the screen.

Last Updated: 07.07.2026