DeepL is planning to change the URL for logged-in users. These users will automatically be redirected to app.deepl.com. Public access will remain on www.deepl.com.
For most users, no action is required. However, if your organization controls network access to DeepL, you will need to update your configuration to avoid disruption.
This article is relevant for IT admins who manage allow lists or block lists for DeepL in their company's network.
Who is affected
You may need to take action if your organization does one of the following:
- Allow specific DeepL URLs to control which services employees can access
- Block DeepL pages to prevent employees from using DeepL without logging in. For more information see this article.
If neither applies, no action is needed.
If you allow-list DeepL URLs
As an IT admin, ensure uninterrupted access for logged-in users by updating your allow list before the end of April.
- If you already use a wildcard rule, like *.deepl.com, no action is needed because app.deepl.com is already covered.
- If you allow specific URLs, update your allow list as follows:
- Add app.deepl.com
- If your organization uses a custom domain, add *.app.deepl.com.
The full list of URLs that need to be allowed is provided below.
www.deepl.com
app.deepl.com
*.app.deepl.com (wildcard to cover your organization’s custom subdomain)
api.deepl.com
auth.deepl.com
sso.deepl.com
*.sso.deepl.comIf you block DeepL pages
If you currently block DeepL pages to prevent anonymous access, your existing block rules remain valid and do not need to change.
To ensure that logged-in users can access DeepL after the URL update:
- Keep your current block rules in place
- Additionally, allow the following URLs:
app.deepl.com
*.app.deepl.com (wildcard to cover your organization’s custom subdomain)
api.deepl.com
auth.deepl.com
sso.deepl.com
*.sso.deepl.com