Built for agencies and B2B sales teams.

Start free →

Free Tracking Domain Checker

Check CNAME or address resolution, the hostname relationship, HTTPS readiness and redirect signals for a branded tracking domain.

DNS (CNAME / A)Web (HTTPS / TLS)Flow (redirect readiness)
Tracking Domain CheckerFreeExample result
Enter the exact hostname configured in your email platform, not a campaign's final destination URL.
HEALTHY
92/100

links.acme-outreach.com is resolving

CNAME foundHTTPS readyBranded child hostname
links.acme-outreach.com CNAME tracking.provider.example.
Hostnamelinks.acme-outreach.com
DNS pathCNAME
HTTPSAvailable
StepExamplePurpose
1links.acme-outreach.comBranded hostname
2Provider tracking edgeRecord the click and resolve the token
3Destination URLFinal visitor page
DNS hostname resolves
Parent-domain relationship confirmed
HTTPS appears ready
How it works

How to use the Tracking Domain Checker

  1. 01

    Enter the exact tracking hostname

    Copy it from your outreach platform.

  2. 02

    Review DNS and HTTPS

    Check the record, the certificate and the redirect signal.

  3. 03

    Test a real campaign link

    Do this after your provider has verified the domain.

What it checks

What the Tracking Domain Checker checks

DNS resolution

What the hostname points to.

CNAME awareness

Provider delegation is visible.

HTTPS readiness

Avoid insecure tracking links.

Redirect flow

Understand the click path.

Brand-domain relationship

The hostname belongs to your brand.

Provider setup context

DNS status is separate from your platform's verification.

Reading results

The click path

A tracking hostname lets a platform attribute clicks while using your domain namespace.

StepExamplePurpose
1links.example.comBranded hostname
2Provider tracking edgeRecord the click and resolve the token
3Destination URLFinal visitor page
Step by step

Why a tracking subdomain exists

  1. 01

    A recipient clicks

    A branded link such as https://links.example.com/abc123.

  2. 02

    DNS routes the request

    It points to the tracking service.

  3. 03

    HTTPS responds

    The endpoint answers with a valid certificate.

  4. 04

    The visitor arrives

    They are sent to the final URL.

Common issues

Common problems and how to fix them

CNAME target typo

Compare DNS with the exact value from your platform.

DNS propagated, provider pending

Finish ownership or activation inside the platform.

HTTPS certificate not ready

Allow certificate issuance to finish, then retest.

Redirect loop or dead destination

Test a real generated link end to end.

A checker verifies public infrastructure only

DNS can resolve while provider verification, certificates or redirects are still pending. Only your platform can confirm tokens, analytics and campaign redirects. A branded domain does not make links inherently trustworthy, and a healthy result does not guarantee that clicks are recorded.

Use cases

When to run this check

Pre-campaign QA

Retest after DNS, platform or certificate changes.

Changing providers

Check the new target, certificate and redirects.

Agency onboarding

Confirm a client's branded tracking domain.

FAQ

Tracking Domain Checker FAQ

Still unsure? Read the DevBoxy blog or contact the team.

What is a tracking domain checker?

It tests the DNS and web readiness of the click or open tracking hostname before you use it in campaigns.

What is a branded tracking domain?

A subdomain you control that you configure with your email platform, so tracked links use your brand instead of the platform's.

Should a tracking domain use CNAME or A records?

Follow your platform's instructions. Many use CNAME delegation. The checker reports what actually resolves.

Does a tracking domain affect deliverability?

It contributes to link trust but is not a standalone deliverability control. Authentication, reputation, complaints and content still matter.

Is HTTPS important for tracking links?

Yes. For production use, tracking links should be served over HTTPS with a valid certificate.

Why does my CNAME exist but the tracking link still fails?

Verification, certificate issuance, routing or redirect setup may be incomplete. Check the whole chain.

Should the tracking hostname be a child of my sending domain?

A branded child hostname is the common pattern and keeps the tracking identity clearly related to your brand.

Can I use the root domain as a tracking domain?

A dedicated subdomain is usually safer, because it separates tracking from your main website.

What should I test after changing tracking providers?

DNS propagation, the new target, certificate readiness, redirects and a real generated link.

Does a healthy tracking domain guarantee clicks will be recorded?

No. Privacy features, browser behavior and platform configuration can still affect analytics.

Pair DNS checks with list verification.

Healthy authentication protects your domain. Clean contacts protect your sender reputation. Cleaner outreach starts with better data.