Stable HTTPS endpoints

Publish localhost with a custom domain and a stable HTTPS URL

Reserve a custom HTTP domain on Plus or Pro, prove ownership with TXT, configure CNAME or apex A records, and publish localhost with HTTPS.

Written and reviewed by: ProxlaneOperated by CloudruUpdated: 2026-10-03

Plans

Plus / Pro

Ownership

Request-specific TXT

Scope

HTTP domains, no wildcard

Before you start

Install and authenticate the CLI

Install the Windows or Linux CLI, run proxlane login as the same OS user, and approve the device in your browser. Start the local service you want to publish.

Read the installation guide

Have DNS access and an available reservation

You need control of the domain's DNS. Plus allows one total reserved HTTP hostname or custom domain; Pro allows five. Pending requests also count toward this quota.

Step by step

01
Request the hostname
Open Dashboard → Endpoints, choose Custom domain, and enter a hostname such as app.example.com. Copy the ownership TXT name and exact value shown for this request.
02
Publish ownership and routing records
Add the request-specific TXT record at _proxlane-verification.app.example.com. For a subdomain, add a CNAME to proxlane.com. For an apex such as example.com, use matching relay A records or provider ALIAS/ANAME flattening.
03
Verify DNS in the Dashboard
Keep the TXT record published. Click Verify DNS after routing propagates. The CLI doctor helps diagnose routing but does not replace ownership verification in the Dashboard.
```
proxlane doctor domain app.example.com
nslookup -type=TXT _proxlane-verification.app.example.com
nslookup -type=CNAME app.example.com
```
04
Start and test the custom-domain tunnel
Once verification succeeds, publish your running local HTTP app. Open https://app.example.com from another device or network and confirm the expected app responds.
```
proxlane http --domain app.example.com 3000
```

Use the correct apex and IPv6 records

An apex cannot use a standard CNAME. A-record routing succeeds when the hostname's addresses all match the relay's A records. If AAAA records exist, they must also match the relay's IPv6 addresses. Disable DNS-provider proxying when it hides the direct routing target.

nslookup -type=A proxlane.com
nslookup -type=A example.com
nslookup -type=AAAA example.com

Keep ownership and routing valid

A pending request does not reserve the hostname globally. Verification establishes your reservation. The relay checks ownership and routing when a custom-domain tunnel starts, and maintenance rechecks existing domains. Keep the request's TXT proof and routing records in place while using the domain.

Protect and keep the endpoint running

Custom domains use the same Dashboard policies as reserved Proxlane HTTP hostnames. Saved Basic Auth or Bearer changes apply on the next tunnel start. Saved IP and country rules normally reach new traffic within seconds. Use a background profile when the URL needs to stay available after your terminal closes.

proxlane http --background --name custom-web --domain app.example.com 3000
proxlane service status --profile custom-web

Troubleshooting

Ownership TXT is missing

Use the exact value from this request, not a different endpoint's token. Check the complete _proxlane-verification hostname and allow DNS propagation before retrying.

Routing does not match

Check CNAME for a subdomain or A records for an apex. Remove unrelated AAAA records and disable proxy mode when the DNS provider returns its own edge addresses.

Domain is not verified or already reserved

Complete Dashboard verification with the account that will start the tunnel. A verified hostname held by another reservation cannot be claimed until that reservation is released.

Frequently asked questions

Can Free use a custom domain?

No. Custom domains share the reserved HTTP-hostname quota available on Plus and Pro.

Does this give my TCP or UDP tunnel a custom hostname?

This workflow is for HTTP domains. TCP and UDP tunnels use public host-and-port endpoints and their separate port reservations.

Proxlane