Free for-sale landers by NamePros

Happy April 1st!

We have exciting news to share with you. This year, our April 1st pranks and activities are changing exclusively to adding useful features each year.

For our first April of this new initiative, we're bringing you:

• Free landers by NamePros
• Guide to free domain parking by NamePros

After a very successful closed beta with select PRO members, industry leaders, and Large Portfolio Holders, we're finally ready to share it with you for its public beta! Special thanks to @Future Sensors for going above and beyond in every way to help us test and improve during the closed beta.

Now it's your turn!

We hope you'll like what you see!

All feedback and suggestions are appreciated.

---

Designs from 2023 to today​

2023 Design:​

Source: DomainGang​

2024 Design:​

2025 Q1 Design:​

2025 Q4 Design:​

Update:

• Check out the latest improvements and new features!

 

[Paul]

What is the time frame for the minimum price field to be added?

This week, assuming I have enough coffee left.

 

[HotKey]

Please forgive me also if I sincerely ask a simple question here. Is there any possibility this is an extended April Fool's Day prank?

Hope not. I really don't want to delete my tweet.

Now, a great AF's would have been "NP acquired by Eye-Pick" and you can now use MasterPros for trading..

 

[VIPDomains]

Kudos to the initiative. It's greatly appreciated.
1) Perhaps you can have several backgrounds to choose from or update this one to be a little more color-fluent or single, dual tones ones to choose from.
2) Allow adding white background around the lander (have borders for it)
3) Give the option to choose the currency (Euro/Dollar et...)
4) Have "Secure... https, tsl, etc... disclaimer at the bottom to treasure the client that things are secure.

 

[VIPDomains]

I created a GoDaddy profile with the name servers provided and assigned it to 1000+ domains... all are approved here and not a single one is showing up in the verified... All of my Namecheap ones are visible thought. Any Ideas?

 

[dirk]

I created a GoDaddy profile with the name servers provided and assigned it to 1000+ domains... all are approved here and not a single one is showing up in the verified... All of my Namecheap ones are visible thought. Any Ideas?

Did GoDaddy add the verification nameserver? I have the same issue at another registrar. Ns1 and ns2 work fine though.

GoDaddy doesn't handle unregistered nameservers that well, haven't looked into it to check wether that's the problem but it's a possibility.

 

[alop]

!duel future sensors

 

[Future Sensors]

@VIPDomains @branding It's something we've been testing, and especially GoDaddy can be very picky while adding the verification nameserver for some ccTLDs. Other registrars were accepting just fine, with a correct delegation in DNS including all three nameservers.

@VIPDomains What are the TLDs you have difficulties with adding the 3rd nameserver for at GoDaddy?

 

[Future Sensors]

@VIPDomains @branding While testing this for NamePros Parking, I also noticed that there are (still) problems adding the DAN *.hn verification nameserver for some ccTLDs like .de through GoDaddy. The nameservers are accepted in the GoDaddy interface, but later on you will receive an email from GoDaddy that they encountered errors ("This is the error we received: Command failed"). Have submitted a ticket with DAN already.

 

[dirk]

@VIPDomains @branding While testing this for NamePros Parking, I also noticed that there are (still) problems adding the DAN *.hn verification nameserver for some ccTLDs like .de through GoDaddy. The nameservers are accepted in the GoDaddy interface, but later on you will receive an email from GoDaddy that they encountered errors ("This is the error we received: Command failed"). Have submitted a ticket with DAN already.

Thanks. I think this is why Dan added the TXT verification later on, as the verification nameserver may give issues.

The .de registry is very strict. You cannot submit nameservers if the domain is not present in the zone file beforehand.

I would definitely look into the way the verification server is set up as well. I encountered the same issue years ago with one of my own setups. To accomplish what you/np is trying to do you create a 'work around' which technically works but is not common/best practice, hence the issue.

While we're at it... What's the reason for using some obscure extension on the verification server? Its for redundancy obviously but there are better, less scammy looking, extensions. You know, just to convey some trust

It's not just GoDaddy btw. Some more obscure registrars will give the the same error/warning although they allow you to ignore the 'warning' and add the DNS server anyway.

 

[Future Sensors]

Thanks for the information @branding - I agree. @Paul and @Quebec Tech Team are already looking into other verification methods, afaik.

With regard to being authoritative first for .de on the nameserver, I can say that NP is authoritative (aa bit set) for just any domain, just like DAN is doing, and a lot of others as well.

With regard to choosing the *.is extension, @Paul can tell more about that.

 

[VIPDomains]

@VIPDomains @branding It's something we've been testing, and especially GoDaddy can be very picky while adding the verification nameserver for some ccTLDs. Other registrars were accepting just fine, with a correct delegation in DNS including all three nameservers.

@VIPDomains What are the TLDs you have difficulties with adding the 3rd nameserver for at GoDaddy?

.COM .NET .XYZ .IO .LAT .LIFE .LTD .NET .AGENCY .VIP .WIKI .PET .STORE .INFO

 

[VIPDomains]

@VIPDomains @branding It's something we've been testing, and especially GoDaddy can be very picky while adding the verification nameserver for some ccTLDs. Other registrars were accepting just fine, with a correct delegation in DNS including all three nameservers.

@VIPDomains What are the TLDs you have difficulties with adding the 3rd nameserver for at GoDaddy?

Here are my settings on the manual, they are the same on the template...
So how do we make it work i have 1000+ domains I want on NP Landers

 

[VIPDomains]

Did GoDaddy add the verification nameserver? I have the same issue at another registrar. Ns1 and ns2 work fine though.

GoDaddy doesn't handle unregistered nameservers that well, haven't looked into it to check wether that's the problem but it's a possibility.

So can i go without the 3rd one?
What do you suggest ...

 

[Future Sensors]

.COM .NET .XYZ .IO .LAT .LIFE .LTD .NET .AGENCY .VIP .WIKI .PET .STORE .INFO

Thanks.

Strange that you're also experiencing trouble while changing NS for .com and .net domains. Were they part of a bulk NS change on your part?

I've successfully been able to set all 3 NamePros nameservers at GoDaddy for .com domains.

Could you test only 1 .com domain and see if it works?

 

[Future Sensors]

So can i go without the 3rd one?
What do you suggest ...

Without the verification nameserver present, the domain will not be associated with your NamePros Parking account, so it will not get the 'Verified' status in your account, and you will see a parking lander instead of a sales lander, and you will not receive leads. So in order to make it work, verification has to be be successful.

 

[skshogun]

That could be added. Is that something you’d like? Any others?

Euro could be nice!

 

[podaf]

You should add Method of payment and how to make payment

 

[dirk]

Thanks for the information @branding - I agree. @Paul and @Quebec Tech Team are already looking into other verification methods, afaik.

With regard to being authoritative first for .de on the nameserver, I can say that NP is authoritative (aa bit set) for just any domain, just like DAN is doing, and a lot of others as well.

With regard to choosing the *.is extension, @Paul can tell more about that.

Thanks. I know you're 'just' a tester but do appreciate your time/input. I'm not that much invested in .de but from what I do know it's usually a dns 'misconfiguration' issue.

So can i go without the 3rd one?
What do you suggest ...

You won't be able to verify it, as per @Future Sensors explanation. That's why they will have to add TXT record verification alongside personal dns hostname verification if they want to cover all bases.

It's not a GoDaddy bug, they actually follow what's being considered best practice.

Without the verification nameserver present, the domain will not be associated with your NamePros Parking account, so it will not get the 'Verified' status in your account, and you will see a parking lander instead of a sales lander, and you will not receive leads. So in order to make it work, verification has to be be successful.

Agreed. See my comment above. I would love to be able to free up some time to investigate, unfortunately I'm very limited in spare time atm.

What I do know for sure, it comes down to the third (verification) nameserver. I encounter the same issue, .com tld different registrar.

That being said, I think current setup will work without issues 99% of the time for gtlds registered at the biggest and known registrars.

 

[dirk]

Thinking out loud... Can you add the ip address for a dns server alongside the hostname at godaddy?

If you can, lookup the ips and fill out both the hostname and ip. Might do the trick.

 

[Future Sensors]

@branding Thanks. It will take some time figuring out these corner cases. Just like you, I think DNS delegation info has to be consistent everywhere, including the verification nameserver. Other methods like optional TXT verification may be a good workaround, as you said.