Skip to content

Conversation

@wambugu71
Copy link
Contributor

Requirements

  • You have completed your website.
  • The website is reachable.
  • The CNAME record doesn't contain https:// or /.
  • There is sufficient information at the owner field.
  • There is no NS Records (Enforced as of September 4th, 2024)
  • I fully accept and understand the Terms of Service outline when using this service.
  • I understand that if these requirements are not met my pull request will be closed.

Description

This domain sautify-mail.is-cool.dev will be used to rest send mail for my GitHub Pages project site for the repository wambugu71/sautify.
It will serve as a personal project showcase, hosting static content and demonstration of my work. The project is already deployed on GitHub Pages at https://wambugu71.github.io/sautify/ and will be accessible directly via this custom domain once DNS and GitHub Pages configuration are complete.

Link to Website

https://wambugu71.github.io/sautify/

@wambugu71 wambugu71 requested a review from a team as a code owner December 25, 2025 07:43
@DEV-DIBSTER DEV-DIBSTER merged commit 4f8ec58 into open-domains:main Dec 26, 2025
5 checks passed
@open-domains
Copy link

open-domains bot commented Dec 26, 2025

Pull Request Merged

Buy Me a Coffee


What's next?

Just follow the steps below and you can start using your domain!

GitHub Pages

  • Go to your GitHub repository that you use for your domain.
  • Click on the Settings tab.
  • Click on the Pages link in the sidebar.
  • In the custom domain option, enter the domain you registered.
  • Check the Enforce HTTPS checkbox.
  • Give your domain some time (~24 hours) for the changes to propagate.
  • Enjoy your domain!

Server Owners

For HTTPS, you will have to configure an SSL certificate to allow the new subdomain to work (here's why).


Need help with your domain? If you have troubles setting up your domain, please create an issue and we will try and help you as soon as possible!

Made a mistake in the records? Don't worry, you can create a new pull request with the corrections.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants