HTTP 440 Login Time-out means your login session has expired and you need to sign in again. It isn't part of the official HTTP standard. It's a code Microsoft uses, mostly in:
- Outlook on the web (OWA) and the Exchange admin center (ECP) on Exchange Server;
- IIS web applications that use forms-based login.
If you're a user: sign in again. If you're sent straight back to the login page, or keep seeing 440 right after signing in, try these in order:
- Close all tabs for the site and open it again in a new window.
- Clear cookies for that site (or try a private window).
- Check that your computer's date and time are correct.
If it still loops, the problem is on the server. The rest of this guide is for the administrator.
1. Exchange: OWA or ECP login loop with 440
When every user gets 440 or a login loop on OWA and ECP at the same time, the most common cause on Exchange Server is an expired Exchange Server Auth Certificate. Exchange uses it to sign authentication tokens. When it expires, sign-in to OWA and ECP breaks.
Check it in the Exchange Management Shell:
# Thumbprint of the certificate Exchange uses for authentication
Get-AuthConfig | Format-List CurrentCertificateThumbprint
# Its expiry date
Get-ExchangeCertificate -Thumbprint <thumbprint> | Format-List Subject, NotAfter
If NotAfter is in the past (or the certificate is missing), renew it. The steps, in short:
# 1. Create a new Auth certificate
New-ExchangeCertificate -KeySize 2048 -PrivateKeyExportable $true -SubjectName "cn=Microsoft Exchange Server Auth Certificate" -FriendlyName "Microsoft Exchange Server Auth Certificate" -DomainName @()
# 2. Make it the Auth certificate, effective now
Set-AuthConfig -NewCertificateThumbprint <new-thumbprint> -NewCertificateEffectiveDate (Get-Date)
Set-AuthConfig -PublishCertificate
Set-AuthConfig -ClearPreviousCertificate
# 3. Restart the OWA and ECP app pools
Restart-WebAppPool MSExchangeOWAAppPool
Restart-WebAppPool MSExchangeECPAppPool
Follow Microsoft's documentation for renewing the Exchange Server Auth Certificate for your Exchange version. It covers hybrid setups, which need extra steps. Microsoft also publishes a script that checks the Auth certificate and can renew it automatically.
Other Exchange causes worth checking when the certificate is fine:
- Authentication settings changed on the OWA or ECP virtual directories (for example, forms-based authentication switched off on one server but not another).
- A recent Cumulative Update or Security Update didn't finish. Check the setup logs and rerun it if needed.
- Time difference between servers in a multi-server setup.
2. Your own IIS application returns 440
If you run an ASP.NET application on IIS, 440 appears when the login session has expired and the app or IIS returns that code. Typical causes:
| Cause | What to check |
|---|---|
| Session timeout too short | sessionState timeout and forms timeout in web.config |
| Login cookie not refreshed on activity | slidingExpiration="true" on forms authentication |
| Several servers behind a load balancer with different machine keys | All servers must share the same machineKey so they can read each other's login cookies |
| Session kept in server memory, load balancer moves users between servers | Store sessions centrally (SQL Server or Redis) or enable session affinity |
| App pool recycled, wiping in-memory sessions | Move sessions out of process, or review the recycling schedule |
A typical web.config adjustment:
<system.web>
<sessionState timeout="60" />
<authentication mode="Forms">
<forms timeout="60" slidingExpiration="true" />
</authentication>
</system.web>
3. How 440 relates to other codes
| Code | Meaning |
|---|---|
| 401 Unauthorized | Not signed in, or the credentials were rejected (standard HTTP) |
| 403 Forbidden | Signed in, but not allowed to see this |
| 440 Login Time-out | Was signed in, but the session expired (Microsoft) |
| 419 (Laravel), 498 | Other non-standard "session or token expired" codes used by some frameworks |
For the standard codes, see HTTP 4xx and 5xx error codes explained.
4. Monitoring Outlook on the web
If you monitor OWA's login page, a 440 or a redirect to the login page is normal for an anonymous check. That makes it a poor health signal. Exchange provides health check pages for each service that return 200 OK when the service is healthy, for example:
https://mail.example.com/owa/healthcheck.htm
https://mail.example.com/ecp/healthcheck.htm
With Pingzo, point an HTTP monitor at those pages. Pingzo checks every 1 to 15 minutes depending on your plan, opens an incident when 3 of the last 5 checks fail, and alerts you on WhatsApp, Slack, Telegram, Discord or email. On paid plans it also warns you before your site's SSL certificate expires. (It can't see Exchange's internal Auth certificate, so keep an eye on that one with Microsoft's script.)
Related guides
- HTTP 4xx and 5xx error codes explained
- HTTP 503 Service Unavailable: causes and fixes
- SSL certificate monitoring guide
Stop Finding Out About Outages from Angry Users
Get instant WhatsApp & Discord alerts the second your API, website, or server goes down. Setup in 30 seconds, with checks as often as every minute.