3
13 Comments

I scratched my own itch (got lots of unused domains) and spent the last weekend working on a little app called 301.website.

http://301.website

I scratched my own itch (got lots of unused domains) and spent the last weekend working on a little app called 301.website. As you might be able to guess, it provides 301 redirects for domain names.

Please take a moment to share your feedback. 🙏🏻
https://301.website

P.S: If you wanna go ahead and use it for your domain, use the coupon 'Indie20' for 20% off.

#product-feedback-request

submitted this linkon February 28, 2019
  1. 3

    No one other than an engineer or possibly a marketer knows what a "301 Redirect" is. Who is your target customer? I know tons of businesses that could benefit from this but have no technical know-how what-so-ever.

    Their current problem would be something like: "I want sub.domain.com to redirect to my Facebook page."

    1. 1

      Thank you. Yes, the name does target the techie audience but I shall work on the copy to make it more friendly for non-tech too.

  2. 2

    It would be great if you can include some info on why anyone would want to use it. Though I am an engineer, it's hard to understand what is a business use case for this is.

    1. 1

      Thank you. I will work on the copy.

  3. 2

    Change the copy at the end to "$1 per website per month"...less confusing...

  4. 1

    I like the simplicity of it! I agree to some degree that the cname part may be confusing for some. but I like it!

  5. 1

    I actually built a micro-SaaS that does this as well. I haven't finished it yet and might never. But it's functional enough for my own use.

    A few things I'm wondering about yours:

    • Does it provide automatic HTTPS for domains?
    • Are there any stats? I want to know how many people are hitting a domain.
    • Can it do 302 redirects as well?
    • Does it only redirect every path to a single URL? Or can it redirect paths on the domain to paths on the destination (e.g. example.io/something > example.com/something)?
    • Is that pricing per domain? I can see that adding up real quick.
    1. 2
      • The HTTPS is left for the target server. It just redirects the incoming request.
      • Stats are on their way.
      • No 302 for now, but will see if it has enough demand to be added.
      • For now; domains -> paths/domains.
      • Yes, per redirected domain.

      Thank you.

  6. 1

    Nearly every reputable registrar provides this functionality. And Cloudflare also provides it, and much more, for free if your registrar does not. What’s your value prop and target market?

    1. 2

      As @nprail has pointed out, CF's free rules aren't enough for people like me. Paid ($20) don't make much sense.
      The value prop I'm offering are:

      • Stats / hits
      • Custom routing bases on req path
      • A central place to manage all the redirects
    2. 2

      While Cloudflare does provide this, it's through page rules which isn't super quick to set up and it's not in a centralized location. Plus, I redirect a lot of subdomains. 3 page rules for free runs out fast.