Can anyone let me know. say you own http://www.subaru.com , can someone somehow register https://www.subaru.com ? surely that isn't allowed as it falls under subaru.com as a domain?

 

https is encrypted http. subura.com would be the domain, which you would own and anything relating to this would be yours. www refers to the machine name, so a request to www.subaru.com would be to a machine called www on the subura.com domain. http://www.subura.com would be a request to machine www at the domain suburu.com using the http protocol, likewise https would be the same but using the secure http protocol.

So the simple answer is no someone couldn't register https as thats not how it works.

 

thankyou for answering my question.

I have one more quick question...

if someone (say a big rich company) was able to use the "Https://www.subaru.com" of the domain subaru.com and subaru.com owner found out; rest assured he didn't authorise this at all but held all the correct documents for the domain.

What sort of action could the owner of Subaru take? What advice would you give to this person?

 

Do you know something we don't ??

 

thanks for answering. hmm now as i'm not sure where i stand.

Basically a finance company seems to be using the https:// of one of my sites. Just wanted to know what options i had.

 

https is a secure website (for example to do your online banking, online ordering, etc), http is not.

 

Hos - as everyone else has said - that's not possible.

You can't register https://www.myname.com or even http://www.myname.com only www.myname.com the http bit comes free

What is the domain name - if you don't mind telling us?

 

They are all correct, with one exception. You actually register subaru.com not www.subaru.com. You wouldn't have to register both www.subaru.com and bbs.subaru.com. If you want a long (and some what boring) descrption of how domain names works then drop me a line.

Come tell us the domain name.

Cheers

Alec

 

domain name...subaru.com
website.......www.subaru.com
ftp...........ftp.subaru.com

 

Not true.

Could use
website = ftp.subaru.com
ftpsite = www.subaru.com

 

Yup, it's all down to the DNS. A website could be 'live' at fred.subaru.com, it doesn't matter.

 

the ftp is only an example, so to give a clearer understanding of domain name!

 

http:// = Hyper Text Transfer Protocol - generally uses port 80
https:// = Hyper Text Transfer Protocol using a Secure Socket Layer (SSL) - have a lock in the bottom left corner of your browser, there is usually a little yellow padlock

Post up the URL in question so we can have a look and do a whois

 

I guess that if someone else is actually hosting *.subaru.com, and depending on the Ts&Cs with the ISP, different protocols (HTTP, HTTPS etc) could be routed to or handled by different applications/organisations. Sounds a bit iffy though?

mb

 

How could someone be using *.subaru.com? Anything that falls under subaru.com is controlled by whoever is authoratative for the DNS of that domain (in this case Sprint the US ISP/Telco):

Registrant:
Subaru of America, Inc. (SUBARU-DOM)
2235 Route 70W
Cherry Hill, NJ 08002

Domain Name: SUBARU.COM

Administrative Contact:
E-Business Administration (EA1624-ORG) mstanton@SUBARU.COM
Subaru of America
2235 Route 70W
Cherry Hill, NJ 08002
US
856-488-8500
Technical Contact:
Nicely, Scott (PJUPXJKYOI) snicely@SUBARU.COM
Subaru of America
2235 Route 70W
Cherry Hill, NJ 08002
US
856-488-8500

Record expires on 03-Aug-2003.
Record created on 02-Aug-1995.
Database last updated on 10-Aug-2002 03:52:29 EDT.

Domain servers in listed order:

DNS.SPRINTIP.COM 208.25.104.7
DNS2.SPRINTIP.COM 205.161.148.7

If they have a dodgy A record in the zone file that points to an old IP address that someone else has access to then maybe or if the adminning ISP had made a change on request by someone other than the owner (ex-employee who is still listed as tech contact etc).

Hos - if we knew the domain in question then we could investigate a bit more and could let you know for sure. Its not like domains are a private thing - the way that DNS works means that anyone with a computer and internet connection can find out pretty everything to do with your domain.

Simon.

 

I was thinking about this whilst cruising up the M40 tonight.

Wouldn't http://www.domain.com and https://www.domain.com have to resolve to the same IP?

The DNS isn't anything to do with the HTTP or HTTPS is it? The same IP should be returned in both cases, hence the web server would have to be compromised or set up wrong for the HTTPS to go somewhere else.

C.

 

Normally yes but you could set up a firewall to fiddle it. The firewall I run here can do all sorts of clever stuff with incoming http and https requests, you can set it to redirect http://www.domain.com/server1 to one machine and http://www.domain.com/server2 to another. It can do this with https too so you could have http and https going to completly different servers even though they seem to resolve to the same IP address. Not sure how common implemntations like this are though.

 

The simply way to redirect SSL to a different IP than http is to use a L3-L7 switch (something like a F5 Big IP). The external interface of the Big IP would be the resolved address and it would then forward requests on http to a web farm and https to a SSL accelerator box.

You could also do it with a Cisco router using PAT or a PIX. Checkpoint would do using different NAT rules.


Jeff

 

It's all effectively server side fiddling though ie the ISP would have to be in on it.

 

Might be mis-configuration....

 

Or Hos'/provider's webserver has been hacked...

 

Hiya,
Apologies for the lack of replies but been away since Friday and have only just got home.

I used subaru.com as an example. I wasn't sure if you could register "https://" as another domain so i thought i would ask here before i looked silly asking my hosts elsewhere as i didn't know...

Definately Https://www. is a different site from the Http://www.

From reading the past few replies, it sounds like its just been misconfigured. I'll pop a question to webhostys. Thanks for the replies.

[Edited by Hos - 8/12/2002 10:53:07 PM]

 

Hmm.
https://www.dymension.com downloads it's content from 194.93.140.190 - could not see an IP for http://www.dymension.com as it loaded so quick.

 

C:\WINDOWS>tracert 194.93.140.190

Tracing route to 194.93.140.190 over a maximum of 30 hops

1 2 ms 2 ms 2 ms 192.168.254.254
2 30 ms 32 ms 37 ms *.*.*.*
3 31 ms 31 ms 30 ms 213.253.166.2
4 30 ms 31 ms 30 ms 195.134.30.249
5 39 ms 36 ms 35 ms 213.253.166.5
6 41 ms 35 ms 34 ms AGNOC-E3-gw.webfactory.co.uk [195.134.0.5]
7 44 ms 43 ms 44 ms 213.253.166.9
8 44 ms 42 ms 44 ms no-dns-yet.cerbernet.co.uk [193.243.227.5]
9 44 ms 46 ms 44 ms p2-lon-main.intensive.net [193.203.5.10]
10 46 ms 46 ms 47 ms 194.93.140.190

Trace complete.

Not much joy there

 

I've had a look at the other site and done a dns lookup of it and its just a misconfig for my domian for another site being hosted on the same server. I'll send an email to webhosts and let them know. Thanks for the replies though.
Hos

 

Shame it was something so simple

Jon

 

www.whateverdomain.com would be registered to the owner, the http or https bit is nothing to do with who owns the domain, its the type of connection to that domain...

Its just telling the browser that its got to make a https (secure) connection to the web server rather than a standard http one.
On another note, if the web server wasn't configured to pass https it wouldn't establish a connection if a https connection were made to it.

Explained the best way I can this time of the morning



[Edited by mega_stream - 8/9/2002 6:26:17 AM]