I had sunteja.com for about 2 years, during which i hosted it on aws for an year on t2.nano(100qps and the vm would go haywire). once my aws-free tire credits were exausted (I didnt want to pay for hosting), i parked with domain monetisation until it expired. i looked at alternative hostings such as medium, but was not happy with their offering since they stopped providing custom domains may be having too many vhosts is slowing down their lbs.
after a lot of searching i came across github pages, at first i didnt know that github provided custom domains, a great deal of indolence later (also i’m lousy at designing UI’s),here it is.
I have couple of compains though, while the industry is pushing for https to be the defacto, github still doesnt support it for custom domains, they could have easily written a lets-encrypt bot to auto-generate certificates and push it to their lbs to for ssl offloading. using A records, asking customers to point their naked A records to github ips is a bad design, deprecating these ips for github will be pain. In future when they want to depricate the ips, they have to ask all the domain owners to point their dns to the new set, and wait till there are no requests on the old ips (if they dont want to loose any traffic) instead github could have given only CNAME on a subdomain and seamlessly moved ips around (the later might be biased concern of a devops/sre)
UPDATE: github is rolling out https support for custom domains in partnership with lets encrypt, they also included information about ANAME, ALIAS records in their documentation for supported dns providers