In this project, I’ll be continuing to develop the backend for the file sharing site to continue the proceedings of the project ‘File System Encryption using AES-256 over HTTPS’.

This involves the HTTPS part of the other project, I had already set up a domain with a free and custom TLD, I also enabled SSL certificate to make the site HTTPS. This was all done in InfinityFree.

[<https://www.infinityfree.com/>](<https://www.infinityfree.com/>)

a free web-hosting site that makes development of a website much simpler with free of cost, the only thing that could be even considered as a downside is the custom and the relatively unknown TLD (Top-level Domains).

<aside> 💡 TLD stands for Top-level Domains. These are the highest level of domains in the hierarchical Domain Name System (DNS) of the internet. Examples of TLDs include .com, .org, .net, and .gov

</aside>

Before I start the documentation of this project, let me leave the link to my domain below.

[<https://datavault.rf.gd>](<https://datavault.rf.gd/?i=1>)

Domain Registry

Here’s the creation of a new hosting account along with username and password. Remember, this is not the same as the login credentials to InfinityFree, It’s a computer generated pass.

I use LastPass as my passwords manager, it’s works really well.

Then you move on to naming your domain with a custom TLD of your choice, it takes 72 hours for the domain to setup due to DNS caching.

<aside> 💡 DNS caching refers to the temporary storage of DNS records by DNS resolvers, such as internet service providers (ISPs) or web browsers. This caching helps improve the efficiency and speed of DNS lookups by reducing the need to query authoritative DNS servers every time a domain name is requested. When DNS records are cached, subsequent requests for the same domain can be resolved locally, resulting in faster response times. DNS caching typically has a predetermined time-to-live (TTL) value, after which the cached records are discarded and new DNS lookups are performed. In the context of the document, DNS caching is mentioned in relation to the time it takes for a newly named domain with a custom top-level domain (TLD) to fully set up, as it may take up to 72 hours due to DNS caching.

</aside>

After that you can register for a SSL certificate for your site this makes it HTTPS enabled.

After 3 days, You can set up SSL cert for your site, here you see the CNAME records updated for the domain.

<aside> 💡 CNAME records are DNS records that are used to map a specific domain or subdomain to another domain. They are often used to create aliases for domains or to point a domain to a different hosting provider. CNAME records can be configured through the domain registrar or DNS provider.

</aside>