Certificates get issued. DNS drifts. Registrars move. nob.center monitors the public control-plane signals that define who can impersonate your service. With clean diffs, history, and alert rules you can automate.
Three modules, one UI, consistent alerting & history.
Detect unexpected certificates for your domains (including wildcards). New issuance is a high-confidence signal that control paths exist — sometimes where you didn’t expect them.
Daily RDAP snapshots with history and diffs. Get notified when registration, contacts, nameservers, or expiry data changes — the “who controls it” layer.
Track DNS records over time (A/AAAA/CNAME/TXT/MX/CAA/NS…). Catch unauthorized changes and drift between environments — the “where does it point” layer.
Build templates and rules: severity, conditions, routing, and dedupe. Track delivery status.
nob.center is not a compliance platform but it helps generate concrete monitoring evidence for common security control frameworks.
Supports configuration monitoring (CM family), system monitoring (SI-4), and continuous monitoring (CA-7) by detecting DNS drift, certificate issuance events, and registration changes with stored history and diffs.
Helps demonstrate monitoring of externally exposed systems and security-relevant change events. Structured alerts and API access simplify evidence collection for CC7 system operations criteria.
Aligns with Annex A controls on configuration management and monitoring activities by tracking domain ownership data, DNS configuration, and certificate lifecycle changes over time.
Two minutes to get from “huh?” to “alert received”.
Select which signals to monitor: CT, RDAP, DNS. Start small and expand.
Define routing and formatting (email/webhook, etc.). Reuse everywhere.
Match on patterns and change types. Assign severity and dedupe windows.
Every change is stored. Compare snapshots and export via API.
Pull alerts, snapshots, and diffs into your own automation. If you prefer a UI: ignore the API, enjoy the UI.
# API usage (curl)
# Swagger / OpenAPI docs are available inside the app UI.
BASE="https://app.nob.center"
TOKEN="$NOB_TOKEN"
# 1) Alert stats (last 7 days)
curl -s -H "Authorization: Bearer $TOKEN" \
"$BASE/api/alerts/stats?days=7"
# 2) CT: certificate matches (paged)
curl -s -H "Authorization: Bearer $TOKEN" \
"$BASE/api/ct-log/matches?page=1&page_size=20"
# 3) DNS: recent changes
curl -s -H "Authorization: Bearer $TOKEN" \
"$BASE/api/dns-watcher/changes?limit=10"
# 4) RDAP: diff snapshots for a domain
curl -s -H "Authorization: Bearer $TOKEN" \
"$BASE/api/rdap/domains/example.com/diff"
Real screenshots from nob.center showing CT monitoring, DNS tracking, and alert management.
Simple limits. No sales calls. Cancel anytime.
$0/month
$249 $149/month
Billed monthly (USD). Taxes calculated at checkout.
Start Pro
RFQ
Tailored contracts for larger teams.
The stuff people ask before they hit “Start free”.
Three public-signal modules: Certificate Transparency (new certificates), RDAP (registration/WHOIS-like data), and DNS records over time. Each module includes rules + alerts + diffs + history.
Not in the marketing sense. nob.center focuses on the domain trust surface: who owns the domain (RDAP), where it points (DNS), and who can issue certs (CT).
Yes — everything is based on public signals (CT logs, RDAP, DNS). It’s domain-based rather than brand-based.
You can define webhook targets with flexible authentication. Each alert delivers full context to your endpoint. The API can also be used to feed SIEM/SOAR workflows.
Payments are processed by Paddle, our merchant of record. Paddle handles billing, tax calculation, and invoicing on our behalf. nob.center never stores your payment details.
Spin up a free tier account and you’ll be receiving alerts in minutes.