second level domain com.be not detected

[karelvanhecke]

Steps To Reproduce

1. Go to amazon.com.be (present in equivalent domains amazon.com since [PS-1703] feat: add amazon.com.be domain to amazon #2349)
2. In the mobile client it shows that it tries to match against "com.be", browser extension has the same issue
3. The equivalent domain rule does not work, no login is shown

Expected Result

amazon.com.be is detected correctly and matched against equivalent domains

Actual Result

amazon.com.be is detected as com.be and equivalent domain rules are not applied

Screenshots or Videos

No response

Additional Context

No response

Build Version

2023.9.1

Environment

Cloud (bitwarden.com)

Environment Details

No response

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[SergeantConfused]

Hi @karelvanhecke,

Thank you for your report. I was able to reproduce this behaviour and I have flagged it to our Engineering team.

If you wish to add any further information, such as screenshots or screen recordings, please feel free to do so at any time - our Engineering team will be happy to review them.

Thank you again,

[heihei1634]

It cannot be a second-level domain name, nor can it be a different port. In this case, there will be many prompts for one URL, which will be very cumbersome.

[detuur]

.com.be is not an actual TLD. Amazon has simply registered the com.be domain name because amazon.be was taken. They are not allowing anyone else to register subdomains under .com.be. This actually means that *.com.be, for the time being, is guaranteed to be an Amazon domain.

Just thought this could be valuable information for anyone working on this.