Verification & SSL
A custom domain serves traffic once Hiraiship has checked that it points to Hiraiship, and that you own it. Its HTTPS certificate is issued as part of the same check.
Statuses
| Status | Meaning | What to do |
|---|---|---|
| Not verified yet | The domain hasn't been registered for verification. | Choose Refresh. |
| Awaiting DNS | Verification is waiting for your DNS records. | Create the records the dashboard lists, then wait or Refresh. |
| Valid configuration | Verified, with its certificate. The domain serves traffic. | Nothing. |
| Invalid configuration | Verification failed. The dashboard shows why. | Fix the records it names, then Refresh. |
The default hiraiship.app domain shows Live after the first deployment until there is one.
How verification works
When you add a domain, Hiraiship asks Cloudflare to start serving it. Cloudflare then checks:
- that the hostname resolves to Hiraiship, through your
CNAMEorALIASrecord; - that you control the domain, through the
TXTrecords the dashboard lists, when it asks for them.
Hiraiship reads the result back when you choose Refresh, and after each deployment of the domain's environment.
Certificates
Certificates are issued and renewed automatically, for each hostname. There's nothing to upload or renew. HTTPS works as soon as the domain shows Valid configuration.
Behind another proxy
If your DNS is on Cloudflare too, set the record to DNS only (grey cloud) rather than proxied. Your traffic still goes through Cloudflare's network, through Hiraiship.