{"id":6569,"date":"2022-10-28T12:07:50","date_gmt":"2022-10-28T09:07:50","guid":{"rendered":"https:\/\/support.withsecure.com\/?post_type=announcement&p=6569"},"modified":"2026-10-19T13:06:04","modified_gmt":"2026-10-19T10:06:04","slug":"changes-in-internet-domains-for-withsecure-elements","status":"publish","type":"announcement","link":"https:\/\/support.withsecure.com\/fi\/announcements\/changes-in-internet-domains-for-withsecure-elements\/","title":{"rendered":"Changes in internet domains for WithSecure\u2122 Elements"},"content":{"rendered":"

UPDATE 2024-06-18:<\/strong> Updated to include api-global.elements.withsecure.com<\/p>\n

UPDATE 2023-05-25: <\/strong>Article updated with rdr.elements.withsecure.com and login.withsecure.com<\/p>\n

UPDATE 2023-01-11:<\/strong> Article updated to reflect that the changes have now happened, and a new secton on required internet domains that need to be allowed.<\/p>\n

As you are probably aware, F-Secure Business has become WithSecure\u2122<\/a>.<\/p>\n

For the first few months, we have maintained the WithSecure\u2122 Elements system using the elements.f-secure.com domain, and redirects to the portal at elements.f-secure.com.<\/p>\n

Now we are taking the next step towards moving all the services to the withsecure.com domain.<\/p>\n

Web Portal Changes<\/strong><\/h2>\n

From November 2nd 2022, we will change to be a dedicated address, no longer redirecting to the elements.f-secure.com hosted portal. This means that there will be two portals running side-by-side during the transition period, and this will allow us to monitor the service with the new domain name while keeping the existing service fully available. Users would be able to access elements via either portal, maintaining all functionality. The changes also include the URLs that are used as part of authentication, which are accessed during the login process.<\/p>\n

Later in November, we will change elements.f-secure.com to redirect to the new , leaving only one physical portal accessible by both names for convenience.<\/p>\n

Later still, we will retire the elements.f-secure.com address and all other portal URLs under f-secure.com, meaning all access will need to be made via the address.<\/p>\n

Impact and user actions<\/h3>\n

We are advising our users to start using at the earliest opportunity. This will help us monitor the transition, and help us ensure that every part of the Elements system is working correctly after the changes.<\/p>\n

Users should update any bookmarks they have towards Elements, to use the new address instead of the old one.<\/p>\n

In addition, any saved passwords in a password manager should also be updated to use the new authentication address, accounts.withsecure.com<\/strong>. This will help the user to continue accessing the Elements portal after the changes are made. Please note that usernames and passwords are not affected by these changes, but most password managers will have linked these to authentication URLs.<\/p>\n

In addition to these end-user changes, we advise organizations that filter or block web traffic to allow access to withsecure.com and any subdomains thereof, in addition to the existing f-secure.com addresses.<\/p>\n

Additional information<\/h3>\n

There are no changes currently planned for the underlying APIs used by our products. These will continue as they are currently.<\/p>\n

Please Note: <\/strong>If a logged-in user switches between the elements.f-secure.com and elements.withsecure.com addresses, they will need to log in again. This is because the login status is based on the domain logged into, and this is by design for security reasons.<\/p>\n

\u00a0<\/p>\n

Email Changes<\/strong><\/h2>\n

In line with the web changes, we are also changing over the email send addresses for Elements related mails. These will now start to come from @withsecure.com email addresses. The changes are happening gradually, with some parts of Elements already using them, and we expect all Elements mails to come from @withsecure.com in the near future.<\/p>\n

Impact and user actions<\/h3>\n

Users are advised to whitelist @withsecure.com in their email clients, to ensure that emails end up in the user\u2019s mailboxes. <\/p>\n

Organizations that filter emails at the mail-server are advised to also whitelist @withsecure.com for the same reason.<\/p>\n

Required internet domains for access<\/h2>\n

If you have web access controls in place in your environment, please note that you will need to allow traffic to the following domain addresses:<\/p>\n