.tn domains and SSL: connect your store without breaking email
Understand registration accounts, DNS records and HTTPS before connecting a store domain. Save existing settings, preserve email and test pages and redirects without copying a generic server address or assuming instant propagation.
Connecting a domain does not mean replacing every DNS record. The task is to direct web visits to your store while preserving email and other services. First identify the registrar, the active DNS manager and the values your store platform currently requires for your account. A server address copied from an old video may be wrong. This guide explains how to understand and review the work; actual configuration values must come from your service’s current instructions.
Separate ownership, DNS and hosting
The registrar manages registration and renewal. The DNS manager holds routing records. The store service receives visits. These roles may sit with one provider or several. Keep the registration account and recovery email under business control and record renewal dates. The official ATI WHOIS service provides information about names registered with it; a lookup does not guarantee registration or establish a right to a trademark.
If someone connects the name for you, ask who owns the account and how access can be recovered. Avoid passwords posted in group conversations. Choose the primary address, with or without www. Both forms may require configuration followed by a redirect to the primary. Deciding before distributing links reduces later changes.
Understand the records involved
A points to an IPv4 address, AAAA to IPv6 and CNAME to another name. MX concerns email, while TXT carries text such as verification and mail settings. Do not add a random AAAA value: an old IPv6 destination can make results differ across devices. Cloudflare’s DNS field documentation explains names, values and cache duration when you need clarification.
| Field | Check before editing |
|---|---|
| Name | Root, www or correct subdomain |
| Type | Matches platform instructions |
| Value | Comes from your current account |
| Existing MX and TXT preserved | |
| TTL | Cache duration, not a universal deadline |
Save the zone before changing it
Export records or capture complete names, types, values and TTLs. Keep a private dated copy. Changing nameservers is broader than changing a website record: necessary services must exist at the new DNS manager. Review email, verification records and subdomains. Ask what an unfamiliar record does rather than removing it.
In a fictional example, a merchant pays 36 TND annually for the domain and 24 TND for separate email, totalling 60 TND. Those invoices do not reveal where services are managed. Changing the website generally does not mean buying email again; it means preserving its configuration. The figures are illustrative, not ATI, Matjri or other provider prices.
Connect the website and test before sharing
Add the domain in the available store settings and carefully enter the required values. When using Matjri for your store, follow account-specific connection instructions or support guidance rather than inferring an IP from another site. Check that the name opens your store, not a default page. Try two connections if possible because cached results can temporarily differ.
Do not repeatedly change records every few minutes when an old page appears. First confirm the saved value and whether you edited the active DNS manager. A correct entry in an unused zone changes nothing. Send an email to the business address and reply from it as well; a functioning website does not prove functioning mail.
Understand the meaning of HTTPS
HTTPS protects the connection to the visited name. It does not certify product quality or every commercial statement. The Let’s Encrypt getting-started guide explains certificate issuance through a suitable client. Hosted providers often manage this part. Never ask customers to bypass certificate warnings or share a private key. Have the domain, certificate and destination checked before promoting a link showing an alert.
Google and Meta verification is separate
Opening a store successfully does not establish ownership inside search or advertising tools. Each service has its own token. Copy the token from your account to the required location and verify it. Do not replace email settings or remove a successful token without understanding why it remains necessary. This diagram summarises ownership verification only, not the complete DNS or SSL process.
Is connecting www enough?
Follow instructions for every name you intend to use and test primary and alternative addresses. One working does not prove the other. Check that redirects preserve product paths rather than sending every visit to the homepage.
Why does the site work while email has stopped?
Mail records may have been lost during a DNS-manager or nameserver change. Compare the saved zone and contact the email provider. Do not copy arbitrary settings from another store.
What proves the connection is complete?
The correct store opens without warnings, links work, alternatives redirect correctly and email sends and receives. Start today by inventorying accounts and records. A preserved configuration makes a change reviewable and recoverable.