The licence will be likely checked via remote API on app start.
Anyway the boat has sailed here as every browser connects to dozens of places automatically and if you go to any bigger site you are basically cyber attacked so advertising companies can fingerprint and track you.
Even if you, as the company selling the software, can accept all of the above, a license server still is a liability. You sold someone a product and now you need to keep a public API running "forever" (as defined in your legalese). If something goes wrong on your end you are now denying the product you already sold to your customers who already paid for it. I know this is in the end all mitigated by some legalese, which is a whole different can of worms. You also need to make sure your license API is secure and can not leak user data or be twisted into exploiting your software during license checking. There is an ongoing cost to keep the infrastructure running.
As a sibling comment pointed out you can use local only license management like license keys or just nothing like WinRAR or FUTO Keyboard[1]. Yes, you will get users not paying for your software, there will be keygens out there. But even if you use a remote license check, there will be cracks on day 1, if your software is popular enough. I know this is an old and flawed argument, but if someone is willing to navigate a website full of malware infested, blinking ads to avoid paying for your software, they probably would not pay for it anyway.
As an example of what the end stage of hooking up every software to a remote API looks like, Stop Killing Games [2] has done a great job of highlighting just how bad it has gotten in the gaming market. I know there have been some heated discussions around the movement, but the core idea of being able to keep using the software you paid for, is something I absolutely support.
[1] https://keyboard.futo.org/
[2] https://www.stopkillinggames.com/ https://hn.algolia.com/?dateRange=pastYear&query=stop%20kill...