Live data from Hacker News

The Perils of an .xyz Domain

spotvirtual.com

241–250 of 282 posts

Re: The Perils of an .xyz Domain

#241
post #57

Earlier quoted context omitted.

I had .email for a while. Many shopping sites wouldn't actually let you use the address, presumably given some filter assuming that "email" was a fake address. Because my name ends with "ss", I switched over to .es, which conveniently is a country TLD (Spain). That's worked very well, though occasionally I'll get spam in Spanish, which cracks me up.

I wonder how well these new TLDs work for custom email if you use them with Google Workspaces / Google Apps for Domains or another reputable email hosting service. I've been using a custom domain (though a .net) for decades now and since I moved to Google Apps years ago I haven't had an issue being seen as spam.

I have .email and .cloud hosted on Office365 and they seem to work fine.

Re: The Perils of an .xyz Domain

#242
post #27

I was pretty excited when ICANN opened up a bunch of new domain extensions, but it does sometimes feel like "all these extensions are great if you don't plan on using them". It was pretty cool that I managed to buy a bunch of domains like . , but to be honest I really don't see myself using my .blackfriday domain for anything. For that matter, I think that (somewhat ironically) `my-last-name.email` would not be taken…

I had .email for a while. Many shopping sites wouldn't actually let you use the address, presumably given some filter assuming that "email" was a fake address. Because my name ends with "ss", I switched over to .es, which conveniently is a country TLD (Spain). That's worked very well, though occasionally I'll get spam in Spanish, which cracks me up.

I have an .email and am slowly replacing my gmail address with it. 99% of services seem fine; occasionally there is some old laggard with broken validation schemes ("more than 3 letters for a tld? YOU MUST BE A HACKER!!!11!") but then it's likely you don't want to do business with such people.

Re: The Perils of an .xyz Domain

#243

Well .COM has had its day. There (was?) even a semi-parody site called Domains For the Rest of Us[0] that generates .COM domains that you can use for side projects (or startups?). [0] https://news.ycombinator.com/item?id=24538758 The new gTLDs are a godsend since all the domain hacks have been largely exhausted. E.G: `del.icio.us`. I like the new avalanche of gTLDs since it reduces domain squatting, domain hacks, and…

> there (was?) even a semi-parody site called Domains For the Rest of Us

It's dead, Jim.

Re: The Perils of an .xyz Domain

#244
post #220

Earlier quoted context omitted.

The problem is that just receiving the message is in-and-of itself bad for the end user. It's not the volume you think (assuming the other poster is accurate about relative volumes) - it's far, far more. Imagine getting 1000 SMS/day that all have a "spam" warning attached, or worse, no warning at all. You'd just stop getting any value from SMS at all, and ignore it. I mean, going back to the postal service - even the…

Without any indication? How about WE THINK THIS MESSAGE IS SPAM _tap to read anyway_

You missed the mentions of scale in the post you replied to (and elsewhere in the thread). Imaging needing to hit that or delete tens of times, maybe hundreds, maybe more, for every non-spam message you receive. You'd soon get sick of it. You'd soon accidentally delete, or otherwise miss, an important message in amongst the plethora of junk.

Re: The Perils of an .xyz Domain

#245
post #158

Whoa. I use an xyz domain daily. This thread is eye-opening. Here's the reply from a SpamAssassin validator. My domain is almost marked as spam solely on TLD grounds. What's the point of a TLD if it isn't a first-party domain on the internet? SpamAssassin Score: -0.599 Message is NOT marked as spam Points breakdown: -5.0 RCVD_IN_DNSWL_HI RBL: Sender listed at https://www.dnswl.org/, high trust [***.***.***.*** listed…

On my personal mail server I have an SA rule that gives .xyz a high score (like a +5 or so) because a while back I was getting a huge amount of spam coming in from senders/URLs using domains of it. I haven't revisited that rule in a long time, and suspect it's not unlikely that others have done similar things.

Re: The Perils of an .xyz Domain

#247

Unpopular opinion (maybe): given the current situation, we should probably consider phasing out TLDs somehow. It's becoming more and more clear than no TLD outside those established before the '90s are actually viable for anything outside of "my small personal blog". It would also avoid people having to remember if the TLD is .net or .com, for instance (even though in my experience .net is slowly disappearing too).

If you don't have TLDs, would each DNS server need the details of every domain?

Re: The Perils of an .xyz Domain

#248

Earlier quoted context omitted.

"We get a lot of spam from those" would fall well within a vaguely defined "valid reason", I'd think. (Most of my SMS spam comes from .info domains.)

> Most of my SMS spam comes from .info domains Do you mean that the SMS messages contain links to .info domains?

Yes.

Re: The Perils of an .xyz Domain

#249

Unpopular opinion (maybe): given the current situation, we should probably consider phasing out TLDs somehow. It's becoming more and more clear than no TLD outside those established before the '90s are actually viable for anything outside of "my small personal blog". It would also avoid people having to remember if the TLD is .net or .com, for instance (even though in my experience .net is slowly disappearing too).

If you don't have TLDs, would each DNS server need the details of every domain?

if most domains happen to be .com, isn't it basically the same?

Re: The Perils of an .xyz Domain

#250
post #100

Earlier quoted context omitted.

I ran into this recently even on Facebook Messenger. A friend of mine was hunting for a short domain name and I had a list of some three character .net and .org domains I recently had found that were available. Cut and pasted the list and the message wouldn't send. Narrowed it down to one. Typed just the bare domain. Wouldn't go through. (It was something incredibly benign like n17.org) Couldn't find a history on tha…

>and it took me sending each domain name individually until I found the one that was failing the entire message. A true hacker would have used binary search ;)

Or a distributed ElasticSearch
Post reply on HN