Always active monitoring

KEEP YOUR SITES ONLINE.
WE FEEL EVERY BEAT.

Ten checks across uptime, certificates, domains, DNS, security headers, performance, exposure, SEO and broken links. Scheduled monitoring is free on unlimited websites, and an hour of downtime sends one message, not a hundred.

MONITORING FREENO CREDIT CARDSELF-HOSTABLE

ONE SITE.
EVERY LAYER UNDER IT.

A website is not one thing. Checking it properly means asking the registry, the resolvers, the certificate and the page itself — and knowing which of them moved.

What a check reaches out to

Every run talks to services outside your infrastructure and outside ours. When one of them reports something different from last time, Pulse tells you which one — rather than a single red dot that could mean anything.

Public DNS resolvers
A · AAAA · MX · NS · TXT · CNAME · CAA · SOA
Registry RDAP servers
Expiry date · registrar status
Your TLS endpoint
Chain trust · hostname · protocol
PageSpeed Insights
Lighthouse · Core Web Vitals

WHATEVER YOUR GOAL.

Every check below exists and runs today. Nothing here is a roadmap item.

See all monitoring checks

Is it up, and is it right? An uptime check records availability, response time and status code. A content assertion goes further and looks at what came back, which is how you catch a 200 response quietly rendering an error page.

Default interval5 min
Feeds the uptime %Uptime only
uptime + contentHealthy

# last three runs

[200 OK] 412ms · body matched

[200 OK] 389ms · body matched

[200 OK] 401ms · “Add to cart” missing

How uptime and content works

A real TLS handshake, not a header sniff: chain trust, hostname match and protocol version. Separately, an RDAP lookup reads the domain's registration expiry straight from the registry. Both warn weeks out rather than the morning it breaks.

Certificate warning21 days
Domain warning30 days

Certificate valid

Expires in 63 days

OK

protocol: TLSv1.3

domain expires: 2027-04-11 (registry)

How certificates and domains works

Both of these remember what they saw last time. A record you declared going wrong fails the check. A change you did not declare is reported and shown, but pages nobody — because a planned DNS edit is not an incident, and the next run treats the new value as normal.

Record types watched8 + SPF/DMARC/DKIM
Undeclared changeReported, not paged

# drift detected

A records 203.0.113.42198.51.100.7

CSP removed on this deploy

Shown as degraded, no incident opened.

How dns and security headers works

Performance via Google PageSpeed, an authorised exposure scan, technical SEO and broken links. These never run on a schedule, on purpose: a third party moving a page should not wake you at 3am.

RunsManual only
HistoryKept per suite
PerformanceLighthouse + CWV
EXPOSUREReady
SEOReady
LINKSReady
How deep tests, when you ask works

READY TO KEEP YOUR PULSE ON UPTIME?

Uptime, SSL, domain, DNS and security-header checks that run on a schedule, plus on-demand performance, exposure, SEO and broken-link tests. Alerts by email, SMS and signed webhook.

Monitoring free foreverNo credit card requiredTesting on Pro