There could be several reasons why the iFrame is not loading the website.
Firstly, as you mentioned, the website is served over HTTP instead of HTTPS. Many modern browsers block HTTP content when the host page is served over HTTPS for security reasons. To fix this issue, you can try changing the website to use HTTPS instead of HTTP.
Another possible reason for the iFrame not loading the website could be due to a Same-Origin Policy violation. This happens when the iFrame's parent page and the website being loaded have different origins (e.g., different domain names or protocols). To solve this, you can try adding the "allow-same-origin" attribute to the iFrame tag.
It's also possible that the iFrame is being blocked by the website being loaded due to security reasons. If the website has implemented security features such as Content Security Policy (CSP), it might be blocking the iFrame from loading. In this case, you can try contacting the website's administrator to see if they can whitelist your iFrame URL.
Finally, it's possible that there's an issue with the website itself, such as it being down or unreachable from your network. You can try accessing the website directly in your browser to see if it loads successfully. If it doesn't, you can try contacting your network administrator or the website's administrator to resolve the issue.
Regarding the dot com ending, it's not necessary for a website to have a .com ending to load in an iFrame. As long as the website is accessible from your network and doesn't violate the Same-Origin Policy or any security features, it should load successfully in the iFrame.
The popup login screen should not affect the iFrame's ability to load the website. However, if the login screen is served from a different domain than the website being loaded, it could violate the Same-Origin Policy and cause the iFrame to fail to load.
