Scanner Access & Hosting Challenges

Confirm what failed

A CAPTCHA, challenge page, access-denied response or hosting log can support an access-block diagnosis. Zero cookies alone cannot: the site may genuinely set none in that scan context.

Collect bounded evidence

Record the public test URL, scan time/timezone, returned status and visible challenge. Compare with the hosting provider's logs. Do not send customer credentials or visitor data.

Ask for a narrow remedy

Ask hosting support whether the specific observed request was blocked and what minimal rule would permit the authorised scan. Keep other security checks active.

ConsentEase does not currently provide a confirmed fixed-egress IP guarantee. Do not copy an old hard-coded address as a permanent allowlist, bypass all WAF checks, or allow every unfamiliar bot. Request current operational guidance if a provider requires an exact address.

Manual inventory meanwhile

Use a clean browser context; inspect representative routes before a choice and in separate reject/accept/custom contexts. Record cookie domain/path/duration, provider purpose and request behaviour. Include relevant interactions and login/checkout states when authorised.

Manual findings are scoped observations, not continuous coverage or a declaration of legal compliance. Review/classify entries before updating notices.