Host your affiliate portal on your own domain with SSL and DNS configuration.
By default, your affiliate portal is accessible at app.icodrip.com/portal/your-org. Custom domains let you host the portal on your own domain — for example, affiliates.yourcompany.com. This creates a more professional, branded experience.
Custom domains include automatic SSL certificate provisioning. Icodrip uses Let's Encrypt to generate and renew certificates for your custom domain. Your affiliates always access the portal over HTTPS with a valid certificate.
Custom domains are available on the Business plan and above. You can add one custom domain per organization on the Business plan and unlimited domains on the Agency plan.
Go to Settings > Domain in your Icodrip dashboard. Enter the subdomain you want to use (e.g., affiliates.yourcompany.com or partners.yourcompany.com). Click "Add Domain" to start the setup process.
Icodrip validates the domain format and checks for conflicts. You cannot use a domain that is already registered to another Icodrip organization. Root domains (e.g., yourcompany.com) are supported but subdomains are recommended to avoid conflicts with your main website.
After adding the domain, Icodrip displays the DNS configuration you need to set up. Keep this page open while you configure your DNS records in the next step.
Log into your DNS provider (Cloudflare, Namecheap, Route 53, etc.) and add the DNS records displayed in Icodrip. You will need to create a CNAME record pointing your subdomain to cname.icodrip.com.
For example, if your custom domain is affiliates.yourcompany.com, create a CNAME record with the name "affiliates" and the value "cname.icodrip.com." If you are using a root domain, you may need to use an ALIAS or ANAME record depending on your DNS provider.
DNS propagation can take anywhere from a few minutes to 48 hours, though most changes take effect within 15 minutes. During this time, Icodrip periodically checks if the DNS is configured correctly.
Once Icodrip detects that your DNS records are correctly configured, it automatically provisions an SSL certificate for your custom domain via Let's Encrypt. This process usually takes less than 5 minutes.
The certificate is a wildcard certificate that covers your custom domain. It is automatically renewed before expiration — you never need to manually manage certificates. The certificate uses modern TLS 1.3 encryption.
If you are using Cloudflare with proxy mode enabled (orange cloud), you may need to configure SSL settings in Cloudflare. Set Cloudflare's SSL mode to "Full (Strict)" to ensure end-to-end encryption between Cloudflare and Icodrip's servers.
After DNS configuration and SSL provisioning, Icodrip verifies that everything is working correctly. The domain status in your dashboard should change from "Pending" to "Active" with a green checkmark.
Test the custom domain by navigating to it in your browser. You should see your branded affiliate portal with a valid SSL certificate. Check that the login flow works correctly and that all portal pages load without errors.
If verification fails, the most common issues are incorrect DNS records, DNS propagation delays, or Cloudflare proxy conflicts. Icodrip provides specific error messages to help you diagnose the issue. You can click "Re-verify" to trigger another check after making corrections.
If your custom domain shows a "DNS not configured" error, double-check the CNAME record in your DNS provider. Make sure the record name matches exactly (no trailing dot in some providers) and the value points to cname.icodrip.com.
SSL certificate provisioning failures are usually caused by DNS verification issues. Let's Encrypt needs to verify domain ownership by resolving the DNS record. If you are using Cloudflare proxy, temporarily disable it (grey cloud) while the certificate is being provisioned, then re-enable it.
If the portal loads but shows a certificate error, your browser may be caching an old certificate. Clear your browser's SSL cache or try in an incognito window. If the issue persists, check that no conflicting AAAA or A records exist for your subdomain.