Dot Brand Frequently Asked Questions With a .BRAND TLD Owner
Make an inquiry
All fields marked with * are required.
Join CSC’s .BRAND product manager, Anne-Mette Roed, and guest speaker, Ian Semey of SaxoBank—a Danish fintech company that owns and uses .SAXO as its primary domain—for this webinar on .BRAND top-level domain ownership.
In this session, Anne-Mette and Ian discuss the practicalities of .BRAND TLD ownership, and answer some of the most frequently asked questions we encounter about .BRAND TLDs.
Topics include:
Getting internal buy-in for a .BRAND TLD
Creating a .BRAND strategy
Potential impact on SEO
Effect on fraud and infringement incidents
Real-life use cases
Webinar transcript
Disclaimer: Please be advised that this recorded webinar has been edited from its original format, which may have included a product demo and other engagement features. To set up a live demo, please complete the form above on our website. If you currently are not on our website and are watching this on our YouTube channel, there's a link to the website in the description of this video. Thank you.
Annie: Hello, everyone, and welcome to today's webinar, "Dot Brand Frequently Asked Questions with a .Brand TLD Owner." My name is Annie Triboletti. I will be kicking things off as your moderator today.
So joining us today are Anne-Mette Roed and Ian Peter Semey. Anne-Mette is CSC's product manager for dot brand, and Ian is Saxo Bank's digital development and domain registration manager. So with that, I would like to welcome in Anne-Mette and Ian.
Ian: Thank you.
Anne-Mette: So thank you very much. So today in this session here, what we will be covering is to have one step back into Round number 1 from 2012. We'll be looking into Round 2 coming up. Then we want to look a bit about what is a .brand, then cover some of the most commonly asked questions to .brand TLD owners. Then we have Ian here today to share some of the Dot sector use cases, and then just round it all up with some of the key dates for Round 2.
So I think it's important just to start out with taking one step back and looking at what was happening with what is called Round 1 back to 2012. So in 2012, ICANN allowed companies and brand owners to apply for the top-level extension in a time-limited window. This is what we refer to as Round number 1.
Back then, ICANN received 1,930 applications. Out of those, 1,409 were unique strings. So as an example, there were 11 applications for .app. Thirty-three percent of those were also dot brand strings. And a dot brand string is when you look to the right of the dot, then you have your company name. And some of the dot brand string applied in Round 1 is .Microsoft, .Apple, .Saxo as an example.
When you look at the overview here to the right, you will see that the business sector that applied in Round 2 (sic) was the majority from the banking and financial institutions as well as the technology. ICANN did say, back in 2012, that if you don't apply in Round 1, a Round 2 will be coming up just around the corner in 2014. That never happened. So studies, assessments, and policy development work has been going on for the last 12 years.
Some of the reasons behind this New gTLD Program for ICANN was to enable some competition because already back then .com was not easy to get domain names under because it was already filled up. And the idea here was that the consumer choice could be bigger by having addresses you could have for your own TLD.
So now ICANN announced a second round to come up. So they announced the second round will open in April of 2026. And again, companies can apply for a top-level domain in a time-limited window. Right now, ICANN is pending to confirm whether that will be 12 or it will be 15 weeks.
The current timeline will then allow top-level domain owners to be delegated in 2027. So that means where you can start utilizing your top-level domain. There will both be open TLDs that will be coming in and .brand TLDs. There can be community TLDs. Any kind of companies who apply for their own top-level extension can attend the program. There is a fee to ICANN for the application itself, which is $227,500 for one application.
The difference, if we look at from back in 2012 to the second round now, is that ICANN has spent much more time on communicating about the opening of the second round. So ICANN has set up a new website. But what they also have done, they have generated some reports looking into the big opportunity there is for brand owners to unlock this value and tackle some key online challenges by applying for a branded TLD.
So what ICANN did, they surveyed more than 2,000 marketing directors to better understand the online priorities and challenges and trends going on today. And some of the key priorities that came out of that report is that it's important for brand awareness and visibility, improve customer retention and loyalty. There are some expanding into new markets, some data and analytics as well as adopting new technologies.
So some of the core business challenges that these 2,000 companies were facing is about standing out from competitors. It's about attracting and engaging the right audience, as well as keeping up with the digital trends going on, such as where AI and data privacy and security as a major trend playing. The full report can be downloaded in our Resources area here if you would like to see the full results of that. But basically, the second round here is opening it up for companies to apply for their own top-level extension.
So let's look at what a .brand is and how it actually works. So I always like to visualize this a bit like looking at it from a building perspective.
So if you look at the left-hand side here, we look at the example of the registry .com, which is owned by VeriSign. So imagine that when you want to register a .com domain name, anybody can go in and actually rent like a window here and register a domain name. It can be a domain name that includes some of your product names. It could be generic domain names. But basically that is owned by VeriSign, who set the rules and regulations for the domain registrations.
Looking at it to the right-hand side here, owning a .brand. So owning the TLD itself means you suddenly own the full building. That gives you a lot of advantages in regards to security, branding, marketing, etc. The part here is that it will only be your company who can register within the .brand. So that's also a very strong message to give to market that it's a safe and secure place, for example if you use it for portal usage, etc.
So another thing that is important to understand is that when you own the full building here, then you're suddenly capable of implementing different security factors. For example, for email security, you can add DMARC at the root of the house, and then it goes down to all domain registrations under the .brand. The difference is that if you wanted to add a DMARC record to a domain under .com, you had to go to the specific domain itself. So that's one example.
The other example is also you can add SSL pre-validation on the top of the building. Again, that prevalidates certificates in the whole house. And additional features also about HTTPS. You can have that preloaded list into HTTP, and that means that you have the HTTPS in web browsers as a guarantee.
So there are many security perspectives seeing it from a branding and marketing perspective as well. You can register short and memorable domain names. So the part here is that owning the building, you can register the domain names by adding any names to the left of the dot. So that could be home.brand. It could be service.brand. It could be our.brand. So that's one of the short parts you can use as well. So short and memorable domain names are able to be registered when you own your own .brand.
So I think we have Ian here on the call. Maybe, Ian, you have some kind of experience as well you want to share when we look at this building picture here?
Ian: Yes. When I started looking at it, it was also a little bit difficult for me to understand actually what is the issue of this. And just to take an example, I think it was earlier this year that there was a registry for our Vietnamese domain names that suddenly changed the rules. And the issue there is that before we didn't need to prove to the registry that we were a company, but suddenly we had to provide documentation approved by a notar. We had to send our CEO or somebody at that level to the local office, and imagine that had to be done within a limited time frame. So try to visualize having your CEO, who is not very easy to contact, and need to understand why it is important for him or her to be present at a local lawyer office nearby to actually sign this.
And that is what can happen when you have your domain owned by somebody else. Like VeriSign can change their rules and say, "Okay, you need to prove that you are a company if you are using that." But owning it makes you definitely set the rules, who can apply and not.
Anne-Mette: Thank you very much, Ian. So I think what I want to do now is move forward with some of the commonly asked questions now we know where how a .brand works. And then I think sometimes some of the questions that come up about owning a .brand TLD could be some of these we have been gathering over time. So the benefit of having Ian here, my idea was that I wanted to ask a few questions to you, Ian, here and then get your feedback on that.
So if we start out here asking the question around which stakeholders were involved in the decision to apply for your .saxo TLD, can you remember? I know this is back in time. It goes back to 2012. But can you remember which departments were involved in this part?
Ian: Well, actually, I can say for sure that marketing was involved because I was and I am part of marketing. But now that I have been involved in trying to get our email domain changed, I can say that it has to be or it has been IT security. It's the brand governance. It's everybody who actually has a stake in what is the company name. So also legal. It's also the people that manage the trademarks. So there's a lot of touchpoints in the company.
Anne-Mette: Thank you for that one. So how did you choose the string of your TLD? So what were the considerations around choosing .saxo as the top-level domain?
Ian: .saxo, the reason, it was a very clear reason because we had to secure it. We wanted to go with the .com version of our company name, but it turned out that it was taken, and it was too expensive to pay them out to get that. So we have grown into this being just the right naming for our company.
Anne-Mette: So did you have a clear strategy when you were applying for this top-level domain, or was it something you developed over time?
Ian: Well, I think it's both. I know that CSC has assisted us in seeing the advantages of this. But of course, it's also something that you know when you think about what should your branding be online, what should the name of your company be. And everybody knows that short, memorable names are easier for everybody to understand and follow. So that's a clear strategy. And then we try to, as much as possible, ensure that everybody follows this rule.
Anne-Mette: So how did you get the internal buy-in for applying for the .brand TLD?
Ian: I think it started very clearly with suddenly an opportunity opening up, and then the legal department were on board. And then it was actually the CEOs that decided, okay, we need to do something because we didn't have the opportunity that we actually wanted. And it's a difficult one. I know. It depends very much on the size of the company. But it's something that you really need to ensure.
Anne-Mette: Thank you. So I think many times people are worrying about how to do the application to ICANN because it sounds like it's a very heavy process in general. Did you get any help with the ICANN application process?
Ian: Yes, of course. We are a bank, and we don't do domains. And what this is, is buying the right to create domain names like a registry. So because this is not our business, we need somebody that actually can make it easy to do. So therefore, ensuring that everything is in place to get the right paperwork, that was done with the help of CSC. And you need somebody to help you, or you are a domain registry before this.
Anne-Mette: Thank you. And then I think one of the questions that very often comes up when you are owning a .brand already, are you considering applying for more brands in the future?
Ian: It can very well be. But it, of course, depends on are you buying a different company, and do you want to expand with that brand? Or do you want to continue just with the brand naming? So it's a little bit of what are the plans. And of course, I don't know the plans that we have going, like, three years out. I don't know. Everything can happen in these day and times, isn't it?
Anne-Mette: Absolutely. And I think for some company owners as well, it's more like finding the overall company to apply for and then registering maybe your sub-companies as the domain name, instead of having every single organization's brand name registered as a TLD. So thinking more like you can register your main brand and then have your brand names under the umbrella of your main brand as an example.
Ian: Yes, yes. That makes it a logical structure. And I think for everybody to make sense of it, it needs to be a logical structure like that.
Anne-Mette: Yeah, thank you. So covering that part, then I think we need to look at some of the most commonly asked questions when you actually own a .brand. Benefit of having you here on the call here today as well. We're really appreciating that. So looking into now when you own a .brand, these are some of the common questions that we are receiving. So do you have a domain strategy in place for your .brand TLD today?
Ian: Yes, and there's always room for people wanting to have new names and going off on tangents and wanting to register domains on what they normally know as something that is nice. And we need to be sure that they reuse the money that is already invested in this .brand and add to the branding and the value that it has.
Anne-Mette: So have you put your domain strategy together with your open extensions, together with your .brand in one strategy so that supports you as operationally?
Ian: Yes. When we went out and started the company, or sorry using .saxo, we needed to find out, okay, what should the optimal domain be? And you helped us with having a survey because you had contacts and helping other companies using these .brand domains. So you helped us showing what was the most normal usage out there. Then we chose one of these. But it's also a matter of trying to make sense of what does make sense for your clients, your users, your prospects. That's the most important thing.
Anne-Mette: So has your .brand TLD provided you any new ways to use domains for products and campaigns? Now we have been touching a bit around marketing. Are there new ways of utilizing the .brand TLD compared to any open TLD extension, like .com and .dk and .se, as an example?
Ian: I'm not totally sure what you're pointing to, if that is the shortening URLs, or is it the infringing?
Anne-Mette: No. So it's more like whether you .brand TLD has provided you new ways to use domains for products and campaigns.
Ian: Ah, yes.
Anne-Mette: So the thing about if you have a product name, then you could be challenged that that product name is already taken by somebody else on the .com.
Ian: Yes, yes.
Anne-Mette: So does it give you any kind of flexibility, or have you seen any change on that front?
Ian: Yes, of course, because the names are not taking like a product or Forex or something that is very common. In this case, it's the financial industry. But it can be anything. It can be go to. It can be like one of the cases that we have. You can type the name that you are selling, and then because you own the top level, you can actually create that as a domain. And if you need to do that and buy this like a book or something that is short, it will be very expensive to do that. So having this possibility, yeah, gives us the possibility to create these kind of euros. Yes.
Anne-Mette: Okay. Great. Thanks, Ian. So have you seen any change in behavior from any infringers since the implementation of .saxo? So I don't know if you have seen any change in their behavior or if you have noticed anything there.
Ian: Yeah, because we are on .saxo now, they can't use that one, and they have to use something that is quite different. So it's easier to spot a site that doesn't belong to us. It's not that it's still a battle because people are not always looking at what is the domain name, especially on the phone. People are trying to hide it. But definitely we are using less money on having to buy similar domains as compared to what we did before.
Anne-Mette: Okay. I think that's a very important statement for many because that is one of the areas where it can be a real good benefit of adding a .brand TLD. So thank you for sharing. So does a .brand TLD work with AI? Are there any benefits? Have you seen anything? What is your experience on the AI part? I know this is the new thing, but you might have some experience you want to share.
Ian: Yes. Yeah, we are, of course, trying to leverage that we have this .brand and trying to create content that is targeted for AI. So we have I think it is about 80,000 articles that are kind of being a source of content. Recently, we also have launched a website or a portion of a website with the different instruments, that is just recently we did that. So when people search for stock in this case, they will be able to find a description of the stock and at the latest price that we offer. So that's about 6,000 pages. And things like that, you need to do, and there's no problem in doing it. But of course, it's not easy, and there's a lot of work to do it, just the same as with the keywords and other SEO work. Yes.
Anne-Mette: Thanks. So will a .brand domain rank in the Google organic results? I did a quick look, and I saw that the Google organic results for home.saxo ranks as the first one and for the keyword Saxo. And then we also saw that the AI overview result ranks first for the term "who is Saxo." So it documents that it works. But do you have any other experience you want to share on the organic part here?
Ian: Yeah, we can take an example of one of the sites that I'm going to talk a little bit about. I typed help.saxo and then I misspelled Saxo, and still it turned out, together with our competitor that has the saxo.com. But our result was on top of this. So yeah, of course. And also because Google is also a .brand. So of course, they also know what it is.
Anne-Mette: Thank you. So another question that comes up very often is about when you use a .brand TLD, is there any impact on SEO? And I think, overall, we all know that a keyword-rich domain name is needed for the SEO, and that is what a .brand can deliver because it will be shorter because there's no other extension like a .com for various and etc. But do you have any kind of experience you want to share how you have been managing the SEO under the domain registration for .saxo or any good advice you want to share here with the audience?
Ian: Yes. So of course . . . Well, I will say, when we did this, then we were prepared in the way that we had a redirection from the old pages to the new pages, and we also did a cleanup. It's always good to use an opportunity like this to do a cleanup and try to remove old stuff and content. But then we ensured that most of the main pages, they are redirected. And at that time, it actually took a hit, of course. Google penalized at that time, when there was a redirection, because a lot of people were doing redirects with redirects with redirects. What you need to do is make an assessment and see what is the potential impact, and then see how long it takes. In our case, I think it was about a half a year we were actually doing similarly or a little bit better than before with our websites.
Anne-Mette: Thanks for sharing that part. So moving forward, a few more commonly asked questions before we move into some usage scenarios. So can domains in a .brand TLD replace registering a .com domain going forward? Do you think so?
Ian: Yes. That is down to if you have invested in a .brand, you should actually leverage it because otherwise you are splitting the brand, splitting the awareness, also splitting whatever you do SEO-wise. So as much as possible, make it easy, make it simple. I know this is not easy, but the less complexity, the easier it is. And we try to enforce that if anybody wants to have something and we try to convince them why not using a .saxo domain.
Anne-Mette: Thank you. So another question that comes up very often is that can you let go of all your domain names outside of your .brand TLD when you now own a .brand TLD? I think that is a question that comes up quite often. And there are not a lot of brand owners who have yet shared what they use their TLDs for and how they use it. But we saw recently that Microsoft announced that they want to keep Microsoft.com for the purpose of commercials, and then they're going to use .Microsoft for domains like 365.Microsoft, Teams.Microsoft, Cloud.Microsoft.
So I think the important part here is that to keep the main considerations around what are your main markets, what are your main areas of interest, and keep those extensions. So it's more like you have things running in parallel. So it's definitely recommended to include that in your domain strategy as well. But is there any advice there you want to share, or have you had any consideration around this part here?
Ian: Yes, we had a fair bit of domains that were created for both marketing purposes. So brief periods and also things like misspellings with odd dashes or not. And I've tried to make a rule that, okay, anything that is not the core branding is something that we can let go of. But of course, you should keep the ones that will hurt you the most if a competitor takes that one and then starts using this for the same purposes as you use your domain for.
Anne-Mette: Great. Moving on to the next one. Here is a question that comes up around, can you use your .brand domains for resellers? I think we have seen on the market in general that there is quite a broad level of that taking place on dealer networks, in localized mini sites for retailers. That's very often used in Germany for the car and manufacturers there so they can enhance original consistency and brand recognition of a unified domain structure as well. So there is some benefit there. I don't know if this is a part you're using, Ian, on .saxo for resellers or for partners.
Ian: In a way we are, because our local offices are actually companies that we have a partnership with. So in a way, they are also resellers. So, of course, you can do that.
Anne-Mette: And then another question that comes up is about emails, whether you can use your .brand TLD for emails. And yes, you can. One of the things I mentioned on the previous slide is about how you can add DMARC at the root so it goes down on all domains there. But it is a way that you can also avoid spoofing emails. It's a way where you can tell the receivers they can verify who the sender is, and that is a way to confirm that part of emails. I don't know. Have you started implementing emails on your site, Ian?
Ian: Yes, for our marketing emails, they're using the .saxo brand. Not on our personal emails, and that's still a hurdle to solve. But our marketing emails, they are using the .saxo domain.
Anne-Mette: And based on the experience, what are the main benefits of owning a .brand? That's also very often the question that comes up. I did mention in the beginning, it's a lot about security and branding as well. But I don't know if you want to add a word or two, Ian, on the benefits that you have been seeing of owning .saxo for your team.
Ian: So one of the biggest benefits is the speed of creating a new domain. There are no hassles in asking for it, finding out what is the cost, getting that approved and going through, getting to all the countries, the registries in the countries where you need this, and finding if it is available or not. So this has been very easy, makes it very easy that you can . . . I think we have up to 7,000 domains that we can create, and of course we don't have that many. But it takes me like 10 minutes, 15 minutes to create a domain. So the biggest burden is all the other stuff that has to be done afterwards in the IT department, and then I have good colleagues that help me out there.
Anne-Mette: Well, that would be the same whether you will be registering a domain for other extensions. It would take a longer time to register, but the setup will be the same because the important part here is that a .brand domain name is having the same behavior as a domain name under .com or .dk or .se. It needs to be set up in the same way. The big difference is that you own this core piece of the internet, so you are the one who can make the choice of which domains, and then, as you're saying, you can do these speedy registrations as well.
So finishing up with the last question for the commonly asked questions here is that can you see any return of investments? Do you have any documented cost savings, or have you done anything internally that you can share with the audience?
Ian: Well, one of the things that we have done is we needed to implement a shortening URL, and we could do that with the domain that we are using both for social, we are going to show that a little bit later, social.saxo, goto.saxo. And in that case, we had a case where we had to send a two-factor authentication SMS at a point in time, and because we could use this short URL and it was clear that it was belonging to us, we didn't need to send two SMSs. I think we saved about was it 60,000 kroner or something like that on that campaign. So yes, you should look out for these possible cost savings. Yeah.
Anne-Mette: Thank you very much for sharing, Ian. So now I really want to move over to looking at some of the usage scenarios that you have, Ian, from .saxo, from using .saxo in your general work. We have the next couple of slides, which is giving some usage scenarios, where we're highlighting the domain name. And then I really want you to just reflect on the usage scenario in general.
So the first domain we have highlighted here is home.saxo. So what was the strategy for the switch from .com, and how do you handle country content/pages, as you're saying, each country has their own company parts? Maybe you want to reflect and share that.
Ian: Yeah. So one of the issues we had was that we have a banking license in some countries and we don't have in other countries. Like in Singapore, we don't. In the UK, we don't. And previously, before owning home.saxo, we were not allowed to mention "bank" in the domain name. So we had to both have saxobank.com and .dk or dk.saxobank.com and uk.saxobank.com for these companies. And then for UK, it was not uk.saxobank.com. I'm saying it wrong. It is uk.saxomarkets.com. So we were not allowed to use the word "bank."
And therefore, we had to have these two kinds of domain names, and it was always difficult. And then when you mention a domain name, a link, we are not allowed to use the word "bank" on the UK website or the Singaporean website. So it's always we need to be on the lookout of if there's any wrong link across these websites. So going to a domain name that doesn't have the word "bank" was actually a solution for this.
And then we switched the URL around. So instead of being dk.saxobank.com and uk.saxomarkets.com, then we ended up having the culture code at the end. So all the SEO value is going to one domain name. So that is also one of the benefits that we can have the SEO value of all the countries, all the cultures going to a single domain name.
Anne-Mette: Thanks for sharing that example. So the next one here is refer.saxo as a domain name itself. So can you share the usage scenario on this domain?
Ian: Yeah. As you can imagine, buying refer.saxo or refer.com or refer. is something that is very expensive. So there we are helped by using a shortener URL, and that helps us create these links automatically. So every time a client signs up and wants to recommend or refer their friends to us, then they get a special URL created for that client. And so when he or she gets friends to sign up, then we can see, okay, it is this client. And the beauty of this is that it's a short URL. It's not long and with a lot of parameters and things like that. It is just refer.saxo/ something that is a random code. And then, yeah, we can use this automatically. We have a service that calls an API and then returns these URLs. So it's nothing that we need to do manually.
Anne-Mette: So the benefit of using it on the .saxo is that "refer" is a generic keyword. And that was something you could just go and register under .saxo as well.
Ian: Yes. True.
Anne-Mette: So that's a nice thing. So the next one here is help.saxo. So can you share if there are some benefits of these targeted domains? I know you touched a bit based on the help previously in this conversation here, but share your thoughts around help.saxo.
Ian: Yeah. So help.saxo is another. This is a special domain where we use a system to host all our help portal, and we have a license so we can change the URL. It's not a redirection, as in the refer.saxo, but it's an independent website with this .saxo domain. And by having this, we can make it work across systems, like cookies, pop-ups, and we can make things work a little bit easier together when they are using the .saxo domain. And it also makes it easy to understand, okay, where do you go for help? Help.saxo.
Anne-Mette: Very good uses there. Thank you for sharing that one. So the next one here is family-offices.saxo. So this descriptive domain name is still shorter than the URL that you're being sent to when you're using this domain in general. So this is a part of your user strategy as well, to be very focused and also have descriptive domains, or is there any other thought behind this domain?
Ian: Yeah, we have still a couple of these kind of redirection URLs that are targeting specific user cases. In this case, it's our institutional offering, and they are targeting some very well-defined user groups kind of. You could say it's a user group family offices. We have introducing brokers and some others, and there, we have set up these kind of redirects. And it makes it also easy to know, "Okay, does this belong to us or not," because it still ends in .saxo.
Anne-Mette: The next one here is, again, a very generic keyword, invest.saxo. So that's a domain name here. So some of the things here we are looking at is more is domains like these help driving the user to the content they're looking for, or are there other advantages that you're seeing by using a domain like invest.saxo?
Ian: Yeah, this is a case of where you take a product name, or in this case, our product is the platform name, and then create a URL for that. Because it's such a central part of what we offer, we also have protected it. So investor.dk, investor.com, I think we have it, especially in the markets where we have it. But the main redirection, the main domain that we market is the invest.saxo, and it makes it easy what is it we are going to. Yeah.
Anne-Mette: Thank you. The next one is podcasts.saxo as a domain name itself. So it seems to be an easy way for marketing to add user-targeted information and also for users to find it. So is that some of the same ideas behind doing registrations like podcasts.saxo here?
Ian: Yeah, podcasts.saxo is one of them. I think there's another, the social.saxo. It's targeted domains that we use for our media, for our outreach. And yeah, we try to make it easy to understand, easy to know what is it that you should look for, memorable domain names.
Anne-Mette: Thank you. There's also a domain name called worksmarter.saxo. So this domain takes the user directly to their own Microsoft account. Is this a part of using .saxo as a secure way to access accounts within Saxo? Or have there been other considerations around the usage of worksmarter.saxo as the domain?
Ian: Yeah, this is our internal IT that have created this, and it makes it . . . Because we are using Office products extensively, then using these short URLs and this redirection makes it easy for our users internally to find where is the content that they are working on. And believe me, that is not simple.
Anne-Mette: Thank you very much for sharing that one. So social.saxo was the next one. You did mention that a bit here. So it looks like some of these parts can be used for different purposes. But do you use .saxo domains for other social channels, like Facebook and LinkedIn and those parts as well?
Ian: Yes. So the use case of this is in our platform, we have a lot of articles, and if clients want to share these articles to somebody or to their followers or whoever they know on social media, we have buttons where when they click on this, it used to create a very, very long URL with some long parameters, and they had to insert that in an email. But now we make a call via this API call to this URL shortener we're using and then it returns social.saxo URL that you can share. And right now, we implemented it for Facebook, LinkedIn, emails, as far as I remember. I don't know if we have more. Yeah.
Anne-Mette: So it gives the user a much shorter URL to share and also for the ones who get it to see that this is a valid and secure link to access, right?
Ian: Yes.
Anne-Mette: Yeah. Great usage scenario. Thank you. Then the next one is called goto.saxo/app. So these are short, memorable domain names. But maybe you can share the benefits of using goto.saxo/app here.
Ian: Yeah. So this is a case of a little bit more complex app link. It depends on what device, how the redirection works. So if you are on desktop, and in this case, you have used the desktop, I can see, to go to this one, because then you land on the homepage. If you were on an Apple device, then you would go to the App Store and find the app that we have. And then if you go on Android, you would go to the same. And we have different apps for the investor and the Saxo trader apps that we have.
And this is a setup that you can do in these link shorteners where you find. You can also do it . . . In this case, we also did it so you actually land on the right culture. So you get the right language as well. So things like that, it's easy to build in and create something with some logic behind so it's easier for users. And then we don't have to update the URLs on our website. There are many links to these, and we have one place to update it if needed.
Anne-Mette: That's really nice. That's really nice. So the last usage scenario here is goto.saxo/onesaxo, and you use this for internal branding. So maybe you want to just share that part with your users as well.
Ian: Yeah. Actually, I just noticed you can recognize the picture from my background to what you see here.
Anne-Mette: Very beautiful picture.
Ian: Yeah, it's our headquarters that's just behind me. So this is one short URL that we use when we have to open our Teams meeting for our biweekly presentation from our management team or different people that are presenting. And the beauty of this is also we save the time by sending emails with different links to different versions of the teams, creating new chats, creating new whatever you need to create to have these webinars up and running. There's one thing that we need to remember. You need to type that in, and then it goes directly to this page. And then when I click on this one, I'm taken directly to the Teams meeting that has this week's meeting. I don't need to remember the long string that you can see in the URL. So this makes it much easier, much less prone for errors, and saves time and complexity, and that's always a good value.
Anne-Mette: So basically, the internal users only need to remember goto.saxo/onesaxo, and then they can be brought to the meetings every second week when you're hosting that. So that's really nice. So thank you very much for sharing all these usage scenarios. I think they're very beneficial for anyone who either would like to own a top-level domain or already owns a top-level domain. So thank you very much for that, Ian.