API, DNS, and Cron Monitoring Are Now Live on Alphora Signals

Website uptime, SSL, and domain expiry cover the front door — but most stacks have more moving parts than a single URL. A third-party API can start returning errors while your homepage stays up. A DNS record can drift after a provider change and quietly break email or a subdomain. A nightly job can fail silently with nothing watching for its absence.

Three new monitor types close those gaps: API monitoring, DNS monitoring, and cron/heartbeat monitoring. All three are available now on Free and Pro plans, alongside your existing website monitors.

Point an API monitor at any endpoint — REST or GraphQL — and we check it every 5 minutes, the same cadence as website monitors. You control:

• Method and headers — GET, POST, or any other verb, with custom headers for auth tokens or API keys.
• Request body — for endpoints that expect a payload, including GraphQL queries.
• Expected status code — define exactly what “healthy” means for that endpoint instead of assuming any 2xx is fine.

This is the same signal model as website monitoring: one alert when the endpoint starts failing, one when it recovers. No repeated noise.

DNS monitors check a domain's records daily against the record type and value you expect. If a record drifts — after a registrar migration, a DNS provider change, or a misconfigured update — you find out instead of your users finding out for you.

This complements domain expiry monitoring, which already ships as part of every website monitor: expiry monitoring tells you the domain still belongs to you, DNS monitoring tells you it still points where it should.

Scheduled jobs are notoriously hard to monitor from the outside — there's no URL to check, because the job either ran or it didn't. A heartbeat monitor flips that around: your job pings a unique URL we give it when it completes.

• Expected interval — how often the job should run.
• Grace period — how much delay is normal before it counts as missed.

If a ping doesn't arrive in time, we signal it — the same way we'd signal a website going down. It works for cron jobs, queue workers, backup scripts, or any process that runs on a schedule.

All three monitor types live alongside website monitors inside a project — there's no separate setup flow. Open a project, add a monitor, and pick API, DNS, or cron. Alerts route through the same Telegram, Slack, and webhook channels you've already configured.