Domains without HTTP/HTTPS prefix not processing correctly

[aFinchy]

Description

When domains are entered without an "http://" or "https://" prefix, they are not being processed correctly. This issue affects the URL normalization process, causing failures in subsequent operations that depend on properly formatted URLs.

Steps to Reproduce

1. Input a URL without a scheme into the system (e.g., example.com or www.example.com).
2. Observe that the URL does not get correctly prefixed with "http://", leading to failures in processing.

Expected Behavior

Domains entered without an HTTP/HTTPS prefix should automatically have "http://" appended to ensure they are processed correctly throughout the system.

Actual Behavior

The domains are left without any scheme, which leads to incorrect processing and potential errors in downstream functionality.

Possible Solution

Adjust the URL normalization function to detect and prepend "http://" to URLs lacking a scheme.

This issue is critical for ensuring all user-entered URLs are handled uniformly and correctly across the platform.

[aFinchy]

After some testing, it appears that it works with www.domain.com, but when you do www.sub.domain.com it does not work.