A 403 “Forbidden” error typically means that your connection to Claim.MD was blocked for security reasons. This is not usually an issue with your account or login credentials. Instead, it is most often related to how your internet traffic is being routed at the time you try to access the site.
Below are the most common causes and what you can do if it happens again.
Common Causes of a 403 Error
1. Accessing Claim.MD from Outside the United States
Claim.MD blocks traffic from certain countries for security purposes.
If you are:
Traveling internationally
Working remotely from outside the U.S.
Using an internet provider that routes your connection through another country
you may receive a 403 “Forbidden” message.
Even if you are physically located in the United States, some internet connections may temporarily route traffic through international networks, which can also trigger this block.
2. Using a VPN or “Secure Connection” Service
Virtual Private Networks (VPNs) and similar security tools are another common cause.
Examples include:
NordVPN
ExpressVPN
Workplace or corporate VPNs
Privacy or “secure browsing” apps on your laptop or phone
Some VPN services route traffic through shared networks that may also be used for malicious activity. When this happens, those networks may be blocked from accessing Claim.MD, resulting in a 403 error.
3. Too Many or Outdated Browser Cookies
In some cases, having too many old or outdated cookies stored in your browser can trigger a 403 error.
This can typically be resolved by clearing your browser’s cookies specifically for:
After clearing the cookies, close and reopen your browser before attempting to log in again.
4. API Request Limits (For API Users)
If you are accessing Claim.MD via the API, a 403 error may occur if too many requests are being made within a short period of time.
Exceeding the allowed number of requests per minute can trigger security protections that temporarily block access. If this occurs, reduce the request frequency and retry after a brief pause.
What If the Error Went Away?
If the issue resolved on its own, it was likely temporary and related to how your connection was routed at that moment. This can happen if:
Your VPN connection changed servers
Your ISP reassigned your IP address
A temporary routing issue corrected itself
No further action is needed unless the error returns.
What Should I Do If I See the 403 Error Again?
If the error happens again, please try the following steps:
Turn off any VPN or “secure connection” app and try accessing Claim.MD again.
If you are on an office or corporate network, contact your local IT support team and ask them to:
Confirm that no VPN, third-party security apps, filters, or firewalls are intercepting or rerouting traffic.
Verify how your traffic is being routed to Claim.MD.
What Information Should I Share If the Issue Continues?
If the problem persists, please gather and share the following details with us:
The exact time and date the error occurred
The IP address being used at the time
Whether a VPN or security tool was enabled (and which one)
A screenshot of the error message
With that information, we’ll be happy to investigate further from our side and help resolve the issue as quickly as possible.