Help Center
Learn how our platform works, what each check means, and how to get the most out of InternetSecure.
Multi-node checks, consensus detection, and how we determine downtime
Adding domains, configuring checks, and using the dashboard
HEAD vs GET requests, check frequency, and timeout settings
Slack, email, and JIRA alert channels
How incidents are created, tracked, and resolved
Automatic branded maintenance page via Cloudflare Workers
Slow response detection with configurable thresholds
Suppress alerts during planned downtime on a recurring schedule
When your WAF blocks specific monitoring locations
Whitelist our monitoring IPs in Cloudflare, AWS WAF, or your firewall
SSL/TLS certificates, HTTPS redirect, HSTS and mixed content
CSP, clickjacking protection, cookie security and security headers
WAF detection, server information and hosting
DNSSEC validation and nameserver configuration
DMARC, SPF and DKIM email spoofing prevention
Invite teammates, manage roles and seat limits
Paid plans include multiple team seats, allowing you to invite colleagues to share access to your domains, scans, uptime monitoring, and incidents.
Go to Account Settings and open the Team Members panel. Enter your teammate's email address and click Send Invite. They'll receive an email with a link to accept the invitation. The link expires after 7 days.
If the invited person doesn't have an InternetSecure account, they'll be directed to register first, then automatically join your team.
Owners can remove a team member from the Team Members panel in Account Settings. Access is revoked immediately. Team members can also leave on their own from the same panel.
Pending invitations can be revoked from the Team Members panel before they're accepted.
InternetSecure monitors your websites from 6 independent nodes distributed across multiple geographic locations. Each node sends an HTTP request to your domain at regular intervals and records the response status and time.
We use a consensus-based approach to avoid false positives. A single node reporting a failure does not trigger an alert — multiple nodes must agree that your service is unreachable before an incident is created.
The default consensus threshold is 3 of 6 nodes. At least 3 nodes must independently confirm that your site is down before we consider it a real outage.
By default, checks use the HEAD method, which requests only response headers without downloading the page body. This is faster and uses less bandwidth.
If your server doesn't support HEAD (some return 405), switch to GET in domain settings.
Checks run at a 1-minute interval from all active nodes. Each check has a 30-second timeout.
User agent: InternetSecure Uptime Monitor/1.0
When an incident is confirmed (consensus reached), alerts are sent through your configured channels:
You receive two alerts per incident: one when downtime is detected and one when the service recovers.
An incident is created when enough nodes agree your site is unreachable. Each incident records:
Incidents are automatically resolved when consensus confirms your site is back up.
A degraded status means some nodes can reach your site but others cannot — often a regional or CDN issue.
To enable uptime monitoring:
The Uptime Dashboard shows all monitored domains with status, uptime %, response time chart, and SSL expiry. Click any domain for detailed history.
When downtime is detected, InternetSecure can automatically deploy a branded maintenance page to your domain using Cloudflare Workers. Visitors see a professional offline page instead of an error, and the page auto-reloads when your site recovers.
How it works:
Setup:
The deployment and teardown is fully automatic — no manual action required during an outage. A cloud icon (☁) appears next to domains with an active offline page.
Degraded is a distinct status from "down" — it means your site is responding but slower than your configured threshold. The site is still reachable, but performance has dropped significantly.
How it's detected:
Status transitions:
You can configure the threshold (100ms – 30,000ms) per domain and optionally enable separate degraded alerts.
Maintenance windows let you suppress alerts during planned downtime so you don't get paged for expected outages like deployments or server restarts.
How it works:
Configuration (per domain):
Configure maintenance windows in your domain's uptime settings.
A node is flagged as blocked when it has an 80%+ failure rate over the last 24 hours while other nodes successfully reach your site. This usually means your server's firewall or WAF is rejecting requests from that node's IP address.
How to identify blocked nodes:
How to fix it:
Whitelist our monitoring IPs in your firewall or WAF. See the IP Whitelist & Firewall Rules article for step-by-step guides for Cloudflare and AWS WAF.
Blocked nodes are excluded from consensus calculations to avoid false positives — your alerting accuracy is not affected, but monitoring coverage is reduced.
If your firewall or WAF blocks automated requests, whitelist these IPs:
Monitoring Node IPs
45.77.71.241
107.191.48.117
108.61.174.176
66.42.33.226
64.176.3.66
139.84.226.210
Cloudflare WAF
Allow InternetSecure Monitoring(ip.src eq 45.77.71.241) or (ip.src eq 107.191.48.117) or (ip.src eq 108.61.174.176) or (ip.src eq 66.42.33.226) or (ip.src eq 64.176.3.66) or (ip.src eq 139.84.226.210)AWS WAF
InternetSecure-Monitoring and add:45.77.71.241/32
107.191.48.117/32
108.61.174.176/32
66.42.33.226/32
64.176.3.66/32
139.84.226.210/32Checks whether your website properly encrypts all traffic using SSL/TLS.
Learn more: What is SSL?
Evaluates security headers and cookie configurations that defend against common web attacks.
Learn more: OWASP Secure Headers Project
Examines your server-side security posture.
Learn more: What is a WAF?
Checks your domain's DNS security and nameserver configuration.
Learn more: What is DNSSEC?
Checks DNS records that prevent email spoofing and phishing.
Learn more: DMARC/DKIM/SPF Overview