Connectivity & Protocol Check

Verify that PortScope can reach your device from the cloud. Ports are checked at the TCP layer first, then with protocol-aware tests for HTTP(S), FTP(S), SMTP, POP3, IMAP, SSH, Telnet, and more.

Diagnostics

🩺 Deep checks (DNS, ping, traceroute)

Target IP or Hostname Device Type

Ports (comma/space separated)

Timeout per port (ms)

Ticket # (optional; prompted if empty)

Auto-run DNS / ping / traceroute on failures

TCP only (skips protocol checks after connect: HTTP GET, banners, etc.)

Cradlepoint / firewall: allow known IPs (Azure outbound)

Tests run from Microsoft datacenter addresses, not from your browser. Allow source 40.119.12.13 — the IPv4 that inetporttester.azurewebsites.net resolves to in public DNS — on the ports you need (for example 8080 and 8443).

Confirm the address: run nslookup inetporttester.azurewebsites.net (expect 40.119.12.13 unless DNS has been updated).
On the Cradlepoint: Firewall / zone policy or port forwarding with a source restriction — allow TCP from that IP to your device’s WAN-forwarded ports.
If DNS changes or tests still fail, re-check nslookup; for extra egress IPs see Microsoft’s App Service IP documentation.

PortScope Diagnostics

TCP open/closed from this server, optional protocol checks, and per-port errors. Hostnames are resolved once per run; ports are checked with bounded concurrency.