Skip to main content
Custom domains let you replace nearnode.io/v/slug with link.yourbrand.com/v/slug. Your printed QR codes and NFC tags display your brand, not ours. Existing tags continue to work on both domains — no reprinting required.
Custom domains are available on the Pro plan (1 domain) and Enterprise plan (unlimited domains).

Setup

1

Add Your Domain

Navigate to Settings → Domains in the Dashboard. Enter your subdomain (e.g., link.yourbrand.com).
2

Configure DNS

Add two DNS records at your domain registrar:CNAME Record — routes traffic to NearNode’s edge:
TXT Record — proves domain ownership:
The verification token is displayed in the Dashboard after adding the domain.
3

Verify

Click Verify in the Dashboard. NearNode checks your DNS records and activates the domain. Propagation typically takes 5–30 minutes.
4

Live

Once verified, all your nodes automatically resolve on both nearnode.io and your custom domain. No node reconfiguration needed.
Ops Tip: You can verify domain setup via the Dashboard — no API calls required. The status indicator shows Pending, Verified, or Failed with diagnostic details.

SSL / TLS

SSL certificates are provisioned automatically via Let’s Encrypt within minutes of domain verification. No manual certificate management required.
  • Protocol: TLS 1.2 and 1.3
  • Certificate renewal: Automatic, 30 days before expiry
  • HSTS: Enabled by default

API Configuration

Response:

Multiple Domains

Enterprise accounts can configure multiple custom domains per workspace — useful for multi-brand portfolios or regional deployments. All domains resolve the same node inventory. The scan URL domain is recorded in analytics events, allowing you to segment traffic by brand.

Domain Verification API

Check verification status programmatically:

Removing a Domain

Removing a verified domain immediately stops resolving scan URLs on that domain. If you have printed QR codes or written NFC tags with the custom domain, those assets will stop working. The nearnode.io URLs remain unaffected.

Troubleshooting