How do I find the domain registrar and nameservers used by Shopify?
Updated on 20 Oct 2026: We updated the lookup steps for RDAP and clarified supported DNS hosting, propagation checks, and Shopify sender authentication.
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 an RDAP lookup for the registrar, then run a DNS NS lookup for the nameservers. Use WHOIS as a fallback where it is still available. Shopify sells domains as a reseller through accredited registrar partners, so a Shopify-bought domain can show the partner's name in registration data. If the domain was bought elsewhere and connected to Shopify, that provider remains the registrar unless the domain was transferred.
Shopify does not publish one dependable nameserver set for every customer domain. Shopify's manual connection guide specifies the domain provider's default nameservers and Shopify's A, AAAA, and www CNAME records. Its provider-specific connection guidance also supports keeping DNS with a separate DNS host in supported configurations. Check the instructions for your DNS host before changing delegation. For Shopify-managed domains, the DNS settings page is where A, AAAA, CNAME, MX, TXT, and SRV records are edited.
Direct answer
- Use RDAP on the exact domain to find the registrar. A Shopify-bought domain can list an accredited registrar partner.
- Query the domain's NS records to find its nameservers. Do not infer them from Shopify's corporate domains.
- Follow the supported connection instructions for your DNS host and update the required web records there.
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 hosts the storefront application and specifies the records needed to route web traffic to the store. Email records sit in the same DNS zone unless a subdomain is delegated, and email sending often uses a separate system.
The phrase "used by Shopify" can therefore 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. Identify the control layer before changing anything.
Shopify-managed domain
- Registrar: An accredited partner can appear in RDAP while Shopify remains the customer-facing reseller.
- DNS edits: Handled inside Shopify admin for supported record types.
- Best clue: Shopify admin shows DNS management, billing, and renewal controls for the domain.
Third-party domain
- Registrar: The accredited registrar shown in registration data, with billing handled by the provider account.
- DNS edits: Handled at the active authoritative DNS host, which can differ from the registrar.
- Best clue: Shopify admin shows connection status, while billing and renewal stay with the provider.
Shopify admin Settings > Domains with A, AAAA, CNAME, MX, TXT, and SRV record controls.
Check Shopify admin first
If store access is available, Shopify admin provides the quickest first-party check. Go to Settings > Domains and select the exact custom domain. The details page shows its connection status and whether DNS can be managed in Shopify.
- Open Domains: In Shopify admin, go to Settings > Domains.
- Select the domain: Use the custom root domain, such as example.com or example.co.uk, rather than the myshopify.com address.
- Check management: For a Shopify-managed domain, open DNS settings > Manage to view the record controls.
- Confirm externally: Compare the admin result with RDAP and public NS records.
A connected third-party domain still uses Shopify for storefront routing, but registration, billing, and renewals stay with the domain provider. DNS remains with the active DNS host. A domain bought through Shopify or transferred to Shopify is managed in Shopify admin. Public lookups remain useful because access, delegation, and ownership can change independently.
How to find the registrar
For generic top-level domains (gTLDs), start with RDAP, which replaced WHOIS as the definitive registration-data source under ICANN's RDAP transition. WHOIS remains a fallback where the registry still provides it, including some country-code top-level domains (ccTLDs). The registrar field identifies the registration provider. A domain registered through Shopify can list an accredited partner rather than Shopify.
The registration result also provides registrar identifiers and domain status codes, with abuse contact details where published. Redacted registrant contact information does not prevent you from identifying the registrar. These results do not establish where DNS is hosted or email is sent; those require separate DNS checks.
WHOIS fallback command, where supportedBASH
whois example.com
- Check RDAP through the registry or registrar's RDAP service. In raw JSON, look for an entity with the registrar role and its IANA registrar identifier.
- Use WHOIS only where supported. Look for Registrar, Registrar IANA ID, and Registrar URL fields.
- Compare the registrar identity with your Shopify account. A reseller name and an accredited registrar name can differ without indicating a problem.
- 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 | Registration or transfer restrictions | Check holds and transfer locks |
Registrar lookup fields that matter
How to find the nameservers
For nameservers, query the domain's NS records. An ordinary lookup uses a recursive resolver and can return a cached answer. The parent-zone delegation and the domain's authoritative NS answer should agree; investigate differences before changing email or storefront records.
Nameserver fingerprinting alone cannot reliably identify a Shopify-registered domain. Registration, DNS hosting, and storefront hosting can move independently. Compare the returned NS hostnames with your DNS provider account, then follow Shopify's supported connection instructions for that DNS host.
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
Shopify admin confirms domain management, while RDAP and NS records identify the registrar and DNS authority.
Do not use Shopify's own domain as the pattern
Shopify's corporate domains can use DNS selected for Shopify's own infrastructure. That does not prove what a customer domain bought through Shopify uses. Check each customer domain directly.
|
|
|
|---|---|---|
NS | Delegated authoritative nameservers | Registrar or storefront host |
A | IPv4 destination for the queried hostname | Registrar |
CNAME | Alias target | Registrar or DNS account 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 root domain uses A, AAAA, and www CNAME records at the domain provider. These records do not replace NS delegation. Shopify currently requires one apex A record, one apex AAAA record, and one www CNAME pointing to Shopify.
Common Shopify web DNS recordsDNS
@ A 23.227.38.65 @ AAAA 2620:0127:f00f:5:: www CNAME shops.myshopify.com.
The IPv4 address above is Shopify's default, but Shopify can provide a regional address with another 23.227.38.x host value. Treat the value shown in Shopify's connection flow or DNS settings as valid. If a provider rejects the condensed IPv6 address, use 2620:0127:f00f:0005:0000:0000:0000:0000. Keep the provider's default TTL.
For a third-party domain, edit records at the authoritative DNS host and follow the supported setup for that host. Connecting a domain changes storefront routing; transferring a domain changes its registration provider. A transfer is not required just to connect the storefront. If a nameserver change is necessary, export and recreate every active record before moving delegation. For a Shopify-managed domain, make supported DNS changes in Shopify admin and verify the public answers afterward.
Shopify domain lookup flowchart showing WHOIS registrar discovery, an NS lookup, and DNS record editing.
Verify DNS changes and propagation
After a DNS edit, compare the parent delegation with the authoritative answers. Then check the answer returned by your usual recursive resolver.
Trace delegation and compare DNS answersBASH
dig +trace example.com NS dig @ns1.example.net example.com NS +norecurse dig @ns1.example.net _dmarc.example.com TXT +norecurse dig _dmarc.example.com TXT
Replace example.com with your domain and ns1.example.net with a nameserver found in the trace. For a delegated subdomain, query its own authoritative server. The dig documentation explains delegation tracing and direct server queries. Check for the aa flag in direct replies to confirm an authoritative answer.
- If the parent delegates to old nameservers, check the nameserver settings with the registration provider.
- If the authoritative answer is wrong, correct the record in that DNS zone. Waiting will not repair an incorrect value.
- If the authoritative answer is correct but the recursive answer is old, allow the cached record to expire according to its TTL.
Shopify allows up to 24 hours for managed DNS changes and up to 48 hours for connection and certificate setup. If the problem persists after that window, contact the DNS host or Shopify Support with your lookup results.
Why this matters for email authentication
Authoritative DNS for each hostname decides where email authentication records must be added. SPF is published for the SMTP MAIL FROM (return-path) domain, while DKIM is under selector._domainkey for the signing domain. DMARC is checked under _dmarc for the visible From domain, with organizational-domain policy discovery where applicable. A TXT or CNAME record added in a control panel that is not authoritative will not appear in public DNS.
After finding the active DNS host, Suped's domain health checker makes DMARC, SPF, and DKIM problems visible in one place. For proof from a real sent message, the email tester checks the message headers as well as the published records.
?
What's your domain score?
Deep-scan SPF, DKIM & DMARC records for email deliverability and security issues.
Shopify automatically configures sender authentication for domains purchased through Shopify; verify those records before changing them. For a third-party sender domain, go to Settings > Notifications > Sender email, start domain authentication, and publish every CNAME value Shopify provides at the authoritative DNS host. Removing those CNAME records can cause deliverability failures. Other sending systems can require separate SPF, DKIM, or return-path records.
Shopify's sender authentication guidance states that its generated CNAME records handle SPF and DKIM, so no separate SPF TXT record is needed for that setup. Keep a valid DMARC record and edit the existing record rather than creating a duplicate. Preserve an existing stronger DMARC policy when authenticating Shopify.
For subdomains, check whether the sending system expects records at the root domain or under a delegated label. A delegated subdomain can have different authoritative nameservers, so query the exact SPF, DKIM, DMARC, CNAME, and MX hostnames rather than assuming the apex zone controls them.
A practical lookup workflow
Collect the evidence in this order to avoid treating a Shopify web record as proof that Shopify is the registrar or DNS host.
- Normalize domain: Start with the registrable root domain, such as example.co.uk, then check www and each sending or delegated subdomain.
- Find registrar: Use RDAP and record the registrar name and IANA ID, with WHOIS as a fallback where supported.
- Find nameservers: Run an NS lookup, trace delegation if needed, and identify the active DNS host.
- Check web records: Look for Shopify A, AAAA, and CNAME targets, allowing for Shopify-assigned regional A records.
- Check email records: Inspect MX, SPF, DKIM, and DMARC at each authoritative DNS zone.
- Decide control: Use Shopify admin for DNS only when the domain is Shopify-managed.
Example evidence fileTEXT
Domain: example.com Registrar: <registrar name from RDAP> Registrar IANA ID: <ID from registration data> NS: ns1.example.net NS: ns2.example.net A: 23.227.38.65 AAAA: 2620:0127:f00f:5:: CNAME www: shops.myshopify.com.
Use the evidence file carefully
The sample shows the type of notes to 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 identifies the correct control panel. Suped is our DMARC and email authentication platform. After a DNS change, use it to review reported sending sources and investigate authentication failures.
Suped's DMARC monitoring shows reported SPF and DKIM results so you can identify affected sending sources. Compare these results with the published DNS records before making another change.
DMARC record detail view showing SPF, DKIM, DMARC, rDNS diagnostics, and DNS records
Suped's blocklist monitoring adds domain and IP blocklist (blacklist) status when investigating delivery problems.
Common traps to avoid
Most Shopify domain mistakes come from acting on the wrong control layer. Check the layer first, then make the change to avoid breaking storefront or email records.
|
|
|
|---|---|---|
Wrong login | DNS changes ignored | Check NS first |
Unsupported DNS setup | Domain connection fails | Follow the DNS-host-specific connection steps |
Duplicate A | Apex conflict | Keep one value |
Wrong zone | Email fails auth | Publish at authority |
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. Shopify's Reset DNS settings also deletes custom mail and subdomain records. Export the zone before using it.
Views from the trenches
Best practices
Start with RDAP, then confirm delegation with public NS lookups for the exact domain.
Record registrar, nameservers, web records, 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 records in a control panel when its nameservers are not authoritative.
Expert tips
For asset discovery, compare registration data with NS, web, and email records before labeling.
If registration data is unclear, compare structured RDAP data with Shopify admin domain status.
When moving DNS, export the old zone first and verify mail records at the new authoritative servers.
Expert view
Shopify can be the customer-facing reseller while WHOIS or RDAP identifies an accredited registrar partner for the exact domain.
2022-11-10 - Email Geeks
Expert view
Nameserver fingerprinting alone is unreliable because registration, DNS authority, and storefront routing can change separately.
2022-11-10 - Email Geeks
