Client error · 403

403 Forbidden

A 403 Forbidden means the server knows what you asked for and will not serve it. Authentication will not change the answer unless the refusal was specifically “this user is not allowed.”

HTTP status codes explained · the longer reference on the blog.

What 403 means

The request arrived and was parsed. A rule then denied it: file permissions, a directory index ban, an IP or country block, a hotlink rule, a missing index file with autoindex off, or an application check that the current user may not see this resource. The HTTP status is the denial. The HTML page around it is whoever generated it — your app, nginx, or a CDN.

A 403 on a URL that should be private is normal. A 403 on your homepage, pricing page, or public API is a bug or a block. Visitors can reach the server, so this is different from a connection timeout or a DNS failure. Search engines that receive 403 on a URL will not index that URL.

Common causes

  • File or directory permissions

    The web user cannot read the file, or cannot traverse a parent directory. Static hosts and nginx then answer 403. A deploy that resets ownership to root is a common trigger.

  • Index listing is disabled and there is no index file

    Requesting a folder such as /assets/ with autoindex off, and no index.html, returns 403 on nginx and some Apache setups. The files inside the folder can still exist.

  • A WAF, bot rule, or IP block

    Cloudflare, ModSecurity, or a host firewall can forbid a user agent, a country, or a datacenter IP range. The homepage checker identifies itself as UptimeGuard/1.0. Scheduled monitors identify themselves as ismysiteup/1.0. A rule that blocks unknown agents will 403 those checks while a normal browser still loads.

  • Application authorization

    The user is signed in, and the app decided this account cannot view the resource. That is a product rule, not a downed server. A mis-scoped rule can forbid every account, including anonymous visitors to a public page.

How to fix it

  • Read which layer wrote the page

    The HTML title and footer usually name nginx, Apache, Cloudflare, or your app. Fix that layer. An app 403 will show in application logs. A proxy 403 often will not.

  • Check permissions on the file and every parent directory

    The worker account needs execute on each directory in the path and read on the file. Compare a URL that works with the one that returns 403.

  • Review WAF events and user-agent rules

    If browsers succeed and the checker returns 403, find the rule that matched the checker’s user agent or IP. Allow the check if the URL is meant to be public. Keep the rule if the URL is meant to stay private.

  • Confirm the public routes are excluded from authz

    After a deploy, test the homepage, a static asset, and the health URL while signed out. A single middleware change can forbid all of them.

Is it your site, or just you?

Try the URL signed out, in a private window, and on a phone using cellular data. A 403 that only happens on your office network is a local allow-list or a VPN policy. A 403 everywhere is the site.

Run the homepage checker. It uses a different network and user agent than your browser. If both see 403, visitors are being refused. If only one sees 403, compare user agent, country, and IP rules before you treat the host as down.

How to monitor for 403

Monitor the public URL and expect 200. A 403 fails that check after a second consecutive failure, which is what you want for a homepage that suddenly refuses everyone. If a WAF blocks only the monitor, the alert is real for that checker and may be a false alarm for browsers — confirm in a private window, then adjust the firewall rule.

The checker on the ismysiteup homepage requests the URL from our servers and shows the HTTP status, response time, and SSL details. No account is required, and that checker allows 5 checks per hour from the same network. A free account watches 5 URLs, each checked every 10 minutes, and sends alerts on WhatsApp, Telegram, Slack, or email. A monitor expects HTTP 200 unless you set a different expected status (100–599). One failed check is confirmed with a second check before the first alert, and a later success sends a recovery alert. Pro (every 5 minutes) and Business (every minute) are listed on the pricing page; paid checkout is not open yet.

Compare Free, Pro, and Business

Related status codes

FAQ

Does 403 mean my website is down?

The server is responding, so the host is not offline. For a URL that should be public, visitors are still locked out, and that URL is effectively down until the rule or permission is fixed.

Why do I see 403 when the site works in my browser?

Your browser sends cookies and a normal user agent. A checker, a search crawler, or a visitor in another country may hit a different rule. Compare a private window and the homepage checker.

Should I set the expected status to 403?

Only for a URL that is supposed to forbid anonymous access and where you want that refusal to count as up. For a public page, leave the expected status at 200 so a 403 alerts you.