SezerYaar that's actually nearly correct. In "Exact match" It's always the full version of the url that is compared, so it includes the protocol (http:// or https://) as typed in the post. Also trailing slashes matter. https://example.com/ won't match a pattern of https://example.com in "exact match" mode. Same for www subdomains, you need to cover them in the pattern if needed.
If you don't care what the original link path or parameters are and want to replace all links to this domain, the easiest is to switch to "Hostname match", where only the hostname (without protocol or path/slash) must be entered as the "match pattern".
Don't forget to add a protocol to the replacement value as well, otherwise links generated by the extension won't be valid.
If you know how to use regexes these will be the most powerful options for this extension, but from your requirements host mode or even exact mode with protocol should suffice.
The extension currently isn't validating the replacement pattern because standard validation rules don't work with the allowed special replacement parameters... Will probably be improved in the future if there's demand.
We could add a note about not forgetting about the protocol in the help text. Let me know if you have any other idea to improve them 😉
EDIT: I just see your edit now, glad you figured it out. You might still be interested by the few tips I shared above.
There's no harm done by asking, that's exactly why this discussion exists 😉
