What it means
Following one of your entry points, we either came back to an address we had already visited or passed ten redirects without reaching a page. Browsers give up in the same way and show an error such as "too many redirects". The detail names the entry points that loop.
Why it matters
Visitors who start from that address never see your site, and search engines stop crawling it. Loops usually come from two systems that each think they own the redirect: for example a CDN that sends HTTP to HTTPS while the origin server, seeing plain HTTP from the CDN, sends it back. Another common cause is a www rule and an apex rule that point at each other.
How to fix it
- Open the redirect chain in the result and note where it starts repeating.
- Decide on one final address, such as
https://www.example.com/, and make every rule point straight at it. - If a CDN or proxy terminates HTTPS, set it to connect to your server over HTTPS too (Cloudflare calls this
Full or Full (strict)), or make the origin trust the
X-Forwarded-Protoheader instead of redirecting. - Remove duplicate rules: keep the redirect in one place, either the CDN, the web server or the application.
Check it worked
Run the HTTP and security headers check again. Each entry point should end on a page with a 200 status after one or two redirects, and the finding should be gone.