Is it an accident? No, it's a wildcard subdomain
1–10 of 49 posts
Re: Is it an accident? No, it's a wildcard subdomain
#2Another more general example to share with family is:
http://www2.scotiaonline.scotiabank.com.online.authenticatio...
These are both cases where the subdomain can trick people. The .c.uk one is a bit more dangerous as they claim a lot of people end up landing on those pages. I had a quick look through some other second level domains to see if anyone else had a site like this.
The more details on two level domains here: http://en.wikipedia.org/wiki/Second-level_domain
Re: Is it an accident? No, it's a wildcard subdomain
#3Re: Is it an accident? No, it's a wildcard subdomain
#4Interesting that they would allow such an odd domain to be registered in the first place. It seems like a big security hole.
Re: Is it an accident? No, it's a wildcard subdomain
#5Re: Is it an accident? No, it's a wildcard subdomain
#6I didn't know single letter domains were allowed? For example none of a.com, b.com, c.com etc. work - do other gTLD allow single letter domains then?
Re: Is it an accident? No, it's a wildcard subdomain
#7Interesting that they would allow such an odd domain to be registered in the first place. It seems like a big security hole.
Why is that interesting? c.uk is a registered domain, the WHOIS for subdomains correctly states that it can't be registered.
Because I found it interesting.
Re: Is it an accident? No, it's a wildcard subdomain
#8Re: Is it an accident? No, it's a wildcard subdomain
#9I didn't know single letter domains were allowed? For example none of a.com, b.com, c.com etc. work - do other gTLD allow single letter domains then?
Unrelated, but I've never understood why t.co counts against your tweet length.. for example, if you tweeted "ebay.c.uk", it would count for length(http://t.co/xxxxxxxxxx) characters (15 characters even though you only typed 9).
Re: Is it an accident? No, it's a wildcard subdomain
#10Interesting that they would allow such an odd domain to be registered in the first place. It seems like a big security hole.
This organizations owns c.uk (so the who-is you should lookup is just c.uk.
What I find hard to believe is that ti looks like it was registered on: 10-Jun-2014!?