I was wondering why new models weren’t being added to Cursor, so I looked into it. It turns out that even though I have Norton 360 installed, Cursor’s traffic was apparently flagged as suspicious and blocked.
I fixed the issue by excluding
*.cursor.sh
*.cursorapi.com
*.cursor-cdn.com
from the “Safe Web” settings.
Hey, thanks for the detailed write-up. Great self-diagnosis. You’re right: when a security suite like Norton Safe Web or a URL filter intercepts HTTPS traffic, requests to the Cursor backend can silently fail, and the model catalog just won’t refresh. The symptom new models don’t show up matches this perfectly.
Your fix via exclusions is the right approach. For completeness, add a few more domains to the allowlist so no requests are still being intercepted:
*.cursor.sh
*.cursorapi.com
*.cursor-cdn.com
*.cursor.com
If something gets blocked again, you can quickly check via Cursor Settings > Network > Run Diagnostics. It’ll show which endpoints aren’t getting through.
This comes up with antivirus tools not for the first time like Norton, Bitdefender, and Avast, so this report is useful for anyone googling the same issue. Let me know if the models still don’t load after the allowlist.