![\"Project](\"https://cdn.brandfetch.io/tailscale.com/fallback/lettermark/theme/dark/h/256/w/256/icon?c=1bfwsmEH20zzEfSNTed\")
Last validated: Jan 12, 2026
\nA Tailscale network (known as a tailnet) is a secure, interconnected collection of users, devices, and resources. Your tailnet is your private space, inaccessible from the public internet. It's akin to a secure conference room where only invited participants can enter. It forms the foundation of Tailscale's approach to networking, providing a flexible yet controlled space for device connectivity, resource sharing, and collaboration across the internet.
\nTailscale creates a tailnet when you first log into Tailscale on any device, be it a phone, personal computer, or virtual machine (VM). Each time you (or another user in your organization) authenticate a device with Tailscale, it adds that device to the tailnet. You can authenticate devices using a Tailscale account (for users) or a tag (for service-based devices).
\nEach tailnet is identified by a tailnet DNS name, and used for features like MagicDNS, HTTPS, and sharing without revealing your organization's identity. You can choose between a default tailnet name (for example, tailfe8c.ts.net) or a personalized tailnet DNS name (such as yak-bebop.ts.net). You can find and manage your tailnet DNS name on the DNS page of the admin console.
Each device in your tailnet receives a private Tailscale IP address within the CGNAT (Carrier-Grade Network Address Translation) range. Some addresses within this range are reserved for Tailscale services. Tailscale IP addresses facilitate direct communication between all your devices, regardless of physical location. It's like having your own personal, secure internet that spans wherever your devices are located.
\nSome pricing plans extend the functionality of tailnets, allowing businesses and organizations to accommodate numerous devices and users, integrating seamlessly with various identity providers such as Microsoft Entra ID, Google Workspace, GitHub organizations, or Okta tenancies. These integrations streamline user access and resource management based on existing organizational structures.
\nYou (or another user with the correct permission) can find and manage tailnet settings through the admin console. The admin console lists all devices and users within the tailnet and provides access to tailnet-wide settings and configurations. Some settings include access control policies, DNS settings, and authentication settings.
\nYou can also manage your tailnet in other ways. For example, you can:
\nAdd entire subnets to your tailnet with subnet routers.
\nRoute traffic with exit nodes.
\nRoute and manage application-specific traffic with app connectors.
\nSet up high availability features.
\nConfigure network and application based access policies using grants.
\nControl how traffic routes through your tailnet using via.
\nIncrease security with features like Tailnet Lock.
\nManage logging, streaming, and events.
\nTailnets also support sharing features. You can invite users to your tailnet or share specific devices with them. Sharing and invites let you securely share internal services with other Tailscale users, including those outside your organization (such as contractors). Individuals can also share resources like a personal Minecraft server with friends while maintaining network security. You can create access control policies to manage what an invited user can do in your tailnet.
\nIn addition to sharing and invites, you can leverage features like Tailscale Serve and Tailscale Funnel to temporarily share access to specific services running on a device in your tailnet.
\nAsk AI
\nreCAPTCHA
\nRecaptcha requires verification.
\nprotected by reCAPTCHA
\n"}