.now showcase and discussion

[MiamiDomainer93]

I was able to pick up these two names in the 5th day of EAP for a great price. All the highly targeted keywords like news and porn sold in the 2nd day of EAP for around $3,400 each. Please share any of your .now, and your thoughts on the potential future. For some reason, I prefer this extension to .deal that also is in EAP.

 

[Future Sensors]

Horrible. They shouldn't be allowed to market this abomination.

Agree. It's not even listed in the Public Suffix List. Stay away from this.

 

[itsrosemary]

Agree. It's not even listed in the Public Suffix List. Stay away from this.

Ignorance knows no bounds

 

[Future Sensors]

Ignorance knows no bounds

So where is co.now in this list?

https://publicsuffix.org/list/public_suffix_list.dat

 

[itsrosemary]

So where is co.now in this list?

https://publicsuffix.org/list/public_suffix_list.dat

Are you still living in the 20th century? The Public Suffix List is very much a late-90s / early-2000s thing. The list is neither part of DNS, nor required for DNS resolution. The Internet is very different in this 21st century. Also, if you paid attention to the posts you're commenting on, it would be obvious to you that the registry is in early access phase, and that it has just been launched.

 

[Future Sensors]

.

 

[Future Sensors]

Are you still living in the 20th century? The Public Suffix List is very much a late-90s / early-2000s thing. The list is neither part of DNS, nor required for DNS resolution. The Internet is very different in this 21st century. Also, if you paid attention to the posts you're commenting on, it would be obvious to you that the registry is in early access phase, and that it has just been launched.

it.com is listed.
co.now is not.

And that is a problem. The PSL is the de‑facto standard used by browsers, security tools, and countless libraries today. Whether it's part of DNS is irrelevant. What matters is real‑world dependency. If you launch a public‑facing TLD, you should expect people to check PSL readiness.

 

[itsrosemary]

Why did you just edit icannwiki to remove co.now?

I am not on icannwiki. It seems it's 'Rebrand now' who has his knickers in twist there. Had no idea that .co.now will trigger some people's personal insecurities with a launch.

 

[itsrosemary]

it.com is listed.
co.now is not.

And that is a problem. The PSL is still the de‑facto standard used by browsers, security tools, and countless libraries today. Whether it's part of DNS is irrelevant. What matters is real‑world dependency. If you launch a public‑facing TLD, you should expect people to check PSL readiness.

Repeating for the 5th time. .co.now has just gone live and is in early access phase.

 

[Future Sensors]

Repeating for the 5th time. .co.now has just gone live and is in early access phase.

Stop pushing it.

 

[love4ever]

Repeating for the 5th time. .co.now has just gone live and is in early access phase.

Means will be launched and active after how many years ?

.

 

[Future Sensors]

Let me repeat.

Calling the Public Suffix List a late‑90s relic ignores how central it is to the modern internet. Every major browser relies on it for cookie boundaries and domain isolation, security tools and libraries use it to correctly identify registrable domains, and virtually every programming ecosystem depends on it for accurate domain parsing.

It's actively maintained, updated daily, and remains the only widely adopted standard for determining public suffix boundaries. Whether it's part of DNS is irrelevant. It exists precisely because DNS alone can't express the policy rules modern web security requires.

If you launch a new TLD today, PSL inclusion is essential for correct real‑world behavior.

 

[Future Sensors]

Even @Paul uses it!

 

[NameGroove]

Don't get your knickers in a twist. My signature already says I am their customer, Sherlock

Jannes post showed you are more than a customer, but rather part of their team. Is that correct?

You're right. It's understandable, though, as we mostly look at things from a TLD investor's narrow perspective on this forum. But there is a whole world to consider from the viewpoint of registries, registrars, and end users. I just wanted to share a positive .now development that’s relevant to this thread.

This thread is about .now, which is run by Amazon's registry.

Discussing your registrars products and services in this thread is off topic and against forum rules

https://www.namepros.com/threads/of...48752/?utm_source=namepros.com#section-011500

1.15. Organization. (a) All content must be organized in an appropriate section (“forum”). (b) Posts and messages must be on topic and relevant where submitted (e.g., a discussion thread or direct message).

• Note: The topic of a page is determined primarily by its title (and sometimes secondarily or refined by its first post/message); subsequent posts (even by the topic's creator) do not change the topic.
  

Should you desire to discuss alt TLDs (whether provided by your registrar or not) you should create a new thread and title it properly.

 

[itsrosemary]

Let me repeat.

Calling the Public Suffix List a late‑90s relic ignores how central it is to the modern internet. Every major browser relies on it for cookie boundaries and domain isolation, security tools and libraries use it to correctly identify registrable domains, and virtually every programming ecosystem depends on it for accurate domain parsing.

It's actively maintained, updated daily, and remains the only widely adopted standard for determining public suffix boundaries. Whether it's part of DNS is irrelevant. It exists precisely because DNS alone can't express the policy rules modern web security requires.

If you launch a new TLD today, PSL inclusion is essential for correct real‑world behavior.

It was a thing once upon a time, I give you that. That said, it should be added once they do a full launch.

 

[Future Sensors]

It was a thing once upon a time, I give you that.

You're definitely not a tech person. It's incorrect.

 

[itsrosemary]

Jannes post showed you are more than a customer, but rather part of their team. Is that correct?



This thread is about .now, which is run by Amazon's registry.

Discussing your registrars products and services in this thread is off topic and against forum rules

https://www.namepros.com/threads/of...48752/?utm_source=namepros.com#section-011500

1.15. Organization. (a) All content must be organized in an appropriate section (“forum”). (b) Posts and messages must be on topic and relevant where submitted (e.g., a discussion thread or direct message).

• Note: The topic of a page is determined primarily by its title (and sometimes secondarily or refined by its first post/message); subsequent posts (even by the topic's creator) do not change the topic.

Should you desire to discuss alt TLDs (whether provided by your registrar or not) you should create a new thread and title it properly.

Incorrect. I have already answered that I am a customer. The original post was about a .now domain.

 

[itsrosemary]

You're definitely not a tech person. It's incorrect.

Yes, not a tech person. But it's also a fact that dns resolution does not require domains to be on a list from mozilla.

 

[Future Sensors]

Yes, not a tech person. But it's also a fact that dns resolution does not require domains to be on a list from mozilla.

That's not what I explained. And it's not a list from Mozilla alone.

https://publicsuffix.org/learn/

 

[itsrosemary]

That's not what I explained. And it's not a list from Mozilla alone.

https://publicsuffix.org/learn/

Here is what ChatGPT has to say about your comment:

No — a TLD (top-level domain) or domain name product does not have to be listed in the Public Suffix List (PSL) (https://publicsuffix.org/list/public_suffix_list.dat) for the Internet to “recognize” it as a valid domain.

Here’s how it works:

1. DNS Recognition vs. Public Suffix List​

• The DNS (Domain Name System) is what actually makes domains work on the Internet.
  • If a domain resolves in DNS (e.g., you can look it up and get an IP or NS records), then the Internet “recognizes” it.
• The Public Suffix List is not part of DNS or Internet routing.

It's up to registries to submit their domains to the list which I am sure .co.now will do if they want.

I am done with this debate. Got better things to do than lecture people

Good day!

 

[Future Sensors]

You're definitely not a tech person, if you have to ask ChatGPT.

Stop pushing .co.now. Thanks.