i notice that accessing sites with (presumably) no ssl cert using https instead of http often results in loading a page from a completely diff site. for example, http://tgoresort.com
results in a page about an rv resort in florida, while https://tgoresort.com
loads a page about shoe inserts. (depending on your viewpoint, i guess that could be amusing... :-)
the links on the bogus page sometimes point to the correct page by name (but with https prepended), and sometimes point to the bogus domain. i would assume that is due to relative pages vs fully specified pages.
is a page about discount golf in s. carolilna, while https://myrtleBeachGolfmasters.com
loads a page from corbera networks. most links on the page point to corbera networks, but the "mas informacion" link points to https://myrtleBeachGolfmasters.com
, and loads a page from corbera.
nslookup gives the same answer for both:
$ nslookup https://www.tgoresort.com
$ nslookup http://www.tgoresort.com
while whois gives diff answers:
$ whois 126.96.36.199
Level 3 Communications, Inc. LVLT-ORG-8-8 (NET-8-0-0-0-1)
188.8.131.52 - 184.108.40.206
Co-Location.com Inc. LVLT-COLOC-1-8-15-7-96 (NET-8-15-7-96-1)
220.127.116.11 - 18.104.22.168
$ whois 22.214.171.124
Internap Network Services Corporation NETBLK-PNAP-11-99 (NET-63-251-0-0-1)
126.96.36.199 - 188.8.131.52
Internet Search Services INAP-DEN-INTERNETSEARCH-16
184.108.40.206 - 220.127.116.11
the question: is this normal, acceptable behavior? should the https://
ref result in some kind of error msg?