Documentation

Domain Names

# Shared Domain Name

When a Trial or Basic account is created, HTTPS is supported out of the box through a shared domain with an SSL/TLS certificate. This shared domain and certificate will use the ImageEngine hostname that is structured as *.cdn.imgeng.in, where the wildcard (*) is a randomly-generated prefix specific to your account. For example xxxyyyzzz.cdn.imgeng.in.

You can not point a CNAME record to these hostnames. If you would prefer to use a custom domain name with HTTPS that corresponds to your own domain (by adding a DNS CNAME record), upgrade to either our Standard or Pro plans and refer to the documentation below.

# Custom Domain (CNAME) with HTTPS / SSL

Standard and Pro plans allow users to add custom domains with HTTPS support. Before starting the process to add a domain, make sure you have access to your DNS provider so you can add a CNAME record. This record will be used for domain validation.

Custom Domain with HTTPS Support Process:

ImageEngine Custom Domain Name Process

# Add Domain

To start the custom domain process, go to the control panel and click on the Add new Domain button. Enter a valid custom domain (a fully qualified domain name - or FQDN) that you own and from which you intend to serve your images. The custom domain name must be unique globally. This custom domain is the hostname from the src attribute of your img tags. In this example, the custom domain name is images.example.com:

<img src="//images.example.com/path/cat.jpg">

Note that the custom domain name must be different from both the domain name of your website and the origin to avoid creating a loop.

When you add a new custom domain, ImageEngine automatically creates a new ImageEngine hostname by appending .imgeng.in. For example, if you add the custom domain images.example.com, images.example.com.imgeng.in is also created.

In the control panel you can manage multiple custom domains.

Note that there are several ways to reach the ImageEngine servers using domain names.

After adding the custom domain, you will see the custom domain appear on the control panel domain My Domain Names section. Next to it, you will see a Domain Pending status indicator. You are now ready to start the HTTPS validation process.

# Enable HTTPS

Before routing traffic to the new custom domain name, you will need to validate the HTTPS certificate record via the ImageEngine control panel. Start by pressing the Enable HTTPS button next to the new custom domain name.

# Add Validation Record to DNS

ImageEngine will generate a certificate validation record. You will see a status button titled add validation record to DNS. Click on this button to see the details of the record. Certificates are provided by Amazon Web Services. A typical certificate validation record looks like:

Record Name: _f6df6f5d07c31ab619bf0240cxxxxxxx.myimg.mydomain.com.
Record Type: CNAME
Record Value: _5419a68cba3exxxxxxxxx4511fae90a4.olprtlswtu.acm-validations.aws.

Add this certificate record information to your DNS. Keep this record in the DNS for as long as the certificate is needed.

# HTTPS Pending

ImageEngine will ping your DNS to attempt to verify the certificate information. Once ImageEngine verifies the certificate from at least one of its edge servers, you will see an “HTTPS Pending” status indicator. ImageEngine needs to verify the certificate from all of its edge servers before the process is complete. This process may take up to 72 hours. Feel free to contact us if you need more information.

# HTTPS Valid

Once ImageEngine has completed the validation process, you will see the status indicator change to HTTPS Valid.

# Add CNAME to DNS

Once the HTTPS Valid indicator is showing, it is time to add a CNAME record to your DNS.

For example, add the custom domain images.example.com as an alias of the ImageEngine hostname it is associated with: images.example.com.imgeng.in. In other words, images.example.com must resolve to images.example.com.imgeng.in. This is achieved by creating a CNAME record in your DNS for your custom domain name, pointing to the corresponding *.imgeng.in hostname.

The DNS records are managed by your DNS provider, which may be your domain registrar or another provider.

A correct setup for images.example.com would look like this when executing the dig command:

$ dig images.example.com
;; ANSWER SECTION:
images.example.com.	59	IN	CNAME	images.example.com.imgeng.in.

If you do not have dig, you can also use nslookup:

$ nslookup images.example.com
Name:    images.example.com.imgeng.in
Aliases: images.example.com

Note for Cloudflare users:

It is recommended to use the DNS only option when name servers are managed by Cloudflare. This option is toggled when clicking the cloud in the row of the domain name in the Cloudflare dashboard.

Cloudflare DNS Record Management

# Domain CNAME Enabled

After you add the CNAME record to your DNS, traffic will start to flow to ImageEngine via HTTPS. The status indicator will change to Domain CNAME Enabled.