Logo
Back to Documentation

Custom Domains

Use your own domain for a Mapiry map with DNS verification and custom-domain publishing

Last updated: April 6, 2026

Custom Domains

Mapiry Pro supports one custom domain per map. This lets you serve a map at your own branded URL such as guide.example.com or example.com.

Availability

Custom domains are a Pro feature.

With custom domains:

  • One map can have one custom domain
  • One custom domain can point to one map
  • Both the bare domain and www variant can route to the same map

What You Need

Before starting, make sure you have:

  • A Pro subscription
  • A domain you control
  • Access to your DNS provider or registrar

How Setup Works

Mapiry uses two steps:

  1. Ownership verification
  • Mapiry gives you a TXT record
  • You add it at your DNS provider
  • Mapiry checks that record before activating the domain
  1. Traffic routing
  • You point your domain at Mapiry's current ingress target
  • Once DNS is live and verification succeeds, requests for that host are routed to your map

Add a Custom Domain

  1. Open the map in your dashboard.
  2. Scroll to the Custom Domain section.
  3. Enter the bare domain you want to use, such as example.com.
  4. Click Add Domain.

Mapiry stores the domain and shows the verification instructions you need next.

Step 1: Add the TXT Verification Record

Mapiry will show a TXT record like this:

  • Name: _mapiry-verify.example.com
  • Value: mapiry-verify=<token>

Add that TXT record exactly as shown in your DNS provider.

Notes:

  • Some DNS providers automatically append your root domain
  • If that happens, enter only _mapiry-verify
  • DNS changes may take anywhere from a few minutes to 48 hours

Step 2: Point the Domain at Mapiry

Mapiry also shows the current ingress target to point your domain at.

Use the DNS record type your provider supports:

  • ALIAS or ANAME for apex/root domains when available
  • Flattened CNAME if your provider supports it
  • A / AAAA records if your hosting target uses fixed IPs

If you want both example.com and www.example.com to work:

  • Point both hosts at the same Mapiry ingress target

Step 3: Verify the Domain

After DNS is in place:

  1. Return to the map's Custom Domain section
  2. Click Verify Domain

If the TXT record matches:

  • Mapiry marks the domain as verified
  • The domain becomes active for that map

If verification fails:

  • Double-check the TXT record name and value
  • Wait a bit longer for DNS propagation
  • Click Verify Domain again

Removing a Custom Domain

To remove a custom domain:

  1. Open the map
  2. Go to Custom Domain
  3. Click Remove Domain

This clears the domain from the map and stops Mapiry from routing that host to it.

Important Limits

  • One custom domain per map
  • One map per custom domain
  • Custom domains are intended for full-map publishing, not per-section routing
  • Subpaths like example.com/map1 and example.com/map2 are not supported as separate map bindings

Troubleshooting

Verification keeps failing

Check:

  • The TXT record name matches exactly
  • The TXT record value matches exactly
  • DNS changes have propagated
  • You are verifying the same domain you registered in Mapiry

Domain opens the wrong site

Check:

  • Your domain is pointed at Mapiry's current ingress target
  • The www host is also pointed correctly if you use it
  • You do not have conflicting DNS records from an older hosting setup

Bare domain works but www does not

Create a DNS record for www that points at the same target as the bare domain.

HTTPS certificate is not active yet

HTTPS availability depends on DNS propagation and Mapiry's current hosting setup. If DNS was just changed, wait for propagation and certificate issuance to finish.

Best Practices

  • Use a dedicated map domain when possible, such as guide.example.com
  • Avoid changing DNS repeatedly during setup
  • Keep your map slug stable even though visitors will usually see the custom domain
  • Test in an incognito window after verification

What's Next?

Related Articles