Website signals, one view

Know what changed.Fix what matters.

RecordsUp watches the signals around each website, shows where problems were found, and keeps the next action clear.

First site is free
No credit cardGuided setupFree first site

RecordsUp index

Sites, checks, and current issues.

Preview

demo-store.example

Broken links

12 links grouped by source page

Needs action

agency-site.example

Website check

Loaded successfully in 0.8 seconds

Healthy

status-preview.example

SSL certificate

Certificate valid for 48 more days

Healthy
Website

Up

342 ms

SSL

Valid

72 days

DNS

Matched

8/8

Full-site crawl

Scan pages and show where each broken link was found.

Status draft

Prepare a clear public status page and publish it only when ready.

Alert route checks

Confirm alerts can actually reach the right channel.

Crawl

whole site

Find broken links across the site and see the source page for each issue.

Group

by site

Keep uptime, SSL, DNS, links, alerts, and jobs in one site view.

Guide

the fix

Show what changed, where it was found, and the next action.

Share

clear status

Publish uptime and incident context customers can understand.

Made for real site work

Teams use RecordsUp around the systems they already run.

From launch teams to client-site teams, the same workflow keeps checks, alerts, and status clear.

WordPress teams
Shopify stores
SaaS dashboards
Agency launches
API products
Status pages
Cron jobs
Client sites
WordPress teams
Shopify stores
SaaS dashboards
Agency launches
API products
Status pages
Cron jobs
Client sites

How RecordsUp feels

A guided path, not a pile of checks.

Add a site, see the result, fix the source, and verify the known issue from the same place. The preview uses reserved example domains.

Start a guided setupView sample report
Add site

Start with the website people visit.

RecordsUp keeps the first setup focused on the domain, the first checks, and the alert route.

Read result

Checkout page needs one link fix.

The site is online and SSL is healthy. RecordsUp found one confirmed broken link on the checkout page and one alert route that still needs a test.

Fix source

Broken privacy policy link

Update the checkout footer link, then recheck this finding.

Verify

Recheck the known issue.

After the page is updated, run a focused recheck so the report confirms the fix without starting over.

Site setup

demo-store.example

example

Guided setup

4 steps

Website

Added

demo-store.example

Uptime

Ready

Homepage + checkout

SSL

Ready

Certificate expiry

Alerts

Test

Primary email route

First report

needs action
Website checkHomepage loaded in 342 ms
SSL certificateValid for 62 days
DNS readiness8 of 8 locations aligned
Broken privacy policy link/checkout -> https://demo-store.example/privacy-old
01

Add site

demo-store.example

02

Choose checks

Uptime + SSL + alerts

03

Find issue

Broken privacy policy link

04

Fix and recheck

Ready to verify

05

Share status

Status draft ready

Live workflow

A site moves from setup to evidence to action. Every row uses safe example data and points to the next customer decision.

Domaindemo-store.exampleadded
Uptime342 ms responsehealthy
SSL62 days lefthealthy
DNS8/8 alignedready
Domaindemo-store.exampleadded
Uptime342 ms responsehealthy
SSL62 days lefthealthy
DNS8/8 alignedready
Broken link/checkoutneeds action
Source pageCheckout footerfound
Next stepUpdate destinationready
RecheckKnown issue onlyqueued
Broken link/checkoutneeds action
Source pageCheckout footerfound
Next stepUpdate destinationready
RecheckKnown issue onlyqueued

Site-first monitoring, not monitor clutter.

0

site model

Website, SSL, DNS, alerts, jobs, and status around one site.

0+

check types

Every signal points to the next check.

0

guided steps

Setup stays fast for nontechnical site owners.

0m

first setup

See the workflow

A short look at how RecordsUp turns checks into understandable site work.

Launch checks

See launch checks.

Website, SSL, DNS, and status stay together so launch problems are visible before handoff.

8/8

locations live

Alert routes

Know alerts will arrive.

Test email, Slack, and webhook routes before a real issue depends on them.

0

missed signals

Site overview

Keep each site readable.

Group uptime, SSL, DNS, broken links, alerts, and status beside the site they belong to.

1

fix path

Result workflow

The product story stays the same from homepage to dashboard.

RecordsUp is built around the work a customer actually does: add the site, understand the result, fix the source, and recheck the known problem.

01

Setup

Start with a website people recognize

Add the site, pick the first checks, and keep advanced settings out of the way until you need them.

demo-store.example
02

Result

See what changed in plain language

RecordsUp separates healthy checks, confirmed issues, and blocked results so the next step is easier to trust.

1 broken link found on /checkout
03

Fix

Use the source page and next action

The report shows where the issue was found, what destination failed, and what your team should update.

Update the checkout footer link
04

Verify

Recheck the known problem

After the fix, recheck the finding or report without forcing a full discovery crawl every time.

Ready to verify

RecordsUp vs traditional monitoring

One site does not need five separate dashboards.

Traditional tools often split uptime, SSL, DNS, domain, and alert routing into separate views. RecordsUp keeps them attached to the same site.

Traditional monitoring

A wall of IDs and separate alerts.

Website check failed
SSL warning
DNS changed
Domain expiry reminder
Slack route failed

RecordsUp

One site, one explanation, one next step.

One site health view

demo-store.example is online, SSL is valid, DNS is aligned, and the domain is safe.

One explanation people can read

Website uptime, SSL validity, DNS readiness, and domain timing stay attached to one site instead of separate tool rows.

One next step when something changes

If alert delivery, DNS, or SSL needs attention, the fix stays in the same place as the rest of the site results.

Site operations

One site. The checks that explain it.

Add a website once. RecordsUp builds the useful operational view around it: uptime, SSL, DNS, broken links, alerts, status pages, and job check-ins when they matter.

Running checks

demo-store.example

Live

Website is up

demo-store.example loaded successfully in under 1 second.

success

SSL certificate is safe

Certificate is valid for 62 more days.

success

DNS change is spreading

8 of 8 public locations now match.

success

Alert route is ready

Primary email passed the delivery test.

success

Loaded

Website uptime

Know whether the homepage, API, or important endpoint responds correctly.

62 days

SSL and domain safety

Track certificate expiry, domain changes, and domain renewal risk before it becomes urgent.

8/8 live

DNS and launch checks

Follow launches and hosting moves with plain-language progress across DNS, website, and SSL signals.

on time

Jobs and scheduled check-ins

Confirm backups, cron jobs, and scheduled workers checked in when expected.

healthy

TCP and API checks

Watch services, ports, headers, JSON responses, and the answers your setup expects.

public

Status pages

Share public status grouped by site, with clear context and only the checks customers need.

Available checks

What RecordsUp watches today.

The current product covers the main site-operations signals. Each check stays attached to the site instead of becoming a separate dashboard island.

Live

Website uptime

Response, status code, content, and JSON assertions.

Live

SSL certificates

Expiry, invalid certificates, and certificate changes.

Live

DNS readiness

Resolver agreement and launch propagation.

Live

Domain expiry

Registration expiry and renewal windows.

Live

API and TCP

Ports, APIs, expected status, headers, and JSON values.

Live

Scheduled check-ins

Cron jobs, backups, workers, and scheduled tasks.

Live

Migration readiness

DNS, website, content, and SSL in one launch check.

Live

Broken links

Run-scoped crawls with source-page results and recovery tracking.

Live

Mixed content

Find insecure assets referenced from HTTPS pages.

Live

Page and visual changes

Review text or screenshot changes against an approved baseline.

Live

Safe browser flows

Verify important journeys while stopping before payment.

Live

Health endpoints

Read component health from structured endpoints.

Live

Status pages

Public status pages for uptime and incident context.

Integrations

See what is live, what needs setup, and what is planned.

See which alert routes you can use today, which need setup, and which channels are next.

What is available now

Email, Slack, Discord, signed webhooks, and Stripe billing are available now. Microsoft Teams, Zapier, SMS, and WhatsApp are next.

Live

Email

Account emails and alert tests can be delivered.

Used for signups, verification emails, password resets, and alert delivery tests.

Live

Slack

Works with a Slack incoming webhook.

Add a Slack webhook in alert settings, then send a test delivery.

Live

Signed webhooks

Webhook alerts include a signature your receiving app can verify.

Useful for automations, incident tools, and custom workflows.

Coming later

Microsoft Teams

Microsoft Teams alerts are not available yet.

Use Slack, Discord, email, or a signed webhook today.

Live

Discord

Works with a Discord webhook destination.

Add the Discord webhook URL in alert settings and verify it with a test.

Provider required

SMS

SMS is unavailable until paid message delivery is connected and tested.

Use email, Slack, Discord, or signed webhooks until SMS delivery is available.

Provider required

WhatsApp

WhatsApp is unavailable until paid message delivery is connected and tested.

Use email, Slack, Discord, or signed webhooks until WhatsApp delivery is available.

Live

Stripe billing

Checkout, billing updates, and the customer portal are ready.

The free first-site flow still works while billing setup is completed.

Product walkthrough

The dashboard shows the next useful action.

Needs attentionnow

Know what is wrong

The dashboard separates site issues from alert setup problems, so people fix the right thing first.

Know what is wrong

The dashboard separates site issues from alert setup problems, so people fix the right thing first.

Guided stepsnow

Open the fix path

Every alert includes the affected site, likely cause, and the next action.

Open the fix path

Every alert includes the affected site, likely cause, and the next action.

Customer viewnow

Share a clean status

Public pages show current state, recent context, and the status customers need.

Share a clean status

Public pages show current state, recent context, and the status customers need.

Entire dashboard

One place for sites, issues, alerts, and public status

overview

Dashboard

app.recordsup.com/demo/dashboard

live

Sites healthy

12 / 12

Needs action

1 route

Public pages

4 active

Website check

Homepage loaded in 342 ms

SSL certificate

Valid for 62 days

DNS readiness

8 of 8 locations aligned

Alert delivery

Add an email destination and send a test

Current site summary

demo-store.example

Site is online. Alert route needs attention.

Website, SSL, and DNS are healthy. Fix the email destination and retest delivery.

Step 1

Open alert settings

Step 2

Add destination

Step 3

Send test alert

Add one site. Get one clear answer.

RecordsUp keeps the beginner path calm while keeping optional checks ready for production work.

Site health

demo-store.example

100%

Website, SSL, DNS, and alerts are healthy.

Next action

No action needed. Your site is online, SSL is valid, and alerts are ready.

Everything is working

Alert route

email delivery failed

Fix destination

First site is free

Why it feels calmer

One product model for site owners and teams.

Sites first

RecordsUp groups website, SSL, DNS, domain, job, and launch checks under the site your team actually recognizes.

Fix paths, not dashboards

When something needs attention, RecordsUp explains what happened, why it matters, and the next action.

Status pages people can read

Share a simple service view with current state, recent context, and only the details customers need.

Alert delivery is checked too

Alert problems stay separate from website problems, so your team knows whether to fix the site or the notification route.

All sites

status.demo-store.example

public
Website online
SSL valid
Alerts ready
Customers see the current service state, recent context, and what is being watched.

Status page reports

Share confidence without sending people into a dashboard.

Public pages turn the same checks into a clean customer view: current state, incident context, and a clear answer.

Pricing

Start with one site. Add more when work grows.

Start with the first site for free. Add paid sites when you need broader coverage.

Starter

First site free

Freeper month

No VAT while free

For one site owner who needs a clear answer.

  • 1 site
  • Website uptime
  • SSL expiry warnings
  • Public status page
Start with one site

Launch

Most useful

€2per extra site

First site stays free · excl. VAT

For active websites, launches, and growing teams.

  • Pay only for active sites
  • DNS and launch checks
  • API and TCP checks
  • Test alert delivery
Choose Launch

Operator

Volume price

€1.50per site from 50

Graduated volume pricing · excl. VAT

For teams running larger client or production portfolios.

  • Automatic volume pricing
  • Scheduled job checks
  • Status-page branding
  • Priority support
Start with one site

Field notes

Practical ways teams use RecordsUp.

See the monitoring workflows RecordsUp is built for: launches, stores, client sites, and status reporting.

field note

Launch checks stay in one place.

DNS, SSL, and site status are easier to trust when they are presented together instead of across separate tools.

Launch workflow

field note

The next action is visible.

RecordsUp is designed to explain what changed and whether the fix belongs on the website, DNS, SSL, or alert route.

Issue triage

field note

Status can be shared cleanly.

Public status pages show the service state in a format customers can scan quickly.

Client reporting

field note

Alert delivery is its own signal.

If the site is healthy but email, Slack, or webhook delivery fails, the route can be fixed without blaming the site.

Alert routing

field note

Launch checks stay in one place.

DNS, SSL, and site status are easier to trust when they are presented together instead of across separate tools.

Launch workflow

field note

The next action is visible.

RecordsUp is designed to explain what changed and whether the fix belongs on the website, DNS, SSL, or alert route.

Issue triage

field note

Status can be shared cleanly.

Public status pages show the service state in a format customers can scan quickly.

Client reporting

field note

Alert delivery is its own signal.

If the site is healthy but email, Slack, or webhook delivery fails, the route can be fixed without blaming the site.

Alert routing

field note

Launch checks stay in one place.

DNS, SSL, and site status are easier to trust when they are presented together instead of across separate tools.

Launch workflow

field note

The next action is visible.

RecordsUp is designed to explain what changed and whether the fix belongs on the website, DNS, SSL, or alert route.

Issue triage

field note

Status can be shared cleanly.

Public status pages show the service state in a format customers can scan quickly.

Client reporting

field note

Alert delivery is its own signal.

If the site is healthy but email, Slack, or webhook delivery fails, the route can be fixed without blaming the site.

Alert routing

field note

Launch checks stay in one place.

DNS, SSL, and site status are easier to trust when they are presented together instead of across separate tools.

Launch workflow

field note

The next action is visible.

RecordsUp is designed to explain what changed and whether the fix belongs on the website, DNS, SSL, or alert route.

Issue triage

field note

Status can be shared cleanly.

Public status pages show the service state in a format customers can scan quickly.

Client reporting

field note

Alert delivery is its own signal.

If the site is healthy but email, Slack, or webhook delivery fails, the route can be fixed without blaming the site.

Alert routing

field note

Plain language reduces handoff.

Clear summaries help nontechnical owners understand what happened without reading raw monitoring output.

Site ownership

field note

Client portfolios stay readable.

Grouping checks by website keeps uptime, SSL, DNS, broken links, alerts, and status attached to the site they affect.

Agency operations

field note

Fewer dashboards, fewer decisions.

The site-first model keeps health, incidents, status, and next steps in one workflow.

Team workflow

field note

Quiet risks become visible earlier.

SSL expiry, domain renewal timing, and DNS drift are easier to act on when they sit beside normal site health.

Site maintenance

field note

Plain language reduces handoff.

Clear summaries help nontechnical owners understand what happened without reading raw monitoring output.

Site ownership

field note

Client portfolios stay readable.

Grouping checks by website keeps uptime, SSL, DNS, broken links, alerts, and status attached to the site they affect.

Agency operations

field note

Fewer dashboards, fewer decisions.

The site-first model keeps health, incidents, status, and next steps in one workflow.

Team workflow

field note

Quiet risks become visible earlier.

SSL expiry, domain renewal timing, and DNS drift are easier to act on when they sit beside normal site health.

Site maintenance

field note

Plain language reduces handoff.

Clear summaries help nontechnical owners understand what happened without reading raw monitoring output.

Site ownership

field note

Client portfolios stay readable.

Grouping checks by website keeps uptime, SSL, DNS, broken links, alerts, and status attached to the site they affect.

Agency operations

field note

Fewer dashboards, fewer decisions.

The site-first model keeps health, incidents, status, and next steps in one workflow.

Team workflow

field note

Quiet risks become visible earlier.

SSL expiry, domain renewal timing, and DNS drift are easier to act on when they sit beside normal site health.

Site maintenance

field note

Plain language reduces handoff.

Clear summaries help nontechnical owners understand what happened without reading raw monitoring output.

Site ownership

field note

Client portfolios stay readable.

Grouping checks by website keeps uptime, SSL, DNS, broken links, alerts, and status attached to the site they affect.

Agency operations

field note

Fewer dashboards, fewer decisions.

The site-first model keeps health, incidents, status, and next steps in one workflow.

Team workflow

field note

Quiet risks become visible earlier.

SSL expiry, domain renewal timing, and DNS drift are easier to act on when they sit beside normal site health.

Site maintenance

FAQ

Questions before you start.

Quick answers about what RecordsUp checks, who it is for, and how alerts and status pages work.

What does RecordsUp actually monitor today?

Today the product covers website uptime, SSL certificates, DNS readiness, domain expiry, API and TCP checks, scheduled job check-ins, migration readiness, alert delivery, and public status pages.

Who is this built for?

RecordsUp is for site owners, launch teams, agencies, and ecommerce teams that want one clear site-level answer instead of separate tools for uptime, SSL, DNS, and status.

Why separate alert delivery from website problems?

Because the fix is different. If the site is online but Slack, email, or webhook delivery failed, the next action should be about the route, not the website.

Are the next checks available now?

No. That section shows what RecordsUp is exploring next. The checks you can use today are listed above.

Contact

Talk to someone before you buy.

Have a question about plans, launches, client portfolios, or which checks fit your workflow? Send us a message.

We usually reply within one business day.

What teams usually ask

Which plan fits one site vs many sites?

Your first site is free. Sites 2–49 use Launch per-site pricing, and Operator volume pricing starts automatically at 50 sites.

How do alert routes get tested?

RecordsUp can send a test through email, Slack, or webhook so delivery is proven before an incident happens.

Can agencies keep client sites grouped cleanly?

Yes. The site remains the main unit, so checks, alerts, and status pages stay attached to the client site.

Start a guided setup

Planned next

On the roadmap

More ways to watch your site are next.

Open each item to see how it would help your team catch problems earlier once it becomes available.

Availability

These checks are not part of your account today. The available checks are listed in the section above.

1
2
3
4
5
6
7
8
9