@alramonl Welcome to the forum!
2fa.directory only provides information about base domains, because of their policy to only include domains in the top 200k websites ranked by SimilarWeb — which does not even rank subdomains.
Thus, to be clear, your feature request amounts to proposing that only vault items containing at least one URI string that starts with one of the following six formats should be included in the Inactive 2FA Report:
https://www.example.comhttp://www.example.comwww.example.comhttps:/example.comhttp:/example.comexample.com
I think that it would in principle be (technically) possible to implement something like the above, but I think it would come with negative consequences. For example, the Inactive 2FA Report would become practically useless for users (like myself) who store only very specific URLs for login forms (to reduce the risk of leaking password data). For example, the URI stored for godaddy.com would be https://sso.godaddy.com/ (with URI matching set to Host); if your proposal were implemented, the user would not be alerted if they had not set up 2FA for their GoDaddy account. This could potentially be solved using the additional-domains field in the 2fa.directory database, but it seems that most entries do not use this field (e.g., their godaddy.com.json entry does not).
A more general (and probably more workable) solution would be to implement the ability to manually exclude vault items from future “Inactive 2FA” reports (including forum sites according to your use-case, but also accounts that use hardware keys or a 3rd-party TOTP authenticator for 2FA, or that use passkeys for authentication). Two relevant feature requests that are currently open are:
- Ability to mark 2FA as done in the inactive 2FA report
- Expand Inactive 2FA Report to include Fido2 etc
In addition, the following feature request from 2020 appears quite relevant to your proposal, but it has been closed:
Interestingly, the behavior described in that thread as undesirable seems to match the behavior that you are now requesting. This implies that something significant changed since 2020 (either on the part of Bitwarden, or on the part of 2fa.directory).