Frecuentemente publicamos actualizaciones de nuestra documentación. Es posible que la traducción de esta página esté en curso. Para conocer la información más actual, visita la documentación en inglés. Si existe un problema con las traducciones en esta página, por favor infórmanos.

About custom domains and GitHub Pages

Páginas de GitHub supports using custom domains, or changing the root of your site's URL from the default, like octocat.github.io, to any domain you own.

Páginas de GitHub se encuentra disponible en repositorios públicos con GitHub gratis y en repositorios privados y públicos con GitHub Pro, Equipo de GitHub, Nube de GitHub Enterprise y Servidor de GitHub Enterprise. Para obtener más información, consulta "Productos de GitHub."

En este artículo

Supported custom domains

Páginas de GitHub works with two types of domains: subdomains and apex domains. For a list of unsupported custom domains, see "Troubleshooting custom domains and Páginas de GitHub."

Tipo de dominio personalizado compatible Ejemplo
subdominio www www.example.com
Custom subdomain blog.example.com
Dominio apex example.com

You can set up either or both types of custom domains for your site. We recommend always using a www subdomain, even if you also use an apex domain. For more information, see "Using an apex domain for your Páginas de GitHub site."

After you configure a custom domain for a user or organization site, the custom domain will replace the <user>.github.io or <organization>.github.io portion of the URL for any project sites owned by the account that do not a custom domain configured. For example, if the custom domain for your user site is www.octocat.com, and you have a project site with no custom domain configured that is published from a repository called octo-project, the Páginas de GitHub site for that repository will be available at www.octocat.com/octo-project.

Using a subdomain for your Páginas de GitHub site

A subdomain is the part of a URL before the root domain. You can configure your subdomain as www or as a distinct section of your site, like blog.example.com.

Subdomains are configured with a CNAME record through your DNS provider. For more information, see "Managing a custom domain for your Páginas de GitHub site."

Subdominios www

A www subdomain is the most commonly used type of subdomain. For example, www.example.com includes a www subdomain.

www subdomains are the most stable type of custom domain because www subdomains are not affected by changes to the IP addresses of GitHub's servers. Your site will also load faster because Denial of Service (DoS) attack protection can be implemented more efficiently.

Subdominios personalizados

A custom subdomain is a type of subdomain that doesn't use the standard www subdomain. Custom subdomains are mostly used when you want two distinct sections of your site. For example, you can create a site called blog.example.com and customize that section independently from www.example.com.

Using an apex domain for your Páginas de GitHub site

An apex domain is a custom domain that does not contain a subdomain, such as example.com. Apex domains are also known as base, bare, naked, root apex, or zone apex domains.

An apex domain is configured with an A, ALIAS, or ANAME record through your DNS provider. For more information, see "Managing a custom domain for your Páginas de GitHub site."

If you are using an apex domain as your custom domain, we recommend also setting up a www subdomain. If you configure the correct records for each domain type through your DNS provider, Páginas de GitHub will automatically create redirects between the domains. For example, if you configure www.example.com as your custom domain for your site, and you have ALIAS and CNAME records set up for the www and apex domains, then example.com will redirect to www.example.com. For more information, see "Managing a custom domain for your Páginas de GitHub site."

Actualizar dominios personalizados cuando tu sitio de Páginas de GitHub está inhabilitado

If your Páginas de GitHub site is disabled but has a custom domain set up, you should immediately update or remove your DNS records with your DNS provider to avoid the risk of a domain takeover. Having a custom domain configured with your DNS provider while your site is disabled could result in someone else hosting a site on one of your subdomains. Para obtener más información, consulta "Administrar un dominio personalizado para tu sitio de Páginas de GitHub".

There are a couple of reasons your site might be automatically disabled.

Leer más

Pregunta a una persona

¿No puedes encontrar lo que estás buscando?

Contáctanos