TCP & UDP port monitoring
Watch every port — even the ones behind your firewall.
Run an agent inside your network and CuliPulse can watch any port that listens there — databases, message brokers, internal APIs — with no need to poke holes in your firewall or expose anything to the internet. Send a string, match the reply, and get told when it stops answering.
No credit card · free plan forever
Send a string, match the reply
Check what your service actually responds — not just that the port is open.
A TCP check that only confirms the port accepts a connection misses half the picture. With banner checks you send a real payload and assert on the reply — so you know the service is not just listening but actually healthy and talking the right protocol.
The reply is matched by “contains” or a regular expression, and the payload can be plain text or hex bytes for binary protocols. The agent reports only whether it matched — the reply itself is never sent to CuliPulse.
One-click presets
Common services, already configured.
Pick a service — each one lists its usual port — and the payload and expected reply are filled in for you where the protocol has one. You can tweak anything — or leave it as-is and start monitoring in seconds.
Confirm the port accepts connections, and optionally send a string and check the response. Works for any TCP service — databases, brokers, proxies, SMTP servers.
Check that any TCP port is open and accepting connections — PostgreSQL, MySQL, MongoDB, Redis, RDP, message brokers. From CuliPulse's shared agents for public hosts, or from an agent on your network for internal ones.
Not in the preset list? Write your own send string and expected reply — plain text, or hex-encoded bytes for binary protocols — matched by “contains” or a regular expression.
Presets, with their usual ports: Redis · 6379, SSH · 22, SMTP · 587, POP3 · 110, IMAP · 143, Postgres · 5432, MySQL · 3306, MongoDB · 27017, RDP · 3389, DNS · 53, NTP · 123.
UDP checks
UDP too: send a payload, match the reply.
UDP has no handshake, so a check has to send something and see what comes back. CuliPulse's agent sends your payload, waits for a reply, and checks what came back — on every plan, Free included. Internal DNS resolvers and NTP servers are fair game, even the ones that never touch the public internet.
Craft a payload, fire it at the UDP port, and check the reply contains what you expect or matches a regular expression. If nothing comes back in time — 10 seconds by default — it's down.
UDP checks run through an agent, which is exactly how you reach a private DNS server or an NTP daemon that isn't exposed to the public internet. Drop an agent on the same network and you can watch it.
Watch your first port in 2 minutes.
Add a TCP or UDP monitor, pick a preset or write your own banner check, and get alerts you can trust — even for services that never touch the public internet.