Spaceship.com - Marketplace Thread

[DomainRecap]

Spaceship.com recently launched a new Marketplace section, and as NamePros has given me the go-head, I think the company deserves its own thread for NP domain marketplace users to converse in.

https://www.spaceship.com/sellerhub/

Personally speaking, I will be setting up a new Spaceship.com account this weekend and going to work investigating its various features, options and policies.

 

[Future Sensors]

Hi @Marina Savina

Once LTO is enabled in SellerHub, how long does it usually take before LTO is visible on / in:

1. The Spaceship sales lander
2. Spaceship search results
3. Namecheap search results

I've enabled LTO for testing one domain, but I'm not currently using Spaceship landers. So far, I haven't seen any LTO option appear in either Spaceship or Namecheap search.

 

[Marina Savina]

But some of these items are so simple. Like being able to sort our names. Seems odd that you would need to monitor feedback and usage to determine that we would like the ability to sort our names.

This is simple. We are beta and we have a lot of features to build and we by now focused on the items that we consider to be more important.

 

[Jannes]

This is simple. We are beta and we have a lot of features to build and we by now focused on the items that we consider to be more important.

Bear with us, this is a tough crowd.

 

[dfav]

Yep, our team is finalising LTO and will start looking into bulk search and sorting/filtering options in a couple of weeks.

I have 3,300 domains. Setting up LTO for each domain would take hours, even days. Instead, it could be something simple:

1) LTO Enabled!

2) LTO installment option: 2-36 installments.

3) Apply these settings to all my domains!

If I need to make any additional adjustments, I could do it for each domain. But this way, LTO is really ineffective! I have to spend extra time on each domain. This would take days! Please consider what I mentioned above.

It should be possible to activate LTO, simply set the number of installments, and apply it to all my domains.

 

[DaveX]

I have 3,300 domains. Setting up LTO for each domain would take hours, even days. Instead, it could be something simple:

1) LTO Enabled!

2) LTO installment option: 2-36 installments.

3) Apply these settings to all my domains!

If I need to make any additional adjustments, I could do it for each domain. But this way, LTO is really ineffective! I have to spend extra time on each domain. This would take days! Please consider what I mentioned above.

It should be possible to activate LTO, simply set the number of installments, and apply it to all my domains.

Not a bad idea! The system would calculate the monthly installment amount based on the price and number of months. Is this what you mean? If so, good idea!

 

[dfav]

Not a bad idea! The system would calculate the monthly installment amount based on the price and number of months. Is this what you mean? If so, good idea!

Hello,

Yes, if I choose 6 installments, the system can automatically set a monthly payment of $1,000 for my $6,000 domain. This should be a simple process.

Customers who want down payments and final payments can choose this, but it's not necessary for everyone. I can do this for some of my domains. But for most domains, 6 installments is the ideal option for me, considering the buy-it-now price. I can do this with a single click!

 

[King]

It may look like this, but that's not how it works. Most of the items that are mentioned here are defined and are consciously cut out of the initial scope to deliver core functionality faster. We deliver in stages and monitor both feedback and actual usage to define what needs to be picked up next. So by sharing the feedback here or via our feedback form on the site you actually help defining the roadmap and the next items that are important to you and other users. The more votes we get the faster item moves out from backlog to in progress.

Seen it mention a few times, can be a nice addition.

 

[Jannes]

Any ETA when we can disable balloon (final) payment? I hate playing with 1+xx+1 month payment plans, especially when the lander only states "initial payment" and then the number of normal installments (xx).

And these look awful, they should be rounded up to the next dollar regardless of cents ("full price" should adjust accordingly):

(yes I know I can get rid of cents if I change this or that, but it's still only a workaround)

 

[fka1080405]

@Marina Savina I believe I'm having similar https issues to @Future Sensors. I'm testing with a large number of .com and .now domains, all configured identically.

(NamePros editor has an issue with some of the text contents of this post so I have switched to using images, the source of the images can be found here on GitHub).

Rather than use Spaceship's DNS servers, I'm using the option to connect with DNS records. Picking one example domain, joe.now, I have added the A records and confirmed they are active:

I have then enabled the for sale page via Spaceship but my requests over http and https all fail. I'm using the resolve option of curl to rule out any DNS issues (ensuring my requests are routed to one of the 2 Spaceship servers):

Both of Spaceship's servers return an empty reply for joe.now over http, and cannot return a response over https because they do not have a certificate.

I've then tried with a .com domain that is also configured in the same way:

And the results of the same commands as above:

So, unlike joe.now, unsuspect.com does receive a response over http but has the same problem over https, no certificate.

Here's what I see in my dashboard for unsuspect.com (and same for joe.now):

Next, I switched my nameservers on the domains to Spaceship's and immediately both http and https work for both domains (no need to toggle for sale page on and off).

The problem can be described as: the landing pages do not work correctly without using Spaceship's nameservers. For non-hsts domains, http works, but for all domains, https does not.

If I was guessing at the cause: your https certificate issuance process uses DNS records instead of the HTTP challenge method which means it cannot ever issue certificates for domains using "Connecting with DNS records" instead of "Switching to Spaceship nameservers"[1]. My recommendation is to remove the the "Connecting with DNS records" option until it is working fully because https is essential.

Additionally, http should always redirect to https: visiting Spaceship landing pages over http does not redirect to https.

[1] The fix for this is either using the HTTP Challenge method or if that isn't an option, delegation of the `_acme-challenge` subdomain.

 

[Marina Savina]

Hi @Marina Savina

Once LTO is enabled in SellerHub, how long does it usually take before LTO is visible on / in:

1. The Spaceship sales lander
2. Spaceship search results
3. Namecheap search results

I've enabled LTO for testing one domain, but I'm not currently using Spaceship landers. So far, I haven't seen any LTO option appear in either Spaceship or Namecheap search.

It takes a few seconds to have LTO visible on the page. As for the search results, it's still in progress and will be released soon. Once added though should also take seconds to a few minutes to sync.

 

[Marina Savina]

I have 3,300 domains. Setting up LTO for each domain would take hours, even days. Instead, it could be something simple:

1) LTO Enabled!

2) LTO installment option: 2-36 installments.

3) Apply these settings to all my domains!

If I need to make any additional adjustments, I could do it for each domain. But this way, LTO is really ineffective! I have to spend extra time on each domain. This would take days! Please consider what I mentioned above.

It should be possible to activate LTO, simply set the number of installments, and apply it to all my domains.

This is the plan. It will be available once we release bulk options.

 

[love4ever]

@Marina Savina

Why you make Down payment & Final payment mandatory ?!!
What if i want buyer to pay only monthly installment, without Down payment & final payment !!?

.

 

[Marina Savina]

@Marina Savina

Why you make Down payment & Final payment mandatory ?!!
What if i want buyer to pay only monthly installment, without Down payment & final payment !!?


Show attachment 283059

.

They will become optional. The change is coming in a couple of weeks.

 

[Marina Savina]

@Marina Savina I believe I'm having similar https issues to @Future Sensors. I'm testing with a large number of .com and .now domains, all configured identically.

(NamePros editor has an issue with some of the text contents of this post so I have switched to using images, the source of the images can be found here on GitHub).

Rather than use Spaceship's DNS servers, I'm using the option to connect with DNS records. Picking one example domain, joe.now, I have added the A records and confirmed they are active:

Show attachment 283049

I have then enabled the for sale page via Spaceship but my requests over http and https all fail. I'm using the resolve option of curl to rule out any DNS issues (ensuring my requests are routed to one of the 2 Spaceship servers):

Show attachment 283050

Both of Spaceship's servers return an empty reply for joe.now over http, and cannot return a response over https because they do not have a certificate.

I've then tried with a .com domain that is also configured in the same way:

Show attachment 283051

And the results of the same commands as above:

Show attachment 283054
So, unlike joe.now, unsuspect.com does receive a response over http but has the same problem over https, no certificate.

Here's what I see in my dashboard for unsuspect.com (and same for joe.now):

Show attachment 283053

Next, I switched my nameservers on the domains to Spaceship's and immediately both http and https work for both domains (no need to toggle for sale page on and off).

Show attachment 283058Show attachment 283056Show attachment 283057
Show attachment 283055

The problem can be described as: the landing pages do not work correctly without using Spaceship's nameservers. For non-hsts domains, http works, but for all domains, https does not.

If I was guessing at the cause: your https certificate issuance process uses DNS records instead of the HTTP challenge method which means it cannot ever issue certificates for domains using "Connecting with DNS records" instead of "Switching to Spaceship nameservers"[1]. My recommendation is to remove the the "Connecting with DNS records" option until it is working fully because https is essential.

Additionally, http should always redirect to https: visiting Spaceship landing pages over http does not redirect to https.

[1] The fix for this is either using the HTTP Challenge method or if that isn't an option, delegation of the `_acme-challenge` subdomain.

Thanks @shr.ink, this is a very detailed and correct description. I checked with the team and they are about to pick up the HTTP challenge method implementation to cover this scenario. For now indeed using spaceship dns for https is recommended, I should have been more clear in my response to @Future Sensors.

 

[Future Sensors]

NamePros editor has an issue with some of the text contents of this post so I have switched to using images

That could be annoying, indeed. You can usually fix it by wrapping it in a code block, like this:

 

[Future Sensors]

For now indeed using spaceship dns for https is recommended, I should have been more clear in my response to @Future Sensors.

No problem.

In my earlier tests, I selected several domains (belonging to other members) that were already delegated to the launch1.spaceship.net and launch2.spaceship.net nameservers. I then obtained the IP addresses of the two associated webservers by querying your authoritative nameservers directly for those domains. Both of these webservers had port 443 completely blocked - as documented in my initial post.

Later, when I received another example domain via DM that used a Spaceship lander, I noticed it was hosted on two different webservers. In this case, both servers had port 443 enabled, and HTTPS was functioning without any issues.

 

[DomainRecap]

https://www.wsj.com/business/deals/cvc-strikes-1-5-billion-deal-for-godaddy-rival-namecheap-a38fd014

 

[domainer8888]

 

[Acroplex]

Richard confirmed that the deal includes both Namecheap AND Spaceship. He remains on board and this is EXACTLY what a strategic acquisition should look like.

 

[Future Sensors]

Richard confirmed that the deal includes both Namecheap AND Spaceship. He remains on board and this is EXACTLY what a strategic acquisition should look like.

It's hardly a coincidence that the deal is being announced on the very day HTTPS and LTO are the hot topics here in this thread. Just saying.