Keep the merchant as owner
Use organization-controlled contact information, billing, renewal, MFA, recovery, and delegated access.
Domain and registrar operations
Keep domain ownership, DNS, email, certificates, redirects, and launch responsibility visible.
Porkbun is a registrar CMS Max teams may use during managed domain work; it is not a native CMS Max application plugin. The right launch method depends on who owns DNS, the required CMS Max records, existing email, subdomains, verification records, and the approved cutover plan.
Operating model
Avoid single-person ownership, undocumented credentials, unreviewed nameserver changes, and launch plans that ignore email or third-party records.
Use organization-controlled contact information, billing, renewal, MFA, recovery, and delegated access.
Record website, email, verification, subdomain, application, TTL, redirect, and security-related records.
A domain can usually point to hosting without moving registrar ownership; use the method approved for the project.
Current CMS Max capability
Porkbun controls registrar and optional DNS services; CMS Max supplies the accepted website endpoint, certificates, redirects, and launch requirements.
Keep registration, renewal, contacts, privacy, transfer lock, and recovery under the approved organization account.
Apply only the CMS Max records and third-party records required for the live architecture.
Decide whether Porkbun or another approved service remains authoritative for DNS.
Retain MX, SPF, DKIM, DMARC, verification, and related records exactly as required by the mail provider.
Verify root, www, certificates, redirects, preferred hostname, and all HTTP-to-HTTPS behavior.
Use provider forwarding only for the accepted use case and choose temporary or permanent behavior deliberately.
Step-by-step workflow
Record before-state evidence and lower TTLs only under the approved change plan.
Verify the registrant, organization access, MFA, renewal, recovery, billing, and authorized contacts.
Capture every current record, nameserver, TTL, forwarding rule, subdomain, and dependent service.
Use the exact current endpoint and verification requirements supplied for the tenant.
Test root, www, HTTPS, redirects, forms, email, subdomains, analytics, and critical integrations.
Watch DNS propagation and certificates, preserve rollback data, then update ownership and renewal records.
Practical reference
Porkbun documentation distinguishes registrar transfer, DNS pointing, nameserver changes, and URL forwarding.

Current references
Interfaces, policies, plans, services, pricing, and requirements can change. Verify the current CMS Max configuration and official provider sources during implementation.
Porkbun Domain Management FAQ
Turn each answer into configuration, representative testing, monitoring, ownership, and a documented recovery path.
No. Porkbun is a registrar and DNS provider used in some domain workflows; the CMS Max application does not need a Porkbun plugin to serve the website.
Usually no. The domain can remain with the organization registrar while approved DNS records point to CMS Max.
Any record not recreated in the new DNS zone, including email, verification, subdomains, third-party applications, and security records.
Porkbun documents automatic HTTPS for its forwarding service, subject to the current provider configuration and domain requirements.
The customer organization should retain durable ownership, renewal, billing, MFA, recovery, and authorized access.
Build for real operations
CMS Max can coordinate the website endpoint, redirects, certificates, verification, and cutover checklist with the organization domain owner.
The world's fastest and most SEO friendly website code.