SAFE WEBSITE MONITORING
Helping Regal Pulse access your website
Regal Pulse needs to reach your website to check it. A firewall, bot protection service or sign-in page can get in the way even when your website is working normally for visitors.
Start with the latest result
Open the affected scan or journey and check its message, time and page address. If the result includes response details or a screenshot, use them to see where the check stopped.
- Green — Accessible. The latest evidence shows that Pulse could reach what it checked.
- Amber — Limited or not confirmed. Some information may be missing, a rate limit may have applied, or there may be no result yet.
- Red — Restricted. A check recorded a block, challenge or sign-in requirement.
Is the website down, or was access restricted?
- Firewall or bot challenge: Compare the time and page address with the event in your security logs.
- Rate limit: Check your logs and wait before retrying. Repeated tests can make the limit harder to diagnose.
- Sign-in page: Check whether a redirect took Pulse to a protected page.
- Timeout or connection error: Try the same page in a normal browser and check your hosting logs. If visitors cannot reach it either, investigate a possible outage.
Review your website security settings
Your developer, host or security provider can help identify the matching event. Look for RegalPulse-Scan, RegalPulse-Journey or RegalPulse-Uptime in request logs. These labels help find requests and can be copied. They do not prove who sent a request.
If you manage the website and need an exception, limit it to the specific rule and public read-only paths you want to scan. Keep sign-in, account, checkout, payment and admin routes protected. Keep the rest of your firewall and rate limits enabled. Pulse does not publish a fixed outbound IP range for allowlisting. Review the result after any change and remove exceptions that are no longer needed.
Test a journey or a form protected by CAPTCHA
Pulse reports a security challenge that stops a check. For a website you control, use a staging site, a test form and a test destination. Check your provider’s guidance on testing Cloudflare Turnstile or testing Google reCAPTCHA. Keep production keys and protections in place on your live site. If the challenge still stops the journey, treat that step as unverified.
Still having trouble?
Ask Pulse about scanning access from your dashboard, or contact support with the result link, time, page address and exact message. Keep passwords, API keys and other credentials private.
