All Collections
Administration
Setting up a domain for a PublicInput custom URL
Setting up a domain for a PublicInput custom URL

If you've already bought a domain or looking to purchase one, to point to PublicInput.com, here's how to get set up.

Ruben Morales Jr avatar
Written by Ruben Morales Jr
Updated over a week ago

The following guide covers steps to set up your custom domain with "domain masking," where visitors to your PublicInput.com page see your custom domain in their URL bar throughout their usage of the site. It is a more involved process than a "redirect," which simply re-routes traffic to your PublicInput.com site.

Please note that custom domains may take up to ten business days to process and set up due to registrar behavior and DNS caching.

Please reach out to our support team for pricing for each option.

To get started, fill out the custom domain request form here

Provide the custom domain name and the URL within PublicInput.com to which this domain will point. The latter can be a project page, topic, or engagement hub.


Option A: Allowing PublicInput to purchase the domain, SSL certificate, and point to a PublicInput custom URL.

This option works best for customers that do not have the technical knowledge or resources to purchase a domain and purchase/set up an SSL certificate.

  1. Fill out the above custom domain request form according to your use case. Below is an example of how to answer each question if you want this option.

    1. Do you own this domain?

      1. No, but I would like PublicInput to purchase the domain

    2. All domains pointed to PublicInput require an SSL certificate. How is this domain's SSL certificate handled?

      1. PublicInput will be purchasing & managing the domain and/or SSL certificate

    3. Do you need a CSR?

      1. No

    4. For both questions pertaining DNS records, select the N/A option

    5. Submit the form

  2. That all! Your request will be sent to our Engineering department. For status updates, just reach out to our support team.


Option B: You have already purchased the domain or want to purchase the domain to keep ownership, and do not have the technical knowledge/resources to set up the domain and SSL certificate. This option also works with subdomains.

  1. Fill out the custom domain request form at the top of this page according to your use case. Below is an example of how to answer each question if you want this option.

    1. Do you own this domain?

      1. Yes, and I'm requesting a primary domain or subdomain to point to a PublicInput page. OR

      2. No, but I plan to purchase the domain.

    2. All domains pointed to PublicInput require an SSL certificate. How is this domain's SSL certificate handled?

      1. PublicInput will be purchasing & managing the domain and/or SSL certificate

    3. Do you need a CSR?

      1. No

    4. For both questions pertaining DNS records, select the N/A option.

    5. Submit the form

  2. Change your domain's nameservers. Please reach out to our support team after submitting the form to receive the nameservers for your domain.

Not sure how to do this? Here are links to articles covering how to change your domain nameservers in GoDaddy, Network Solutions, Google Domains, NameCheap and Hostgator.

3. We'll look for your domain routing to begin pointing to our DNS endpoint and set up custom routing for your site. Some registrars may take 24-48 hours to update, and we have to verify domain ownership with our cloud infrastructure provider after that happens; so please plan on 2-3 business days for these changes.


Option C: You have already purchased the domain or want to purchase the domain to keep ownership, and have the technical knowledge/resources to set up the domain and SSL certificate. This options also works with subdomains.

  1. Fill out the custom domain request form at the top of this page according to your use case. Below is an example of how to answer each question if you want this option.

    1. Do you own this domain?

      1. Yes, and I'm requesting a primary domain or subdomain to point to a PublicInput page. OR

      2. No, but I plan to purchase the domain.

    2. All domains pointed to PublicInput require an SSL certificate. How is this domain's SSL certificate handled?

      1. We have a certificate for this primary domain/subdomain already & will share the credentials via email to support@publicinput.com. OR

      2. This subdomain/primary domain that I own does not yet have an SSL certificate, but will purchase one and send to PublicInput.

    3. Do you need a CSR?

      1. Sometimes you will need a CSR when purchasing the SSL certificate, if that is the case, select Yes and let the support team know so we can send you one.

    4. For both questions pertaining DNS records, select Yes or Not yet and add the provided DNS records to your domains DNS records.

    5. Submit the form

  2. Once you have purchased the SSL certificate, send us the .PFX file along with it's password.


Custom Domains FAQ

  • How long does this take?

    • We try our best to fulfill these requests within 5 business days, but they may take up to 10 business days.

  • Can you tell us what format you need our SSL Certificate in? DER or PEM?

    • We need the SSL certificate to be created in the PEM format.

  • Need a CSR (Certificate Signing Request)?

    • Reach out to our support team for one.

  • How do you need it packaged? Bundled or Extracted?

    • Bundled (zip file) or Extracted (individual files) work but Bundled is best as it keeps all files in one place.

  • What files do you need?

    • We need the .pfx file along with its password when the file was created. If a .pfx file is not possible to send, please send us the .crt and .key files and we will generate the .pfx file


See also:

Did this answer your question?