GitHub Pages DNS record generator

curl -X POST https://163-123-236-68.sslip.io/api/tools/github-pages-dns-generator \
  -H "Content-Type: application/json" \
  -d '{"domain":"","username":"","ipv6":false}'

{
  "tool": "github-pages-dns-generator",
  "input": {
    "domain": "",
    "username": "",
    "ipv6": false
  },
  "result": {
    "verdict": {
      "tone": "success",
      "headline": "A records ready — add your GitHub name for www",
      "summary": "Add the four A records at the root of your domain, and the www CNAME below once your GitHub name is filled in."
    },
    "findings": [
      {
        "id": "domain-not-needed",
        "severity": "info",
        "title": "The records below do not need your domain",
        "detail": "The four apex A records are the same for every GitHub Pages site, so typing your domain only makes this page name it instead of speaking generically."
      },
      {
        "id": "add-username-for-www",
        "severity": "info",
        "title": "Add your GitHub user or organisation name for the www record",
        "detail": "The www CNAME points at your own \"<name>.github.io\", which is the one value here that is not fixed — so it is left out below rather than shown as a pattern you could paste by mistake. Type the name above and the finished record appears."
      },
      {
        "id": "repository-cname-depends-on-publishing-method",
        "severity": "info",
        "title": "Whether the repository needs its own CNAME file depends on how it publishes",
        "detail": "Configuring a custom domain in the repository's Pages settings creates a commit that adds a CNAME file to the root of the source branch automatically. A site published through a custom GitHub Actions workflow never gets that commit, and GitHub neither requires nor reads an existing CNAME file there — so a mismatch only matters for a branch-published site.",
        "fix": "Check whether this repository publishes from a branch or from a custom Actions workflow before treating its CNAME file as something to fix."
      },
      {
        "id": "apex-a-records-ready",
        "severity": "pass",
        "title": "Four apex A records, ready to paste exactly as shown",
        "detail": "These four addresses are the same for every GitHub Pages site using a custom domain, with nothing per-repository to substitute."
      }
    ],
    "parts": [
      {
        "kind": "record",
        "title": "Apex A records to publish",
        "value": "185.199.108.153\n185.199.109.153\n185.199.110.153\n185.199.111.153",
        "note": "All four go at the root of the domain (shown as \"@\" in most panels), not a subdomain.",
        "at": {
          "name": "@",
          "type": "A"
        }
      },
      {
        "kind": "table",
        "title": "DNS records for your domain",
        "columns": [
          "Host",
          "Type",
          "Value",
          "Priority"
        ],
        "mono": [
          2
        ],
        "rows": [
          [
            "@",
            "A",
            "185.199.108.153",
            "—"
          ],
          [
            "@",
            "A",
            "185.199.109.153",
            "—"
          ],
          [
            "@",
            "A",
            "185.199.110.153",
            "—"
          ],
          [
            "@",
            "A",
            "185.199.111.153",
            "—"
          ],
          [
            "www",
            "CNAME",
            "(add your GitHub name above)",
            "—"
          ]
        ],
        "note": "Tick \"Also add IPv6\" above to list the optional AAAA set alongside these."
      }
    ],
    "limits": [
      "This cannot see whether the repository's own CNAME file matches what DNS actually points to — a mismatch there is a GitHub-side setting this tool never sees, and (per the finding above) it only matters for a site published from a branch, not one published through a custom Actions workflow."
    ]
  }
}