Security alerts eMudhra CA compromise · Chrome drops the root Oct 27 Check your certificate → PHP2Shell · is your PHP version exposed? Check your site →

Domain security & uptime monitoring

Is it up? Is it safe?

https://
Security Scans
HTTPS
Compliance
24/7
Uptime Monitoring
Start Monitoring Free See It In Action

Integrated alerts via Email, Slack, JIRA, Linear, and Teams.

  • Cloudflare custom offline page, auto-deployed the moment your site goes down.
  1. 1

    Add a domain

    30 seconds, no agent, no DNS change.

  2. 2

    We watch it two ways

    Up or down every 10 seconds. Safe or exposed every day.

  3. 3

    You get the message

    In Slack, email, JIRA, Linear or Teams, only when three nodes agree.

example.com GET /health · 10 sec
UP
/health
212ms
↑ 4m 12s outage · 3 nodes agreed
SSL89d | Checked4s ago | 6 nodesHealthy
✓ Chicago, US OK – 200 188ms
✓ Los Angeles, US OK – 200 176ms
✓ London, UK OK – 200 241ms
✓ Tokyo, Japan OK – 200 264ms
✓ Johannesburg, ZA OK – 200 395ms
✓ Santiago, Chile OK – 200 312ms
same monitor
A

Security posture

scanned 2h ago · 88/100 · up from C 61 in 30 days

Exposure · clean
✓TLS 1.3 ✓HSTS ✓CSP ✓DMARC ✗DNSSEC ✓X-Frame

Timeline · uptime and security, last 30 days

Today 10:41 uptime
+ Recovered after 4m 12s · offline page removed
Today 10:37 uptime
− Down · HTTP 502 from 3 of 6 nodes · Cloudflare offline page served
• Alerted Slack #ops, email, JIRA OPS-118
Oct 21 02:00 security
+ Exposure resolved · nginx 1.18 → 1.26, 3 CVEs closed
+ Grade B → A (88/100)
Oct 14 02:00 security
− nginx 1.18.0 reached end of life · 1 actively exploited CVE
• Alerted Slack #security · JIRA SEC-241
Oct 3 02:00 security
+ HSTS and Content-Security-Policy added · grade C → B
• Certificate renewed · expires Jan 20

Example monitor · illustrative data

One monitor, every kind of alert

The alert you would have gotten

Down at 10:37, back at 10:41. A version past end-of-life. A header that showed up. The same monitor sends all three to the channel you already watch, and keeps them on the domain’s timeline.

Sample alerts · real ones carry your domain, your channels, your ticket keys

DOWN InternetSecure Today · 10:37

example.com is down · HTTP 502 from 3 of 6 nodes

Consensus reached in 11s · Cloudflare offline page activated · recovered 10:41 (4m 12s)

Sent to Slack #ops · email · JIRA OPS-118

EXPOSURE InternetSecure Oct 14 · 02:00

nginx 1.18.0 reached end of life · 3 known CVEs, 1 actively exploited

Severity high · Fix: upgrade to 1.26 or hide the version string

Sent to Slack #security · JIRA SEC-241

IMPROVED InternetSecure Oct 3 · 02:00

HSTS and Content-Security-Policy added · grade C → B

Strict-Transport-Security: max-age=31536000; includeSubDomains

Sent to email digest

Outages · 10-second checks, 3-node consensus, no false positives Exposure · end-of-life software, known CVEs, actively exploited escalations Changes · headers, certificates, grade, DNS and email auth
~10 sec
Check Interval
6 Locations
3-Node Consensus
Zero
False Positives
~5s
Alert Delivery
100%
Engineer Built & Run

More than up or down

Every monitor is also a security record

Uptime tells you the site answered. The same monitor also records what it answered with: the software it discloses, the headers it sends, the certificate it presents. When any of that changes you hear about it, and the change is kept.

External exposure

The server, framework and CMS versions your site discloses, matched against end-of-life dates and known CVEs, with actively exploited ones escalated. New, resolved and escalated findings go out on the same channels as outages: email, Slack, JIRA, Linear, Teams.

Security timeline

A timeline per domain with incidents and security changes side by side: a header dropped, a certificate swapped, a grade that moved, an outage. Kept 12 months on Free, 2 years on Pro, forever on Enterprise. Evidence, not just a dashboard.

Framework mapping Enterprise

Every check mapped to SOC 2, ISO 27001, NIST CSF, NIST 800-53, PCI DSS and HITRUST, with evidence export for your auditor.

Cloudflare Integration

Your domain is your status page.

When downtime hits, visitors stay on your URL and see a branded offline page instead of an error. When you recover, they're redirected automatically. No third-party status page to maintain. No manual updates. No forgotten "we're back!" posts.

Outage confirmed

Consensus reached — your origin is genuinely down

Worker route activated instantly

Cloudflare intercepts requests and serves your offline page

Recovery detected — route removed

Traffic flows back to your origin automatically

Works on Cloudflare's Free plan

Cloudflare Workers includes 100,000 free requests per day — more than enough to serve your offline page during any outage. No paid Cloudflare plan required.

Use the default page or provide your own custom HTML. Just needs a Cloudflare API token with Worker Scripts and Workers Routes permissions.

example.com

503 — Service Down

We're on it.

Something went wrong and our monitoring caught it. Engineers are investigating.

Auto-reloads when back up

"Night Rain" offline page — served via Cloudflare's edge network · auto-reloads when back up

Incident Timeline

Every incident gets a detailed timeline showing exactly what happened, when, and how it was resolved.

INC-42 Resolved

example.com

Started

Feb 27, 11:18:54 AM

Duration

3m 21s

Cause

HTTP 500

Affected Servers

6 nodes

Last Successful Check · Feb 27, 2026 11:18:36 AM

Los Angeles, US · HTTP 200 · 14ms

18s

Failure Detected · Feb 27, 2026 11:18:54 AM

London, UK · HTTP 500 · 396ms

“HTTP 500 Internal Server Error”

2s

Outage Confirmed (5 servers) · Feb 27, 2026 11:18:56 AM

Chicago, US · HTTP 500 · 168ms

Los Angeles, US · HTTP 500 · 14ms

Tokyo, Japan · HTTP 500 · 320ms

Santiago, Chile · HTTP 500 · 441ms

Johannesburg, South Africa · HTTP 500 · 387ms

6 of 6 nodes agreed · threshold: 4

1s

Offline Page Activated · Feb 27, 2026 11:18:57 AM

Cloudflare Worker route enabled · visitors see maintenance page

JIRA Ticket Created · Feb 27, 2026 11:18:57 AM

IUJ-5

Slack Alert Sent · Feb 27, 2026 11:18:57 AM

Slack webhook

Email Alert Sent · Feb 27, 2026 11:18:57 AM

[email protected]

3m 18s

Recovered · Feb 27, 2026 11:22:15 AM

London, UK · HTTP 200 · 392ms

1s

Recovery Confirmed (different server) · Feb 27, 2026 11:22:16 AM

Chicago, US · HTTP 200 · 13ms

1s

Recovery Confirmed (different server) · Feb 27, 2026 11:22:17 AM

Los Angeles, US · HTTP 200 · 14ms

4 of 6 nodes agreed · threshold: 4

1s

Recovery Confirmed (3 servers) · Feb 27, 2026 11:22:18 AM

Tokyo, Japan · HTTP 200 · 320ms

Santiago, Chile · HTTP 200 · 441ms

Johannesburg, South Africa · HTTP 200 · 392ms

1s

Offline Page Deactivated · Feb 27, 2026 11:22:19 AM

Cloudflare Worker route removed · normal traffic restored

JIRA Recovery Updated · Feb 27, 2026 11:22:19 AM

IUJ-5

Slack Recovery Sent · Feb 27, 2026 11:22:19 AM

Slack webhook

Email Recovery Sent · Feb 27, 2026 11:22:19 AM

[email protected]

Not All Outages Are Created Equal

Detection speed depends on how your site fails. A hard crash is caught in seconds. A slow timeout takes longer to confirm — but we still catch it.

Hard Error 500 / Connection Refused
~5s
alert sent
0s 5s 10s 15s 20s 25s 30s 35s 40s 45s 50s 55s 60s 65s 70s 75s 80s 85s 90s
Detection ~1s Peer verification ~2s each
Slow Response 10s timeout
~25s
alert sent
0s 5s 10s 15s 20s 25s 30s 35s 40s 45s 50s 55s 60s 65s 70s 75s 80s 85s 90s
Detection ~10s Peer verification ~10s each
Complete Timeout 30s max-time
~75s
alert sent
0s 5s 10s 15s 20s 25s 30s 35s 40s 45s 50s 55s 60s 65s 70s 75s 80s 85s 90s
Detection ~30s Peer verification ~30s each

Why the range? Every check requires consensus — multiple nodes must independently confirm the outage before an alert fires. This eliminates false positives but means detection time scales with how long your server takes to fail.

You can configure per-domain timeouts to fine-tune detection speed for critical services.

3AM. Your Site Goes Down.

Without Monitoring

Nobody knows for hours
Customers see error pages
Found out from a customer tweet
Scramble to create tickets manually
No incident record

With InternetSecure

Team alerted in under 10s
Visitors see a branded offline page
Slack, Email, Teams — simultaneously
JIRA & Linear tickets auto-created
Full timeline for post-mortem

What We Check

Every check, every 10 seconds, from a global node.

HTTP / HTTPS
Content Matching
Response Time
SSL Expiry
DNS Resolution
Status Codes
Redirect Chains
Multi-Node Consensus

Track, fix, and record. Compliance made simple

HTTPS

Validate your SSL certificate, TLS version, HSTS enforcement, and mixed content.

SSL Certificate TLS Version HSTS Mixed Content

Web Application

Check security headers that protect against XSS, clickjacking, and session hijacking.

CSP Clickjacking Cookies Security Headers

Infrastructure

Detect web application firewalls and server version exposure.

WAF Detection Server Version

DNS

Verify DNSSEC implementation and nameserver configuration for domain integrity.

DNSSEC Nameservers

Email Authentication

Check DMARC and DKIM records to prevent email spoofing and phishing attacks.

DMARC DKIM

Uptime Monitoring

10-second checks from multiple locations with response time tracking.

Outage

Multi-Framework Security Compliance

One scanner. 50+ security controls. Evidence for your auditors automatically collected.

Automated Scanning & Monitoring

Schedule daily, weekly, or monthly scans with change detection and real-time notifications for security configuration changes and certificate expiration.

Compliance Automation

PDF & JIRA integration with automated evidence collection for 50+ controls across multiple frameworks - reduce audit preparation time by 70%.

HITRUST CSF, SOC 2, ISO 27001, NIST CSF 2.0, PCI DSS, and NIST 800-53

Pricing

Free for one domain. From $5 a month for a team.

Plus $5 · Pro $20 · Enterprise $149 a month. 30-day Pro trial, nothing charged today, cancel anytime.

Start Monitoring Free Compare plans →