How do I find the domain registrar and nameservers used by Shopify?
Michael Ko
Co-founder & CEO, Suped
Published 10 Jun 2025
Updated 4 Jun 2026
8 min read
Summarize with
The fastest way to find the registrar and nameservers used by a Shopify domain is to check the exact domain, not Shopify in general. Run a WHOIS or RDAP lookup for the registrar, then run a DNS NS lookup for the nameservers. If the domain was bought through Shopify, the registrar layer often points to Tucows or OpenSRS, with Shopify acting as the customer-facing reseller. If the domain was bought elsewhere and connected to Shopify, the registrar is usually that original domain provider.
I do not treat Shopify as having one dependable public nameserver set for every customer domain. For third-party domains, Shopify's manual connection guide tells you to keep nameservers managed by the domain provider and point records at Shopify. For Shopify-managed domains, the DNS settings page is where A, AAAA, CNAME, MX, TXT, and SRV records are edited.
Direct answer
- Registrar: Use WHOIS or RDAP on the exact domain. Shopify-bought domains often show Tucows Domains Inc. or OpenSRS.
- Nameservers: Query the domain's NS records. Do not infer them from Shopify's own corporate domains.
- Shopify connection: For most third-party domains, change DNS records, not nameservers.
What Shopify actually controls
A Shopify store can involve several separate control points. The registrar controls the domain registration. The authoritative nameservers control DNS answers. Shopify controls the storefront application and the records needed to route web traffic to the store. Email records sit in the same DNS zone, but email sending often uses separate providers.
That distinction matters because the phrase "used by Shopify" can mean different things. A domain can be registered through Shopify, have DNS edited in Shopify, point its web records to Shopify, and still send email through a separate system. I start by identifying which layer I need.
Shopify-managed domain
- Registrar: Often Tucows or OpenSRS behind Shopify, confirmed by WHOIS or RDAP.
- DNS edits: Handled inside Shopify admin for supported record types.
- Best clue: Shopify admin access plus matching WHOIS registrar output.
Third-party domain
- Registrar: The company where the domain was bought or transferred.
- DNS edits: Handled wherever the authoritative nameservers point.
- Best clue: A, AAAA, and CNAME records point to Shopify, but NS records do not have to.
A Shopify Admin domain settings screen showing where DNS records are managed.
How to find the registrar
For the registrar, start with WHOIS or RDAP. The registrar field is the direct answer for the registration layer. If the domain was registered through Shopify, I expect to see a backend registrar rather than "Shopify" as the formal registrar name. Tucows Domains Inc. and OpenSRS are common signals for Shopify-bought domains, but the lookup result for the exact domain wins.
The registrar result also tells you where transfer locks, renewal status, and abuse contacts live. It does not prove where DNS is hosted and it does not prove where email is sent. Those require separate checks.
Registrar lookup commandsBASH
whois example.com rdap -j example.com
- Check WHOIS: Look for Registrar, Registrar IANA ID, and Registrar URL fields.
- Check RDAP: Use RDAP when WHOIS output is redacted, inconsistent, or hard to parse.
- Compare examples: If you are doing asset discovery, compare several confirmed Shopify-bought domains.
- Avoid assumptions: A Shopify-hosted storefront does not mean the domain was registered through Shopify.
|
|
|
|---|---|---|
Registrar | Registration provider | Best first clue |
IANA ID | Registrar identity | Useful for matching |
Name server | Delegated DNS | Confirm with DNS |
Status | Transfer state | Migration planning |
Registrar lookup fields that matter
How to find the nameservers
For nameservers, query the live NS records. The parent zone delegation and the domain's authoritative answer should agree. If they do not agree, treat the result as a DNS issue that needs investigation before you change email or storefront records.
Nameserver fingerprinting is useful, but it is weaker than registrar lookup for identifying a Shopify-registered domain. A domain registered through Shopify can use custom nameservers. A domain not registered through Shopify can still point web records to Shopify. A reseller-backed domain can also change defaults over time.
Nameserver lookup commandsBASH
dig NS example.com +short nslookup -type=NS example.com
Confidence levels for Shopify identification
Use several signals together when deciding whether a domain is Shopify-managed or only Shopify-hosted.
Low confidence
Visual check only
Only the site looks like a Shopify storefront.
Medium confidence
DNS web records
A and CNAME records point at Shopify web infrastructure.
High confidence
Multi-signal check
WHOIS, NS records, and Shopify admin evidence all match.
Do not use Shopify's own domain as the pattern
Shopify's corporate domains can use DNS providers selected for Shopify's own infrastructure. That does not prove what a customer domain bought through Shopify uses. Customer domains need direct checks.
|
|
|
|---|---|---|
NS | Who answers DNS | Who hosts web |
A | Apex routing | Registrar |
CNAME | Alias target | DNS owner |
MX | Inbound mail | Storefront host |
What each DNS clue proves
Shopify DNS records are not nameservers
The most common confusion is mixing up nameservers with Shopify's required web records. Shopify's manual setup for a third-party domain is about A, AAAA, and CNAME records. Those records live wherever DNS is already hosted. They are not a replacement for the domain's NS delegation.
Common Shopify web DNS recordsDNS
@ A 23.227.38.65 @ AAAA 2620:0127:f00f:5:: www CNAME shops.myshopify.com.
If the domain is third-party, I leave nameservers at the domain provider's defaults unless there is a planned move to another DNS host. If the domain is Shopify-managed, I make supported DNS changes in Shopify admin. If the registrar and DNS host are different, I ignore the registrar login for DNS edits and go to the nameserver provider instead.
A flowchart showing WHOIS lookup for registrar and NS lookup for DNS host.
Why this matters for email authentication
The same DNS authority that answers web records also decides where SPF, DKIM, and DMARC records must be added. If I add a TXT record at the registrar but the nameservers point elsewhere, nothing useful happens. The record can look correct in one control panel and still fail in public DNS.
After I know where the domain's DNS lives, I check the domain with Suped's domain health checker so DMARC, SPF, and DKIM problems are visible in one place. If I need proof from a real sent message, the email tester checks the actual headers instead of only the DNS records.
?
What's your domain score?
Deep-scan SPF, DKIM & DMARC records for email deliverability and security issues.
For Shopify stores, this becomes important when marketing platforms, transactional mail, support desks, or custom sending subdomains enter the mix. A store owner can have a clean Shopify storefront and still have broken email authentication because records were placed in the wrong DNS account.
For subdomains, I also check whether the sending service expects records at the root domain or under a delegated label. The setup patterns in email subdomains apply here because the authoritative nameserver still decides which TXT, CNAME, and MX records are real.
A practical lookup workflow
When I need a defensible answer, I collect the evidence in this order. It avoids the common mistake of treating a Shopify web record as proof that Shopify is the registrar or the DNS host.
- Normalize domain: Check the apex domain first, then repeat for www and sending subdomains.
- Find registrar: Use WHOIS or RDAP and record the registrar name and IANA ID.
- Find nameservers: Run an NS lookup and confirm which provider answers public DNS.
- Check web records: Look for Shopify A, AAAA, and CNAME targets.
- Check email records: Inspect MX, SPF, DKIM, and DMARC at the active DNS host.
- Decide control: Use Shopify admin only when Shopify is managing the domain's DNS.
Example evidence fileTEXT
Domain: example.com Registrar: Tucows Domains Inc. Registrar IANA ID: 69 NS: a.ns.shopco.com NS: b.ns.shopco.com NS: c.ns.shopco.com A: 23.227.38.65 CNAME www: shops.myshopify.com.
Use the evidence file carefully
The sample above shows the kind of notes I keep, not a universal Shopify default. If one field changes, update the conclusion. Registrar, NS, web, and email records can move independently.
Where Suped fits
Registrar and nameserver discovery gets you to the right control panel. The next job is making sure email authentication is actually healthy. Suped is the best overall DMARC platform for most teams because it turns DNS findings into monitored DMARC, SPF, DKIM, blocklist, and blacklist workflows instead of leaving them as one-time lookup notes.
In Suped's DMARC monitoring, I can see which sources pass or fail authentication, whether a Shopify-adjacent sending setup is missing DKIM, and what steps fix the issue. Suped also brings blocklist monitoring into the same workflow, which helps when DNS mistakes affect reputation.
DMARC record detail view showing SPF, DKIM, DMARC, rDNS diagnostics, and DNS records
The practical value is simple: once the authoritative DNS host is known, Suped helps track whether the records there are right, whether changes caused failures, and whether a domain's mail starts appearing on a blocklist or blacklist. That is more useful than saving a registrar screenshot and hoping nothing changes later.
Common traps to avoid
Most Shopify domain mistakes come from acting on the wrong layer. I check the layer first, then make the change. That saves time and prevents broken storefront or email records.
|
|
|
|---|---|---|
Wrong login | DNS changes ignored | Check NS first |
Wrong NS | Store not live | Use provider default |
Duplicate A | Apex conflict | Keep one value |
Missing TXT | Email fails auth | Add at DNS host |
Shopify domain troubleshooting traps
High-risk mistake
Do not move nameservers before copying every active record, including MX, SPF, DKIM, DMARC, verification TXT records, and subdomain records. A clean storefront cutover can still break email if the old DNS zone had records that were not recreated.
Views from the trenches
Best practices
Start with WHOIS, then confirm delegation with live NS lookups for the exact domain.
Record registrar, nameservers, A, CNAME, MX, SPF, DKIM, and DMARC in one shared note.
Use Shopify admin for DNS only when the domain is actually managed inside Shopify.
Common pitfalls
Do not assume Shopify has one public nameserver set for every customer domain or store.
Do not treat Shopify web records as proof that Shopify registered the domain itself.
Do not add email TXT records at the registrar if NS records point somewhere else.
Expert tips
For asset discovery, combine registrar, NS, web, and email signals before labeling.
If WHOIS is vague, compare RDAP output and repeated checks on confirmed domains.
When moving DNS, export the old zone first and verify mail records after cutover.
Expert from Email Geeks says Shopify appears to resell Tucows or OpenSRS for domain registration, but the exact WHOIS result should lead the analysis.
2022-11-10 - Email Geeks
Expert from Email Geeks says nameserver fingerprinting alone is unreliable because domains can use default, custom, or external DNS.
2022-11-10 - Email Geeks
The reliable answer
To find the domain registrar used by Shopify for a specific domain, check WHOIS or RDAP. For Shopify-bought domains, expect Shopify as the customer-facing place to manage the domain and Tucows or OpenSRS as a common backend registrar signal. To find the nameservers, query the domain's NS records and trust the live DNS delegation.
For third-party domains connected to Shopify, do not look for a universal Shopify nameserver set. Keep the nameservers where DNS is managed, then add Shopify's A, AAAA, and CNAME records there. For Shopify-managed domains, use Shopify admin for DNS changes and verify the public records afterward.
