- Open New monitorGo to Monitors and choose "New monitor".
- Pick the check typeSelect TCP port, DNS record, Ping (ICMP) or Domain expiry under Check type.
- Enter the targetEnter host and port, hostname, host or IP address, or domain name, depending on the type.
- Set type-specific optionsFor DNS choose the Record type and optional expected value; for domain expiry set the warning days.
- Create the monitorSet the interval and timeout, then choose "Create monitor".
Besides HTTP, Uptime Tracker can check raw TCP ports, DNS records, ICMP ping and domain registration expiry. TCP and DNS are on every plan; ping and domain expiry need Starter or higher.
| Check type | Plan | What it verifies |
|---|---|---|
| TCP port | Free | A TCP connection to host:port opens |
| DNS record | Free (NS, SRV, PTR on Starter) | A record resolves, optionally to an expected value |
| Ping (ICMP) | Starter | A public host answers ICMP echo |
| Domain expiry | Starter | Registration expiry date from RDAP |
TCP port
Use a TCP monitor for databases, mail servers, SSH, game servers or anything that listens on a port. Enter Host and port, for example db.example.com:5432. The check passes when the connection opens within the timeout. The target must be publicly routable; private and internal addresses are refused.
DNS record
A DNS monitor resolves a record and optionally checks the answer. Choose the Record type: A, AAAA, CNAME, MX and TXT on every plan, plus NS, SRV and PTR on Starter. Enter the Hostname, for example example.com. For SRV use _service._proto.name, and for PTR enter a public IP address.
Use Expected value (optional) to catch hijacked or misconfigured records: the check fails unless an answer contains that text. For example, check that a TXT record still contains your SPF policy, or that an A record still points at your load balancer.
Ping (ICMP)
A ping monitor sends ICMP echo requests to a public hostname or IP address. Enter the Host or IP address without a port. Some networks block ICMP; if the host never answers ping, use a TCP or HTTP monitor instead.
Domain expiry
A domain-expiry monitor warns you before a domain registration lapses. Enter the Domain name, such as example.com, and set Warn this many days before expiry between 1 and 90 (default 30). The expiry date comes from the registry over RDAP, discovered through the IANA bootstrap list. The monitor runs hourly from a cached registry answer that is refreshed about every 12 hours.
Some registries do not publish RDAP data. For those domains the monitor shows unknown rather than guessing a date.
Team-only protocol checks
On Team you can also monitor gRPC health (grpc.health.v1 over TLS, with an optional service name) and SMTP or IMAP servers. The mail checks read the banner and negotiate STARTTLS or implicit TLS; they never authenticate or send mail.
Frequently asked questions
Can I monitor a server on my private network?
No. For security, monitors cannot target private or internal network addresses. The target must be publicly reachable.
Why does my domain-expiry monitor show unknown?
Some registries do not publish RDAP data. Uptime Tracker shows unknown instead of guessing the expiry date.
Which DNS record types are supported?
A, AAAA, CNAME, MX and TXT on every plan. NS, SRV and PTR need Starter or higher.
