Live data from Hacker News

The Perils of an .xyz Domain

spotvirtual.com

221–230 of 282 posts

Re: The Perils of an .xyz Domain

#221

This is a total shame because .xyz is extremely catchy and, in my mind, could be the new .com in a few years. All the other TLDs are hard to remember -- in my experience, people will ask "was it my.website or mywebsite.com?" but if you tell someone "it's mywebsite.xyz" they always get it right.

This has not been my experience at at; people assume saying .xyz is a joke and then act surprised when the URL doesn't work and you say "no really, it ends in .xyz".

Roll your eyes all you want, but get the dotcom.

Re: The Perils of an .xyz Domain

#222

> we would occasionally get feedback from users and prospects that the .xyz domain felt unprofessional I had a .xyz domain. I thought it was easier, the domain was short to type. I was completely wrong. I asked a few non-technical friends. They said they would never use my site because of the .xyz, it felt like a spam site. I redid the site on .net with a longer domain name - much better results.

[deleted]

Re: The Perils of an .xyz Domain

#223
post #91

Earlier quoted context omitted.

I didn't know about abc.xyz, that's a really nice URL

Quite likely only investors in Google / Alphabet stock know that site and have it bookmarked because that's where Alphabet publishes its quarterly earnings. I also guess for the same reason, it only gets significant traffic once a quarter during earnings season.

I like to think of it as Ruth's blog ;)

Re: The Perils of an .xyz Domain

#224

Earlier quoted context omitted.

I wonder if that's why he mentions "without a valid reason".

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

Re: The Perils of an .xyz Domain

#225

Earlier quoted context omitted.

I have this same problem with "obscure" .net domains. My text messages are silently dropped. The only work around I found is to not include http:// , just use the bare domain. Personally, I find this behavior of my SMS provider reprehensible.

Is it reprehensible only when it impacts you or is it still reprehensible when it's blocking hundreds of spam messages a day you might otherwise be receiving?

I should receive 100% of messages from numbers I message. If my carrier wants to helpfully filter my other messages, I should be able to opt out.

Re: The Perils of an .xyz Domain

#226
post #187
post #174

I have had similar experiences with corporate firewalls blocking my .app domain. I got in a painfully stupid argument with a middle-age IT admin “we don’t want to our employees installing apps” It’s not an app, you don’t install it, it’s a “WebApp”, it’s just a freaking fancy website who’s domain ends in .app - lol, this was like three years ago and just thinking about it is getting me heated

> I got in a painfully stupid argument with a middle-age IT admin “we don’t want to our employees installing apps” If they think that any domain that ends in .app is for installing apps, their mind is gonna be blown about some of the sites on .net and .org domains...

.net is going to install the entire internet! We cant allow that!

Re: The Perils of an .xyz Domain

#227

As a guy who's blog and email consists of .xyz domains, I can only say two or three times in ad many years has it ever been a problem (that I'm aware of, at least), and then it was a website not letting me create an account using it for email. I suspect I'm either lucky, or something.

Same here. My DKIM headers are signed by a well known and respected email provider. I assume if you self host the results are gonna be wildly different.

Sometimes I send reminders from my xyz domain to my corporate email accounts (which tend to have a rather aggressive filtering) and everything seems to work fine.

Re: The Perils of an .xyz Domain

#228
post #80

Got a nice .xyz domain mainly for mail with SPF,DKIM correctly set up and tested against multiple validators. No big issues so far except for the HR department of a potential new gig which can painlessly mail me@mydomain.xyz about job interviews BUT never get my replies back. I don't who to blame more in this mess: - Me for playing smartass instead of using a @gmail.com because they impose the rules so everybody comp…

It's nobody's fault but the XYZ registry. They sell XYZ domains for $1 for the first year, which makes them the #1 favorite of spammers/phishers.

Re: The Perils of an .xyz Domain

#229
- uses googlemail as TXT entries but privateemail.com MX entries for spot.xyz domain

- no DKIM/DMARC verification headers that make sense, just a default ~all

- wonders why emails are classified as spam

Well, yeah. Maybe use an email spam rating tool next time, like mail tester [1]?

[1] https://www.mail-tester.com

Re: The Perils of an .xyz Domain

#230
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 haven't had many issues using .xyz with gsuite (with the exception of a couple of sites that didn't accept it as a valid email), but most of the people I email are @gmail.com.
Post reply on HN