Help Center › Custom Domains - Branding and Profile URLs
Overview
By default, all NFC Tagify profile links use the id.nfctagify.com domain — for example, id.nfctagify.com/?id=abc123. If your company has its own domain, you can connect it to NFC Tagify so that your employees' profiles appear under your own URL instead, such as cards.yourcompany.com/jane-smith.
Custom domains give your digital cards a more professional, on-brand appearance and reinforce trust when contacts tap or scan a card.
---
What Custom Domains Do
When a custom domain is configured and verified, any public profile link belonging to your company will resolve through your chosen domain rather than the NFC Tagify default. The full profile URL structure becomes:
`
https://[your-domain]/[profile-slug]
`
Everything else — analytics, QR codes, NFC tap behaviour — continues to work exactly as before. No re-programming of physical cards is needed once the domain is verified.
---
Prerequisites
Before you begin, make sure you have:
- Ownership of a domain — you need a domain name registered with any registrar (e.g. GoDaddy, Namecheap, Cloudflare Registrar, Google Domains).
- DNS management access — you must be able to log in to your DNS provider and add or edit records. If your IT team controls DNS, loop them in before starting.
- Company Admin role — only Company Admins and above can configure custom domains in the NFC Tagify portal.
---
Step-by-Step Setup
1. Add the Domain in the Portal
cards.yourcompany.com) and click Add Domain.A verification DNS record will be displayed on screen. Copy this — you will need it in the next step.
2. Add the DNS Record at Your Registrar
Log in to your DNS provider and add the record shown in the portal. This is typically a CNAME record pointing your chosen subdomain to NFC Tagify's servers:
| Type | Name | Value |
|------|------|-------|
| CNAME | cards (or your chosen subdomain prefix) | [NEEDS VERIFICATION: target hostname shown in portal] |
If you are using a root/apex domain (e.g. yourcompany.com with no subdomain), you will need to add an ANAME or ALIAS record instead. Not all DNS providers support these record types — using a subdomain (e.g. cards.yourcompany.com) is generally simpler and more compatible.
3. Verify the Domain
Return to the portal and click Verify. NFC Tagify will check that the DNS record exists and resolves correctly. If verification fails, wait a few minutes and try again — DNS changes sometimes take time to propagate locally even if they are correct.
4. Wait for SSL Provisioning
Once verified, an SSL certificate is automatically provisioned via Cloudflare. This usually completes within a few minutes. Your domain will show a status of Active once the certificate is in place and HTTPS is working.
Do not share the custom domain URL with your team until the status is Active.
---
SSL Certificates
SSL is handled automatically — you do not need to purchase or install a certificate yourself. NFC Tagify uses Cloudflare to provision and renew certificates on your behalf. Certificates are renewed automatically before they expire, so there is nothing ongoing for you to manage.
If the SSL status shows an error after 15 minutes, check that your DNS record is correctly pointed and that there are no conflicting records (such as an existing A record for the same subdomain).
---
DNS Propagation Time
DNS changes can take anywhere from a few minutes to 48 hours to propagate worldwide, depending on your DNS provider and the TTL (time-to-live) settings on your records. In practice, most providers complete propagation within a couple of hours.
If your domain shows as unverified for more than an hour:
- Double-check the record type and value in your DNS settings.
- Try a DNS checker tool ([NEEDS VERIFICATION: recommended tool URL]) to confirm the record is visible globally.
- Ensure you have not added the full domain as the record name (e.g.
cards.yourcompany.com.yourcompany.comis a common mistake).
---
Troubleshooting
Verification keeps failing
Confirm the CNAME record name and value match exactly what the portal displays. Some DNS providers automatically append your domain to the name field — check that the resulting full record is correct.
SSL certificate not provisioning
Ensure no other DNS records for the same subdomain conflict with the CNAME. A common issue is having an A record and a CNAME on the same subdomain simultaneously.
Profiles still showing on id.nfctagify.com
The domain must show Active status in the portal before profile URLs switch over. If the domain is active but profile links still show the old URL, try refreshing your portal session.
Domain was working but has stopped
Check whether you accidentally deleted or changed the DNS record. If your domain registration has expired, reinstate it and the SSL certificate will re-provision automatically.
---
Frequently Asked Questions
Can I use my root domain (e.g. yourcompany.com) instead of a subdomain?
Yes, but it requires an ALIAS or ANAME record rather than a CNAME, and not all DNS providers support this. A subdomain such as cards.yourcompany.com is recommended for broader compatibility.
Can different departments have different custom domains?
No. Custom domains are configured at the company level and apply to all profiles within that company. Individual departments or profiles cannot use separate domains.
Will existing NFC cards stop working if I add a custom domain?
No. Physical NFC cards are programmed with a redirect URL. Existing taps will continue to resolve correctly regardless of domain changes.
Do I need to renew or manage the SSL certificate?
No. SSL certificates are provisioned and renewed automatically by NFC Tagify. You do not need to take any action.
What happens if I remove a custom domain?
Profile URLs will revert to using id.nfctagify.com. Any QR codes or printed links using the custom domain will stop resolving correctly, so plan any removal carefully.
---
Related: [Company Settings](../help-pages/company-settings.md) · [Profile URLs and Slugs](../help-pages/profile-urls.md) · [Reseller Custom Domains](../help-pages/reseller-custom-domains.md)