top-level domain
The last part of a domain name, after the final dot, such as com, org or uk.
In more detail
Top-level domains sit at the top of the domain name system and are managed by registries under global coordination. Some are generic, such as com and org, and others belong to countries, such as uk. Attackers sometimes register a brand name under a different top-level domain to create a lookalike.
Example
In example.com the top-level domain is comRelated terms
- domain name — A human-readable name, such as www.example.com, organised as labels from most specific on the left to the top-level domain on the right.
- DNS — The system that turns names such as learnsome.tech into IP addresses.
- lookalike domain — A domain name made to resemble a trusted one, such as evilexample.com next to example.com, to trick people or filters.
Taught in
- Social Engineering, Phishing & Human Defense — Cybersecurity Fundamentals, GRC & Cryptography
- Public Key Infrastructure: X.509 Certificates & CAs — Cybersecurity Fundamentals, GRC & Cryptography
- Privacy Principles, GDPR Subject Rights & Minimization — Cybersecurity Fundamentals, GRC & Cryptography
- Data Loss Prevention & Egress Monitoring — Cybersecurity Fundamentals, GRC & Cryptography
- Security Capstone Review & Certification — Cybersecurity Fundamentals, GRC & Cryptography
- The Merge Request That Deployed To Production — GitLab Certified CI/CD Associate Exam Prep
- How The Exam Works: Fifty Questions, No Notes — GitLab Certified CI/CD Associate Exam Prep
- Continuous Integration, Delivery And Deployment: One Keyword Apart — GitLab Certified CI/CD Associate Exam Prep
- From Push To Runner: How GitLab Starts A Pipeline — GitLab Certified CI/CD Associate Exam Prep
- Anatomy Of .gitlab-ci.yml, And Three Ways To Check It — GitLab Certified CI/CD Associate Exam Prep
- Jobs And Stages: Who Waits, Who Runs, Who Gets Skipped — GitLab Certified CI/CD Associate Exam Prep
- Rules, Workflow Rules And The Legacy only And except — GitLab Certified CI/CD Associate Exam Prep
- Reuse With extends And include, And What Survives The Merge — GitLab Certified CI/CD Associate Exam Prep
- Stages Versus Needs: Building The Pipeline As A Graph — GitLab Certified CI/CD Associate Exam Prep
- Parent, Child And Multi-Project Pipelines — GitLab Certified CI/CD Associate Exam Prep
- Artifacts: Which Files Reach Which Jobs — GitLab Certified CI/CD Associate Exam Prep
- Caching: Dependencies That Survive Between Pipelines — GitLab Certified CI/CD Associate Exam Prep
- CI/CD Variables: Where Values Come From, And Which One Wins — GitLab Certified CI/CD Associate Exam Prep
- Environments, Review Apps And Deployments — GitLab Certified CI/CD Associate Exam Prep
- The Container Registry: Build, Tag, Push, Clean Up — GitLab Certified CI/CD Associate Exam Prep
- Package Registries: Publishing With The Job Token — GitLab Certified CI/CD Associate Exam Prep
- Adding GitLab's Security Scanners To A Pipeline — GitLab Certified CI/CD Associate Exam Prep
- Reading Security Results: The Merge Request And The Vulnerability Report — GitLab Certified CI/CD Associate Exam Prep
- Runner Types And Executors: Who Runs The Job, And Where — GitLab Certified CI/CD Associate Exam Prep
- Registering Runners And Routing Jobs With Tags — GitLab Certified CI/CD Associate Exam Prep
- Debugging Pipelines: The Graph, The Errors, The Logs — GitLab Certified CI/CD Associate Exam Prep
- Faster Pipelines: Minutes You Can Win Back — GitLab Certified CI/CD Associate Exam Prep
- Pipeline Clinic: Five Tickets, Five Fixes — GitLab Certified CI/CD Associate Exam Prep
- Recall Sprint: Knowing It Cold, With No Docs And No AI — GitLab Certified CI/CD Associate Exam Prep
- Final Mock And Review: One Question Short — GitLab Certified CI/CD Associate Exam Prep
- Debian Packages: dpkg, apt And The Sources List — LPIC-1 Linux Administrator (101-500 and 102-500) Exam Prep
- Client DNS: Files First, Then The Server — LPIC-1 Linux Administrator (101-500 and 102-500) Exam Prep