Give your service
its own address.

Check your hosting first

banchi provides a subdomain and its DNS connection settings. You supply the hosting or server that runs your website and APIs. With a standard DNS connection, visitors connect directly to that host.

Hosting that advertises custom domains can still require different DNS records or a paid plan. Compare its requested settings with the supported records below. Ask us before purchasing if you are unsure.

Four steps to connect

1. Publish your site on your hosting

   Check that the provider's default URL works. Confirm that your plan supports custom domains and find out which DNS records it requires.

2. Register the address with your host

   Open Your addresses → address settings in banchi and copy the hostname. Add the full hostname under Custom domain on your hosting, without https:// or a path.

3. Save the target in banchi

   Choose Connect to my own hosting. A hosting preset accepts one CNAME target or IPv4 address. For IPv6, multiple IP addresses, child names, TXT or CAA, use individual DNS records. Do not put paths or port numbers in DNS targets.

4. Check HTTPS and app features

   Wait for your host to issue its certificate and run the banchi check again. Once connected, open your address and perform the app checks. Timing depends on the host and DNS caches.

banchi checks DNS and HTTPS. It distinguishes saved DNS, HTTPS reachability and a successful response at the root. Sign-in, posting and payments are not tested automatically.

Configure individual DNS records

Open individual DNS settings for your address and enter the type, name and value requested by your host. For an address such as your-name.banchi.app, use these name formats.

The rented address itself

Enter @ or your-name.banchi.app. This is the root of your rented address.

Names below your address

Enter the complete hostname, such as www.your-name.banchi.app, api.dev.your-name.banchi.app or _verify.your-name.banchi.app. Relative names such as www, another customer's address and wildcards such as *.your-name.banchi.app are not accepted.

A and AAAA

Enter the public IPv4 or IPv6 address supplied by your host. Multiple IP addresses at the same name are supported. Private-network and certain reserved addresses are not accepted.

CNAME

Enter the complete destination hostname. A CNAME cannot share its name with another record. For example, a root CNAME cannot coexist with a root TXT; verification would need a different name.

TXT

For web service ownership verification and DNS-01 certificate challenges. Email records such as SPF, DKIM and DMARC are outside the supported scope.

CAA

Use the certificate issuer settings requested by your host, for example 0 issue "letsencrypt.org". Match the actual issuer: an incorrect value can block certificate issuance or renewal.

The standard limit is five records per rented address. Verification TXT, CAA and banchi's automatic notice record all count. When no root A, AAAA or CNAME is set, banchi adds one notice record at the root, leaving four records for your settings. Adding your own root target automatically replaces the notice record; you do not edit that record yourself.

You may save a verification TXT first and add the hosting target afterward. You can also use child hostnames without publishing at the root. banchi's HTTPS diagnostic checks the root only: configure hostname acceptance, certificates and app features separately for every child hostname you use.

DNS_SAVED

No root hosting target is set, so there is no root HTTPS destination to test. Check each record's application status after saving TXT or other records. This is not confirmation of a published website.

HTTPS_REACHED

Root HTTPS responded with a status such as 401, 403, 404 or 405. Authentication or unsupported HEAD requests can cause this. Test the intended features in a browser.

LIVE

Root DNS matches and an HTTPS HEAD request returned 200–399. Redirect destinations, sign-in and posting have not been tested by this check.

Instructions for your hosting

The three destinations below were checked against the provider's official instructions and banchi's input constraints. End-to-end connections from banchi have not been tested, so follow the records your provider actually displays. Nameserver changes, email records and setups exceeding the five-record limit cannot be configured as requested. Contact us with the requested record's name and type; do not send private keys or authentication tokens.

App settings and tests before launch

A change of hostname can require app configuration changes. Check the items your service uses. These also apply when changing a regular custom domain.

Pages, images and APIs

Open and reload the home page and a deep link at the new address. Check public URLs, asset paths and API endpoints for old hostnames or HTTP links.

Sign-in

Update allowed URLs and OAuth callback URLs with your authentication provider. Test sign-in, reload and sign-out. Some providers require the full callback path to match.

Posting, forms and APIs on another host

Add only the required new origins to your app's Origin, CORS and CSRF settings. Submit a test and verify the saved result. Do not disable CORS checks globally.

Human verification, such as Turnstile

The widget owner must allow your rented hostname. Turnstile expects a hostname without a scheme or path. Avoid allowing the whole banchi.app parent, which includes other customers. Check the form at the new address.

Cookies and sessions

Omit the cookie's Domain attribute to scope it to your own host. Do not set it to banchi.app. Different rented addresses can still be considered same-site by browsers. Verify the request origin rather than relying only on SameSite. For __Host- cookies, set Secure; Path=/ and omit Domain.

WebSockets, video and files

If used, test connection, disconnection, reconnection, playback and any required partial downloads at the new address. A successful DNS check does not verify these features.

HTTPS and browsers

Check for certificate warnings, test on a phone and reload after important actions. Do not treat a launch as successful by bypassing certificate warnings.

Turnstile hostnames · CORS · Cookie scope

When something does not work

Still stuck? Use the bug report form. Include your hostname, hosting service, time, steps and diagnostic code. No GitHub account is required and reports are private. Do not include passwords, private keys, cookies or sign-in links.

Supported DNS and differences from owning a domain

Available records

A, AAAA, CNAME, web verification TXT and CAA at your rented name and multiple levels below it. The standard five-record limit includes automatic notice records. Your A/AAAA/CNAME targets are DNS-only; banchi does not proxy your site content. See individual DNS settings.

Not currently configurable

Email setup such as MX, SPF, DKIM and DMARC, NS delegation, wildcards and names outside your rented address. These are current banchi product limits, not prohibitions inherent to subdomains.

Ownership and continued use

You rent the subdomain for your contract period. This does not include ownership of the parent domain or a right to transfer the same name to another registrar. The parent domain's DNS, registration and reputation can have shared effects.

Email, certificates and browser boundaries

Email records such as MX are unavailable. Certificate issuance limits and same-site boundaries may be shared under the parent domain. Scope cookies and authentication permissions to your own hostname.

Traffic and protection

For standard connections, site traffic charges and attack handling depend on your hosting contract and configuration. banchi's fee does not include a server, unlimited destination traffic or destination attack protection.

Changing hosts, stopping renewal and leaving

When changing hosts, register the hostname on the new host first, then change banchi's target and verify it. Some traffic can still reach the old host while DNS changes propagate. Remove the old deployment after confirming the switch.

The price is ¥500 JPY per address per year, including tax. One email can own multiple addresses, with separate contracts and renewal dates. Use Stop auto-renewal for the chosen address and confirm in Stripe. The address remains usable through its paid period. Sales are limited to residents of Japan.

When ending use, first choose Stop connecting and go back to park in banchi and confirm that the connection DNS and TXT records have been removed and the change has propagated. Then remove the custom domain from your host and remove authentication URLs and Turnstile permissions. Removing the host registration first can let someone else claim it while your DNS still points there.

Separately remove the entry from your GitHub account or organization's Verified domains. If you cannot remove it or your banchi address is no longer editable, contact support before the address is rented again. Also contact us if you need to resume use.

See the terms for expiry and release timing

What we verified

• GitHub Pages: On September 6, 2026, we used normal banchi screens to acquire an address and save DNS. Ownership verification, HTTPS, search, saving, sharing and file export were tested on Tsunagicho in a real browser.
• Cloudflare Pages: On September 5, 2026, we measured a DNS-only CNAME connection to a different account and HTTPS. The temporary test connections were removed afterward.
• Mado: Pages, maps and Turnstile were checked with operator-managed routing. This is not evidence of a general customer Workers/R2 connection.
• Vercel: Verified end to end on September 7, 2026, in a real browser against a real Vercel project — saving the connection, DNS diagnosis, certificate issuance and removal. The connected app's own behavior still needs a separate check.
• Netlify: Verified end to end on September 7, 2026, against a real Netlify site — saving the connection, DNS diagnosis, certificate issuance and removal. The connected app's own behavior still needs a separate check.
• Your own server (VPS): Official instructions were compared with banchi's input constraints. End-to-end connection has not been tested.
• Individual DNS records: Support for A, AAAA, TXT, CAA, multiple child levels and DNS-01 CNAME delegation does not mean end-to-end certificate issuance, automated renewal and app behavior have been tested with every host.

Hosting services can change their requirements. If their instructions differ, check the current official documentation and required record types, then contact us if anything is unclear.