Cybersecurity glossary
What is a Second-Level Domain (SLD)?
Learn what a second-level domain (SLD) is, how it relates to TLDs and subdomains, why SLD ownership matters for security and brand control, and how to protect registered domains.
Definition
A second-level domain (SLD) is the label directly to the left of the top-level domain in a domain name—for example, the example in example.com—typically the name an organization registers and controls under a TLD.
Why second-level domains matter
People say “our domain is example.com.” In DNS vocabulary, example is the second-level domain (SLD) under the .com top-level domain. That registered name is the root of brand websites, email, certificates, and subdomain sprawl.
Losing control of an SLD—through expiry or hijacking—can take down an entire digital identity at once. Understanding SLD vs subdomain vs TLD helps teams scope DNS security correctly.
Where the SLD sits in a name
Consider shop.cdn.example.com:
| Label | Role |
|---|---|
| com | Top-level domain (TLD) |
| example | Second-level domain (SLD) / registrable brand label |
| cdn | Subdomain under the SLD |
| shop | Deeper subdomain under cdn.example.com |
Public Suffix List nuances matter for cookies and registrable domains: example.co.uk is not simply “SLD = co”. Always use public-suffix-aware logic in browsers and security tools.
How SLDs are obtained and used
Choose a TLD namespace
Select .com, a country-code space, or another TLD with acceptable policy and risk.
Register the SLD
Create the registrable domain through a registrar and verify ownership contacts.
Delegate name servers
Point the domain to authoritative DNS that will publish records.
Create records and subdomains
Publish A/AAAA/MX/TXT and create service subdomains as needed.
Issue certificates
Obtain TLS certificates covering the apex and required names.
Protect registration
Lock transfers, enable MFA, monitor changes, and renew reliably.
Security implications of SLD ownership
DNS control plane
Whoever controls the SLD can change NS records and redirect traffic.
Email authenticity
SPF/DKIM/DMARC for the organization hang off the domain namespace.
Cookie and SSO scope
Parent-domain cookie scoping and IdP callbacks often reference the registrable domain.
Certificate surface
Attackers with DNS control may obtain domain-validated certificates for the SLD.
Practical checklist
- Inventory every SLD your brand owns, including legacy and defensive registrations.
- Protect registrar accounts with phishing-resistant MFA and transfer locks.
- Monitor NS/DS changes for each critical SLD.
- Use public-suffix-aware libraries when deciding cookie domain scope.
- Avoid unnecessary subdomain sprawl that expands takeover risk under the SLD.
- Keep WHOIS/registration contacts current for recovery and abuse notices.
- Treat SLD expiry as a Sev-1 business risk with auto-renew and alerting.
- Document which teams may create subdomains under each SLD.
The practical takeaway
A second-level domain (SLD) is the label under a TLD that organizations typically register—the example in example.com. It is the root of DNS, email, and certificate trust for that brand namespace.
Protect SLD registration like production infrastructure, understand public-suffix edge cases, and manage subdomains as delegated risk under that root.
Related security terms
Top-Level Domain (TLD)
The rightmost DNS label such as .com or .org under which SLDs are registered.
Subdomain
Labels under an SLD used to organize hosts and services.
Domain Name System (DNS)
The hierarchical naming system that defines SLD and TLD relationships.
Domain Hijacking
Theft of registration control over an SLD and its namespace.
Frequently asked questions
What is a second-level domain in simple terms?
In example.com, example is the second-level domain. It is usually the brand name you register, while .com is the top-level domain.
Is www.example.com an SLD?
No. www is a subdomain (third-level label). The SLD is still example under the .com TLD.
Who controls an SLD?
The registrant who registered the name through a registrar, subject to registry rules for that TLD.
How is an SLD different from a subdomain?
The SLD is the registered name under a TLD. Subdomains are additional labels created under that SLD by the owner.
Are country-code names always simple SLD.TLD?
Not always. Some namespaces use multi-level public suffixes (for example, example.co.uk), where the registrable domain includes more than one label under the public suffix list.
Why do security teams care about SLDs?
Owning and protecting the SLD controls DNS, email authentication, cookie scope decisions, and certificate issuance for the brand namespace.
Can two organizations share an SLD?
Generally no for the same full registrable domain. Subdomains under one SLD can be delegated to different operators, which creates security trust boundaries.
References
Explore authoritative guidance and frameworks related to second-level domain (sld).
Explore every security definition
Return to the glossary to search by term, alias, starting letter, or security category.