If your site verification or cookie scan fails with an HTTP 403 error, it usually means your firewall or bot protection is blocking requests from Kukie.io servers. This guide explains why this happens and how to fix it.

Why This Happens

Kukie.io verification and scanning work by making HTTP requests from our servers to your website. Firewalls, Web Application Firewalls (WAFs), and bot protection services may block these requests because they come from an automated source rather than a regular browser.

Common services that may block our requests:

• Cloudflare — Bot Fight Mode, Managed Challenges, or country-based blocking rules
• Sucuri — WAF with bot protection
• Wordfence — WordPress firewall with rate limiting and bot blocking
• Hosting-level firewalls — ModSecurity, server firewalls, or IP-based blocking

Our servers use IP address 46.62.206.36 and User-Agent KukieBot/1.0.

Your Banner Still Works

The cookie banner loads client-side in your visitors' browsers — not from Kukie.io servers. Blocking our server IP only affects verification and scanning. Your banner will continue to work perfectly for all your visitors.

Verification and scanning are server-side tools that help you confirm your installation and discover cookies. They are optional features that do not affect banner functionality.

Fix for Cloudflare

1. Log in to your Cloudflare dashboard.
2. Select your domain and go to Security → WAF → Custom Rules.
3. Click Create rule.
4. Set rule name to Kukie Cookie Consent.
5. Set the expression to: (ip.src eq 46.62.206.36)
6. Set the action to Skip and select all WAF components to skip.
7. Make sure this rule is above any blocking rules in the list.
8. Save and deploy the rule.
9. Return to Kukie.io and retry verification or scanning.

Tip: If you also use Cloudflare's Bot Fight Mode, you may need to create a separate rule for the User-Agent: (http.user_agent contains "KukieBot") with action Skip.

Fix for Sucuri

1. Log in to the Sucuri dashboard.
2. Go to Firewall → Settings → Whitelisting.
3. Add IP address 46.62.206.36 to the whitelist.
4. Save changes and retry verification or scanning in Kukie.io.

Fix for Wordfence

1. In your WordPress admin, go to Wordfence → Firewall → Blocking.
2. Check that IP 46.62.206.36 is not in any block list.
3. Go to Wordfence → Firewall → Rate Limiting.
4. Under "Whitelisted IP addresses", add 46.62.206.36.
5. Save changes and retry.

Fix for Hosting-Level Protection

If your hosting provider has server-level bot protection or a firewall:

• Contact your hosting support and ask them to whitelist IP 46.62.206.36.
• Alternatively, ask them to whitelist User-Agent KukieBot/1.0.

Still Not Working?

If you've whitelisted our IP and the issue persists:

• Check that your site is publicly accessible (not behind basic auth or maintenance mode).
• Make sure your domain resolves correctly (no DNS issues).
• Contact us at support@kukie.io with your domain name and we'll help diagnose the issue.

Related Articles

• How to Verify Your Banner Installation
• Kukie.io Server IP Addresses