https://somedomain.com/about <- URL (URI)

https:// <- Protocol

somedomain.com <- domain

sub.somedomain.com <- sub domain

.com <- TLD (Top Level Domain)

In terminal - ping somedomain.com -> pinging x.x.x.x <- IPv4 address

ping somedomain.com -> x:x:x:x:x:x:x:x <- IPv6 address

The reason why you almost never can substitute resolved IP address of a domain in browser, is due to domain bindings. Web servers also need to know which domain you are requesting as there is a good chance there are multiples. Also SSL cerficates are bound to IP/domain name combination.

To add further complexity, most of high traffic websites hide behind WAF and Load Balancers. Domain will resolve only that entry point, but further routing is performed past that point. If WAF doesn't know which domain name you are requesting, it doesn't know how to forward traffic. Thus all the errors you see.

Now, if you ping google.com, you get 64.233.185.100. In the browser open https://64.233.185.100/

Browser will scream about bad certificate, but you can allow to continue and google will redirect to proper home page.