News for hackers. Stuff that matters.
Re:Is it an accident? No, it's a wildcard subdomain by MrSourz on Sunday April 12, 2015 @06:10PM (#9364921)
I think this is a good demo to share with family and am glad this organization has c.uk.

Another 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 by MrSourz on Sunday April 12, 2015 @06:28PM (#9364967)
What I find hard to believe and just realized was that this domain was registered on 10-Jun-2014.

Edit: People were first able to register .uk domains last year, and if the .co.uk domain already exists then you must own it in order to register the .uk domain.

Re:Is it an accident? No, it's a wildcard subdomain by 0x0 on Sunday April 12, 2015 @06:37PM (#9364996)
Direct registrations under .uk (and not just .co.uk, .org.uk etc) were only opened last year.
Re:Is it an accident? No, it's a wildcard subdomain by MrSourz on Sunday April 12, 2015 @06:40PM (#9365003)
That explains it; I was completely baffled. I wonder how much of a bidding war there was for this domain.
Re:Is it an accident? No, it's a wildcard subdomain by MatthewWilkes on Monday April 13, 2015 @09:03AM (#9367341)
The owner of the .co.uk has first dibs, so in this case there was no bidding war.
Re:Is it an accident? No, it's a wildcard subdomain by Jodie_C on Sunday April 12, 2015 @07:42PM (#9365171)
There was an ok.su that would accept any traffic sent its way: mail, web, im, dns, so on.

I often wonder how many errors sent ok.us traffic to that black hole, and what they did with the data. I assume there are several other .su domains set up with blackholes as well.

Re:Is it an accident? No, it's a wildcard subdomain by AshleysBrain on Sunday April 12, 2015 @06:20PM (#9364947)
I 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 by TheDong on Sunday April 12, 2015 @06:24PM (#9364956)
https://t.co/ is very well known. Probably the most used single-character domain in existence :)

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 by TheLoneWolfling on Sunday April 12, 2015 @06:42PM (#9365012)
Re:Is it an accident? No, it's a wildcard subdomain by calebegg on Sunday April 12, 2015 @07:39PM (#9365164)
> This was the case as of 2011-08-16 [...] I'll let them know about it tomorrow and I expect it'll be rectified in a day or two

Quite optimistic :-) especially since the situation has gotten worse by two characters since then.

Re:Is it an accident? No, it's a wildcard subdomain by abraham on Sunday April 12, 2015 @10:10PM (#9365601)
Because your tweet is no longer "ebay.c.uk", Twitter changes is to to "http://t.co/xxxxxxxxxx" which takes additional charactors that what you entered.
Re:Is it an accident? No, it's a wildcard subdomain by dmart on Sunday April 12, 2015 @06:49PM (#9365036)
According to Twitter, t.co is mandatory in order to prevent phishing and calculate link popularity:

https://support.twitter.com/articles/109623

Re:Is it an accident? No, it's a wildcard subdomain by TheDong on Sunday April 12, 2015 @07:17PM (#9365108)
I'm not asking why they use t.co. I'm asking why it counts against my tweet length. If I want to tweet 140 characters and they interpret some of them as a link, why can I no longer tweet my 140 characters because something on their system turned it into 150 characters? They could shorten it while still using my url's length for accounting. They already let you tweet more than 140 bytes due to unicode so it's clearly not a technical reason such as a char(140) db column.

They very well could simply take min(len(t.co/url), len(orig_url)) without breaking any past tweets or changing the 140 character limit's spirit. It would just behave more logically.

Re:Is it an accident? No, it's a wildcard subdomain by ytjohn on Sunday April 12, 2015 @08:48PM (#9365357)
The 140 character limit isn't just an arbitrary number to see how creative people can be within it. Many people forget or never knew that twitter started out with its 140 character limit because of SMS limitations. SMS limits messages to 160 characters, and twitter reserves 20 of those. The final result of your message, including URLs has to fit within 140 characters to reach any SMS bound audience in a single message.
Re:Is it an accident? No, it's a wildcard subdomain by function_seven on Sunday April 12, 2015 @10:11PM (#9365602)
But that's not the case now. The SMS limit is 160 7-byte characters, basically ASCII. But as parent noted, "They already let you tweet more than 140 bytes due to unicode so it's clearly not a technical reason such as a char(140) db column.".

So why do they do it here?

Re:Is it an accident? No, it's a wildcard subdomain by glitch on Sunday April 12, 2015 @08:09PM (#9365244)
(1) Keeping it simple and consistent and (2) they want to ensure that as much relevant traffic goes through t.co as possible. If you want to lock people into t.co URLs, there's no reason for them to play games otherwise unless it truly starts eating into the character count. It's an avenue for profit through data mining. Also, the notion of blocking phishing sites is also there, but the real reason is data mining. They want as much desired, relevant data as possible about the URLs people are using on their service — where they're going, when they're going there, who's going there, etc., etc., etc. In the data, there is money. It's also about other untaped potential in being the middle man (e.g., injected ads) — not that they'll necessarily do such a thing, but from their perspective it's good to be in the position to exploit as many avenues of profit as possible.
Re:Is it an accident? No, it's a wildcard subdomain by TheDong on Sunday April 12, 2015 @08:17PM (#9365259)
You misunderstood. I meant that they could use the minimum of those two lengths when checking the length of your tweet while still turning it into a t.co url either way. All traffic still goes through t.co. The behavior is identical to today except that it's simpler and consistent because it doesn't make my 140 character tweet invalid.
Re:Is it an accident? No, it's a wildcard subdomain by glitch on Sunday April 12, 2015 @08:28PM (#9365300)
They could do something along those lines, but that would not be "keeping things simple". Plus, there is not significant motivation for them to do it — plain and simple. They could, but so far it's not worth the time/money investment. Every little feature, every little bit of work added and layered onto things has an associated cost/benefit to it. Simply put, it's not worth it to them at this present time.
Re:Is it an accident? No, it's a wildcard subdomain by Macha on Sunday April 12, 2015 @06:29PM (#9364971)
Re:Is it an accident? No, it's a wildcard subdomain by mmahemoff on Sunday April 12, 2015 @07:12PM (#9365088)
q, x, and z are the only registered .com domains. Go figure! https://en.wikipedia.org/wiki/Single-letter_second-level_dom...

Of those, x is currently timing out, q redirects to some kind of customer-only login wall, and z is the winner as the only normal public-facing website on a single-letter .com.

I wonder if eBay still owns x.com, having been Elon Musk's PayPal precursor. If so, it's a staggering oversight to leave the domain dormant.

Re:Is it an accident? No, it's a wildcard subdomain by ryanlol on Sunday April 12, 2015 @07:51PM (#9365199)
Registrant Organization: PayPal Inc. Admin Organization: eBay Inc.

Yes they do. Although, I do recall x.com being online not too long ago.

Re:Is it an accident? No, it's a wildcard subdomain by 0x0 on Sunday April 12, 2015 @07:52PM (#9365202)
I ended up on x.com when i was looking for paypal api documentation, it must have been just a year or so ago.
Re:Is it an accident? No, it's a wildcard subdomain by 0x0 on Sunday April 12, 2015 @06:22PM (#9364950)
X.org is pretty well known
Re:Is it an accident? No, it's a wildcard subdomain by pidg on Sunday April 12, 2015 @07:09PM (#9365084)
Another fantastic outcome of non-profit (lol) Nominet's recent, desperate attempts to squeeze every last penny out of the .uk tld.
Re:Is it an accident? No, it's a wildcard subdomain by cbd1984 on Sunday April 12, 2015 @06:17PM (#9364940)
Interesting 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 by MatthewWilkes on Sunday April 12, 2015 @06:19PM (#9364946)
Why is that interesting? c.uk is a registered domain, the WHOIS for subdomains correctly states that it can't be registered.
Re:Is it an accident? No, it's a wildcard subdomain by cbd1984 on Sunday April 12, 2015 @06:22PM (#9364951)
> Why is that interesting?

Because I found it interesting.

Re:Is it an accident? No, it's a wildcard subdomain by ars on Sunday April 12, 2015 @06:32PM (#9364982)
No, he means what do you find unusual about it. It seems like an ordinary name to me.

Is it that it seems too easy to typo?

Re:Is it an accident? No, it's a wildcard subdomain by GSimon on Sunday April 12, 2015 @07:14PM (#9365098)
> No, he means what do you find unusual about it

> It seems like a big security hole.

Re:Is it an accident? No, it's a wildcard subdomain by MatthewWilkes on Monday April 13, 2015 @09:02AM (#9367336)
The problem with c.uk. being an allowed domain is, I agree, very dodgy. This thread is about the WHOIS returning that it's not responsible for foo.c.uk. though which is absolutely what I'd expect.
Re:Is it an accident? No, it's a wildcard subdomain by Yelwis on Sunday April 12, 2015 @07:44PM (#9365176)
Because .UK only allowed registrations at the third level for decades, i.e. example.co.uk, example.ac.uk etc. I think it's also the most-used CCTLD.

Then they introduced second level domains, but they're still rarely used at present. ebay.uk and google.uk are registered, but don't do anything yet.

Re:Is it an accident? No, it's a wildcard subdomain by MrSourz on Sunday April 12, 2015 @06:24PM (#9364958)
You're missing something here. The UK is a country that allows second-level domains e.g., co.uk, gov.uk, org.uk as well as just domains ending in .uk.

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!?

Re:Is it an accident? No, it's a wildcard subdomain by icebraining on Sunday April 12, 2015 @06:42PM (#9365011)
What I find hard to believe is that ti looks like it was registered on: 10-Jun-2014!?

That's the date when they started allowing registration for top level domains (before they just allowed second level).

Re:Is it an accident? No, it's a wildcard subdomain by iamben on Sunday April 12, 2015 @06:41PM (#9365005)
You need to own the .co.uk to get the .uk (at the minute), unless the .co.uk hasn't been registered.
Re:Is it an accident? No, it's a wildcard subdomain by MrSourz on Sunday April 12, 2015 @06:59PM (#9365059)
That's a sensible practice. Thanks for the info!
Re:Is it an accident? No, it's a wildcard subdomain by xg15 on Sunday April 12, 2015 @07:03PM (#9365070)
So, does this mean, I can buy com.uk and edu.uk now?
Re:Is it an accident? No, it's a wildcard subdomain by Yelwis on Sunday April 12, 2015 @07:37PM (#9365157)

    Error for "com.uk".

    This domain cannot be registered because it contravenes the Nominet UK
    naming rules.  The reason is:
      third-level domains may not be identical to a top-level domain.

    WHOIS lookup made at 00:32:52 13-Apr-2015
But edu.uk is available for the owner of edu.co.uk.

Other 2-3 letter domains seem to have been squatted (I tried several ISO codes and some newer generic TLDs).

Re:Is it an accident? No, it's a wildcard subdomain by gabeio on Sunday April 12, 2015 @08:20PM (#9365266)
You could buy e.uk and catch typos like <college>.e.uk with the same page!
Re:Is it an accident? No, it's a wildcard subdomain by mizzao on Sunday April 12, 2015 @10:38PM (#9365687)
It's ac.uk for "academic".
Re:Is it an accident? No, it's a wildcard subdomain by gabeio on Sunday April 12, 2015 @10:54PM (#9365735)
then *.a.uk
Re:Is it an accident? No, it's a wildcard subdomain by nattofriends on Sunday April 12, 2015 @10:44PM (#9365705)
You would fool no one because the UK uses *.ac.uk for academic institutions.
Re:Is it an accident? No, it's a wildcard subdomain by eric59 on Sunday April 12, 2015 @06:23PM (#9364954)
How is a wildcard subdomain configured?
Re:Is it an accident? No, it's a wildcard subdomain by nav1 on Sunday April 12, 2015 @06:30PM (#9364978)
Something along lines of

  *	IN	A	<ip_address>
Re:Is it an accident? No, it's a wildcard subdomain by MrSourz on Sunday April 12, 2015 @06:27PM (#9364963)
A simple DNS configuration would be:

An A record * .domain.com -> IP address

and in Nginx on the server with that IP address

server {

        listen          80;

        server_name     domain.com *.domain.com;
Re:Is it an accident? No, it's a wildcard subdomain by TheDong on Sunday April 12, 2015 @06:30PM (#9364977)
It depends on your DNS provider as to if they support it or not. Often, they will not and you'll simply have to run your own dns nameserver (bind) with a wildcard config, such as http://community.aegirproject.org/dnswildcard ... Googling around will find you many bind configurations and discussions of this feature.
Re:Is it an accident? No, it's a wildcard subdomain by datenwolf on Sunday April 12, 2015 @06:29PM (#9364969)
Have the glue record for a/your domain (e.g. c.uk) point to your own nameserver. Configure the nameserver to respond to any request for an A or AAAA record under that domain with the target IP address. Make the HTTP server listening on that IP address answer regardless of the Host header.