Introduction

Python can get the system hostname with a small standard-library call. In most cases socket.gethostname() is the right answer, but it helps to understand what that value means and how it differs from the machine's fully qualified domain name.

The Usual Method: socket.gethostname()

The standard and most direct approach is socket.gethostname().

1import socket
2
3hostname = socket.gethostname()
4print(hostname)

This returns the host name configured for the local machine. It is usually what people want for logging, diagnostics, or tagging output with the current machine identity.

A small helper function is often enough:

1import socket
2
3
4def get_hostname() -> str:
5    return socket.gethostname()
6
7
8print(get_hostname())

That works on Windows, macOS, and Linux because the socket module is cross-platform.

When platform.node() Is Good Enough

Python also exposes platform.node(), which returns the machine's network name.

import platform

print(platform.node())

In many environments, this gives the same result as socket.gethostname(). If your code already uses the platform module for other system details, this may be a convenient alternative. Still, socket.gethostname() is the more common answer when the question is specifically about the hostname.

Hostname Versus Fully Qualified Domain Name

Sometimes people ask for the hostname but actually need the fully qualified domain name, or FQDN. These are not always the same.

• Hostname might be something short such as app01
• FQDN might be something longer such as app01.example.internal

If you need the FQDN, use socket.getfqdn():

1import socket
2
3print("hostname:", socket.gethostname())
4print("fqdn:", socket.getfqdn())

Whether getfqdn() returns something more useful depends on local DNS and host configuration. On some machines it may look identical to gethostname().

Getting the Name for Logging or Metrics

A common practical use is to stamp logs, metrics, or reports with the host name. It is often helpful to fetch it once at startup and reuse it rather than calling for it repeatedly throughout the codebase.

1import logging
2import socket
3
4HOSTNAME = socket.gethostname()
5
6logging.basicConfig(level=logging.INFO)
7logger = logging.getLogger(__name__)
8
9logger.info("service started on host=%s", HOSTNAME)

This pattern keeps host identity consistent across all log messages and avoids duplicating the lookup logic.

Environment Variables Are Less Reliable

You may see code that uses environment variables such as COMPUTERNAME on Windows or HOSTNAME on Unix-like systems. That can work, but it is less portable and less trustworthy than using the standard library.

1import os
2
3hostname = os.environ.get("COMPUTERNAME") or os.environ.get("HOSTNAME")
4print(hostname)

This approach depends on the environment being populated the way you expect. In containers, services, shells, or restricted execution environments, those variables may be missing or overridden. Prefer socket.gethostname() unless you have a specific reason to rely on environment configuration.

Common Pitfalls

• Using environment variables instead of the standard library and then getting inconsistent results across machines.
• Expecting the hostname to always be a fully qualified domain name.
• Assuming socket.getfqdn() will always return a useful domain name even when DNS is not configured.
• Looking up the hostname repeatedly in many places instead of reading it once and reusing it.
• Confusing the local host name with the public network name visible from outside the machine.

Summary

• Use socket.gethostname() for the normal Python answer to "what is this machine's hostname".
• 'platform.node() is a reasonable alternative but is less commonly used for this specific task.'
• Use socket.getfqdn() only when you specifically need the fully qualified domain name.
• Avoid depending on HOSTNAME or COMPUTERNAME environment variables unless your environment guarantees them.
• For logging and diagnostics, read the hostname once and reuse it consistently.