// DNS

What Is a Nameserver?

A nameserver is part of the Domain Name System. It helps computers discover the DNS records associated with a domain name.

// definition

A nameserver is a DNS server

A nameserver is a server that responds to DNS queries. When talking about domains, the term usually means an authoritative nameserver: a server responsible for providing the official DNS records for a particular DNS zone.

// basic idea

What does a nameserver actually do?

Imagine someone enters:

www.example.com

A computer needs to find out where that hostname should lead.

DNS eventually reaches the nameservers responsible for example.com and asks them for the relevant DNS information.

Domain name | v DNS lookup | v Authoritative nameserver | v DNS record | v Destination

// example

What does a nameserver look like?

A domain may use nameservers such as:

ns1.example-dns.com ns2.example-dns.com

These are hostnames identifying DNS servers.

It is common for a domain to use more than one nameserver so DNS can continue working if one server becomes unavailable.

// records

Nameservers provide DNS records

The nameserver does not normally contain the website itself. Instead, it provides information describing how the domain should behave.

A

Maps a hostname to an IPv4 address.

AAAA

Maps a hostname to an IPv6 address.

CNAME

Makes one hostname an alias of another hostname.

MX

Identifies the mail servers used to receive email.

TXT

Stores text used for verification, security policies and other purposes.

NS

Identifies the nameservers responsible for a DNS zone.

// authoritative

What is an authoritative nameserver?

An authoritative nameserver is considered an official source of DNS information for the DNS zones it serves.

example.com | v Authoritative nameserver | +-- A record +-- CNAME record +-- MX record +-- TXT record

If another DNS server asks for information about example.com, the authoritative nameserver can provide the records configured for that zone.

// NS records

How does DNS know which nameservers to use?

DNS uses NS records.

NS stands for:

Name Server

A simplified configuration might look like:

example.com NS ns1.example-dns.com NS ns2.example-dns.com

These records identify the nameservers responsible for that DNS zone.

// hierarchy

Nameservers are part of the DNS hierarchy

DNS is organised as a hierarchy rather than one enormous central database.

For example:

DNS root | v .com | v example.com | v www.example.com

Each level can help direct DNS queries towards the servers responsible for the next level.

// delegation

What is DNS delegation?

Delegation means assigning responsibility for a DNS zone to particular authoritative nameservers.

For example, the DNS infrastructure responsible for the .com top-level domain can indicate which nameservers are responsible for example.com.

.com | v "Ask these nameservers about example.com" | v ns1.example-dns.com ns2.example-dns.com

// registrar

Where do you set nameservers?

For a registered domain, nameserver settings are commonly managed through the company acting as the domain registrar.

Domain registrar | v Nameserver settings | v DNS provider | v DNS records

You might therefore register your domain with one company while using another company to provide its DNS.

// distinction

Domain registrar, nameserver and web host are different

Domain registrar

Manages the registration of your domain name.

Nameserver

Answers DNS queries and provides DNS records for zones it is authoritative for.

DNS provider

Operates the DNS infrastructure where you manage your records.

Web host

Runs or stores the website or application reached through the domain.

// changing nameservers

What happens when you change nameservers?

Changing a domain's nameservers changes which DNS servers are authoritative for that domain.

Before: Domain | v Old nameservers | v Old DNS records After: Domain | v New nameservers | v New DNS records

Important: changing nameservers is different from changing an individual DNS record. A nameserver change can move responsibility for the entire DNS zone to another provider.

// records vs nameservers

Changing a DNS record vs changing nameservers

Change a DNS record

Keep the existing DNS provider but modify something such as an A, CNAME, MX or TXT record.

Change nameservers

Change the DNS servers responsible for providing the authoritative records for the domain.

// resolver

Nameserver vs DNS resolver

Another important distinction is between a recursive resolver and an authoritative nameserver.

Recursive resolver

Searches for DNS information on behalf of the user and may cache the result.

Authoritative nameserver

Supplies the authoritative DNS records for the zones for which it is responsible.

Browser | v Recursive DNS resolver | v Authoritative nameserver | v DNS answer

// redundancy

Why do domains normally have multiple nameservers?

Domains usually have at least two authoritative nameservers.

ns1.example-dns.com ns2.example-dns.com

This improves resilience. If one nameserver cannot answer a query, another may still be available.

// caching

Why can nameserver changes take time?

DNS information is cached.

After changing nameservers, some DNS resolvers may still temporarily remember older information.

Nameserver change | v Some DNS caches still contain old information | v Cache expires | v Current information is requested

This is part of what people commonly refer to as DNS propagation.

// glue

What are glue records?

Consider this configuration:

Domain: example.com Nameserver: ns1.example.com

DNS needs to locate ns1.example.com before it can ask that nameserver about example.com.

This can create a circular dependency.

A parent DNS zone can therefore provide IP-address information for the nameserver. This information is commonly called glue.

// subdomains

Subdomains can use different nameservers

DNS delegation does not have to stop at the main registered domain.

A subdomain can be delegated to another set of nameservers.

example.com | v Nameservers A api.example.com | v Nameservers B

This can be useful when different systems or teams manage different parts of a domain.

// mental model

The easiest way to remember it

Domain = the name Nameserver = where authoritative DNS answers come from DNS records = the instructions IP address = a network destination Hosting = where the website or service runs

A nameserver therefore does not usually store your website. Its job is to provide the DNS information needed to locate the services associated with your domain.

// summary

Nameservers provide the DNS answers.

A nameserver is a DNS server. In domain management, the term usually refers to an authoritative nameserver that provides the official DNS records for a domain or DNS zone. NS records identify nameservers, while DNS delegation tells the wider DNS system which nameservers are responsible for answering questions about a zone.

// networking

What Is DNS?

DNS is the system that connects human-readable domain names to the servers and services behind them. Without DNS, using the web would usually require remembering numerical network addresses instead of names such as freelancecoder.uk.

// definition

DNS means Domain Name System

DNS, or the Domain Name System, is a distributed system used to translate domain names into information that computers can use to locate internet services.

// basic idea

Domain name to server

People prefer names. Computers ultimately need network addresses and routing information.

Domain name | v DNS lookup | v IP address or another DNS destination | v Server | v Website or service

When you enter a domain into a browser, DNS helps determine where the request should be sent.

// example

A simple DNS lookup

Imagine that a browser needs to open:

www.example.com

The browser needs to determine which server or service is responsible for that hostname.

www.example.com | v DNS | v Destination | v Web server

Once the destination has been found, the browser can begin communicating with the appropriate server.

// distinction

Domain, DNS and hosting are different

Domain

The human-readable name, such as example.com.

DNS

The system that tells computers where services associated with that name can be found.

Hosting

The server or platform that stores and serves the website or application.

Website

The actual pages, files and application content that visitors interact with.

Domain | v DNS | v Hosting | v Website

// records

Common DNS record types

DNS stores different kinds of information in DNS records.

A

Maps a hostname to an IPv4 address.

AAAA

Maps a hostname to an IPv6 address.

CNAME

Makes one hostname an alias of another hostname.

MX

Identifies the mail servers responsible for receiving email for a domain.

TXT

Stores text information. TXT records are commonly used for domain verification and email-related policies.

NS

Identifies the authoritative nameservers responsible for a DNS zone.

// A record

Pointing a domain to an IPv4 address

An A record maps a hostname directly to an IPv4 address.

example.com | v A record | v 203.0.113.10

The exact IP address will depend on the server or hosting platform being used.

// CNAME

Pointing one hostname to another

A CNAME record creates an alias between hostnames.

www.example.com | v CNAME | v hosting.example.net

The DNS system can then continue resolving the destination hostname.

Important: a CNAME points to another hostname, not directly to an IP address.

// email

DNS also controls email routing

DNS is not only used for websites.

MX records tell other mail systems which servers should receive email for a domain.

person@example.com | v DNS MX lookup | v Mail server | v Mailbox system

This is why changing website hosting does not necessarily mean changing email hosting.

// nameservers

What are nameservers?

Nameservers are DNS servers responsible for providing information about domains and DNS zones.

A domain registrar may allow you to select which nameservers are authoritative for your domain.

Domain | v NS records | v Authoritative nameservers | v DNS records

Those authoritative servers contain or serve the DNS records that describe where the domain's services should go.

// hierarchy

DNS is hierarchical

Domain names are organised into levels.

www.example.com www = hostname / subdomain example = registered domain label com = top-level domain

At the very top of DNS is the DNS root.

DNS root | v .com | v example.com | v www.example.com

Terminology: people sometimes informally call example.com the "root domain", but in DNS terminology the actual DNS root is the top of the global DNS hierarchy.

// resolution

How DNS resolution works

A DNS lookup can involve several different systems.

Browser | v DNS resolver | v DNS hierarchy | v Authoritative nameserver | v DNS answer | v Browser

A recursive resolver performs or coordinates the lookup required to obtain the answer for the client.

// caching

DNS answers can be cached

DNS systems often cache previous answers so that every lookup does not have to repeat the full resolution process.

This improves speed and reduces unnecessary DNS traffic.

// TTL

What is TTL?

DNS records commonly include a value called TTL, meaning Time To Live.

TTL tells DNS caches approximately how long a record may be retained before it should be refreshed.

TTL = 3600 3600 seconds = 1 hour

A DNS change may therefore not appear everywhere immediately because some systems may still have an older answer cached.

// propagation

What does DNS propagation mean?

When people say that DNS is propagating, they usually mean that different DNS resolvers and caches are gradually replacing previously cached information with newer records.

Old DNS record | v DNS record changed | v Some caches still contain old answer | v Caches expire and refresh | v New answer becomes widely visible

The term "propagation" is convenient, although much of the delay is actually caused by caching and TTL behaviour.

// URL

DNS does not resolve an entire URL

Consider:

https://www.example.com/articles/dns

DNS is primarily concerned with the hostname:

www.example.com

The rest of the URL is handled by the web request and the server or application.

// IP

DNS and IP addresses

DNS and IP addresses solve different parts of the problem.

Concept	Purpose
Domain name	Human-readable name.
DNS	Resolves names and provides service information.
IP address	Network address used for routing traffic.
Server	Handles requests and provides a service.

// practical

When would you edit DNS?

You may need to change DNS records when:

Connecting a website

Pointing a domain to Blogger, WordPress, a hosting company or another web platform.

Configuring email

Adding MX and other email-related records.

Verifying ownership

Adding a TXT or CNAME record to prove control of a domain.

Creating subdomains

Connecting names such as blog.example.com or api.example.com to services.

// mental model

A useful way to remember DNS

Domain = name DNS = directions IP address = network address Hosting = where the service runs Website = what the visitor sees

DNS acts as the connection between the name people type and the internet service that should receive the request.

// summary

Names need directions.

DNS stands for Domain Name System. It connects domain names with the servers and services behind them using records such as A, AAAA, CNAME, MX, TXT and NS. DNS is separate from the domain itself, the hosting platform and the website content, but it is the system that connects those pieces together.

// blogging platforms

What Is Blogger?

Blogger is Google's hosted blogging platform. It allows users to create and publish blogs without having to configure their own web server or install a separate content management system.

// definition

Blogger is a hosted publishing platform

Blogger is an online service for creating, managing and publishing blogs.

Google operates the underlying platform and hosting infrastructure, while the blog owner manages the posts, pages, design and settings.

This means a user can publish a website without manually maintaining their own web server.

// simple model

Blogger combines publishing and hosting

Write content ↓ Blogger ↓ Google infrastructure ↓ Published website

Much of the technical hosting infrastructure is handled by the platform automatically.

// blogspot

Blogger sites can use a Blogspot address

A new Blogger site can be given an address such as:

example.blogspot.com

The blogspot.com domain is used for Blogger-hosted blog addresses.

// blogger vs blogspot

Blogger and Blogspot are not quite the same thing

Blogger

The publishing and website management platform.

Blogspot

The domain commonly used for Blogger-hosted website addresses.

Blogger ↓ Publishing platform Blogspot.com ↓ Default blog domain

// custom domains

Blogger can use your own domain

A Blogger site does not have to remain on a .blogspot.com address.

A separately registered domain can be connected to the Blogger site.

Before: myblog.blogspot.com After: www.mywebsite.com

The content can remain hosted through Blogger while visitors use the custom domain.

// dns

Custom domains are connected using DNS

Blogger provides DNS information that must be added at the provider managing the domain's DNS records.

A typical configuration includes a CNAME for the website hostname.

www ↓ CNAME ↓ ghs.google.com

Blogger also provides a second verification CNAME associated with the particular blog and Google account.

// root domain

Blogger normally uses a subdomain for a custom domain

A Blogger custom domain is normally configured using a hostname such as:

www.example.com

rather than using only:

example.com

The root domain can then be configured to redirect visitors to the www address.

// example architecture

A custom Blogger site can work like this

example.com ↓ DNS ↓ www.example.com ↓ Blogger ↓ Google hosting infrastructure

The domain can be registered with one company while Blogger hosts the website.

// domain + blogger

Blogger does not have to own your domain

Your domain can be registered through a separate registrar.

Domain registrar ↓ DNS records ↓ Blogger ↓ Website

This keeps domain registration and website hosting as separate components.

// https

Blogger supports HTTPS

Blogspot addresses use HTTPS automatically.

Blogger also supports HTTPS for properly configured custom domains.

http://example.com ↓ https://example.com

HTTPS encrypts communication between the visitor's browser and the website.

// posts

Posts are the main publishing unit

Blogger is designed around publishing posts.

Blog │ ├── Post 1 ├── Post 2 ├── Post 3 └── Post 4

Posts can contain text, images, links, HTML and other content.

// pages

Blogger also supports standalone pages

Pages are useful for content that is not primarily part of the chronological blog feed.

About Contact Services Privacy Policy All Posts

// posts vs pages

Posts and pages have different purposes

Posts	Pages
Usually part of the blog feed	Standalone content
Normally date-based	Usually more permanent
Useful for articles	Useful for About or Contact content

// editor

Blogger includes a post editor

Content can be created through Blogger's editing interface.

Users can work visually or edit the HTML representation of post and page content.

Write post ↓ Add formatting ↓ Add images ↓ Edit HTML if required ↓ Publish

// html

Blogger allows direct HTML

Blogger can be useful for people who want a simple publishing platform but still want access to HTML.

<h2>My Heading</h2> <p> My article content. </p>

More advanced page designs can therefore be created without completely replacing the Blogger platform.

// css

Blogger themes can be customised with CSS

.post-body { font-size: 18px; line-height: 1.7; }

CSS can change colours, fonts, spacing, layouts and many other aspects of the design.

// javascript

JavaScript can add additional behaviour

Custom code can be used to add interactive behaviour to Blogger pages and themes.

HTML + CSS + JavaScript ↓ Custom Blogger experience

This allows Blogger to be extended considerably beyond a basic text blog.

// themes

Themes control the appearance of a Blogger site

Blogger provides themes that determine much of the layout and styling of the site.

Typography Colours Columns Header Sidebar Post Layout

// theme code

Blogger themes can also be edited directly

Blogger provides access to the theme's HTML.

This allows advanced users to modify the site's underlying template and add custom HTML, CSS or supported scripts.

Theme editing gives Blogger considerable flexibility. It is possible to make a Blogger site look very different from the default themes when custom code is used.

// gadgets

Blogger uses gadgets for page components

Gadgets can add sections to the site's layout.

Pages Labels Blog Archive Profile HTML / JavaScript

Gadgets can normally be positioned through Blogger's Layout interface.

// labels

Posts can be organised with labels

Blogger labels act as categories or tags for grouping related articles.

Post: What Is JSON? Labels: JSON APIs Data Programming

Visitors can then browse posts associated with a particular label.

// archive

Blogger maintains a post archive

Published posts have dates and can be organised chronologically.

2026 │ ├── September │ ├── What Is HTML? │ ├── What Is CSS? │ └── What Is JavaScript? │ └── August └── Earlier posts

// feeds

Blogger provides blog feeds

Blogger can expose published content through feeds.

These feeds can be useful for:

RSS Readers Atom Feeds Automation Post Indexes Integrations

// automation

Blogger content can be used programmatically

Feeds and APIs make it possible for software to retrieve Blogger content.

Blogger posts ↓ Feed / API ↓ JavaScript ↓ Automatic post index

This is how an automatically populated All Posts page can be created without manually updating the list every time a new article is published.

// hosting

Blogger includes web hosting

A Blogger user does not normally need to purchase separate traditional web hosting for the Blogger site.

You manage: content design domain settings Google manages: Blogger platform hosting infrastructure

This is one of Blogger's most important characteristics.

// hosted platform

Blogger is different from running your own server

Blogger	Self-hosted website
Hosting infrastructure managed for you	You arrange hosting
Built-in publishing system	You choose or build the software
Platform controls server environment	Potentially greater server control
Simple administration	Can require more administration

// blogger vs wordpress

Blogger and WordPress take different approaches

Blogger	WordPress
Google-hosted publishing platform	Content management system
Hosting built into the service	Can be hosted by many providers
Theme and gadget system	Theme and plugin ecosystem
Designed around straightforward publishing	Can support much broader application structures

WordPress.com is a hosted WordPress service, while the WordPress software itself can also be hosted elsewhere.

// advantages

Why might someone use Blogger?

Hosting Included

The site does not require a separately configured traditional hosting account.

Simple Publishing

Posts and pages can be created through a web interface.

Custom Domains

A separately registered domain can be connected.

Code Access

HTML, CSS and theme code can be customised.

// limitations

Blogger is not a general-purpose server platform

Blogger gives substantial control over content and front-end presentation, but it does not give the site owner the same server-level control as a VPS or self-managed hosting environment.

You cannot simply install any server-side software you want inside Blogger.

Blogger supports: HTML CSS JavaScript Posts Pages Themes Gadgets Feeds Blogger is not: A VPS A PHP server A general-purpose database server

// uses

What can Blogger be used for?

Blogs Educational Sites Technical Articles Personal Websites Small Business Content Tutorials Documentation Affiliate Content

// mental model

The simplest way to think about Blogger

Google account ↓ Blogger ↓ Posts + pages + theme ↓ Google-hosted website ↓ Blogspot address or Custom domain ↓ Visitors

// summary

Publish without managing the server.

Blogger is Google's hosted blogging and publishing platform. It provides website hosting, posts, pages, themes, gadgets, feeds, HTTPS and support for custom domains. Users manage the content and design while Google operates the underlying Blogger infrastructure.

// websites

What Is WordPress?

WordPress is software for creating and managing websites. It provides a content management system that allows pages, blog posts, images, navigation, themes and other website content to be managed through an administrative interface.

// referral disclosure This article contains a WordPress.com referral link. If you use the link and make a qualifying purchase, Freelance Coder may receive WordPress.com account credit. You may also be eligible for referral credit under WordPress.com's current referral terms.

// definition

WordPress is a content management system

WordPress is a content management system, commonly shortened to CMS.

A CMS provides tools for creating, organising, editing and publishing website content.

Instead of manually editing every page as a separate HTML file, WordPress can store content and generate web pages dynamically.

// create a website

Build a website with WordPress.com

WordPress.com combines WordPress with managed hosting, giving you a platform for creating, hosting and managing a website from one service.

Explore WordPress.com ↗

// cms

What does a CMS do?

A content management system separates much of the website's content from the underlying code.

Content ↓ WordPress ↓ Theme + templates ↓ HTML + CSS + JavaScript ↓ Browser

This allows website owners to manage content without manually rebuilding every page.

// content

WordPress can manage posts and pages

Posts

Commonly used for articles, news and other date-based content.

Pages

Commonly used for more permanent content such as About, Contact and Services pages.

// editor

WordPress uses a block-based editor

Modern WordPress content can be assembled from blocks.

Paragraph Heading Image Gallery Columns Buttons Lists HTML

Blocks can be combined to construct pages and posts without manually writing all of the underlying HTML.

// themes

Themes control website presentation

A WordPress theme determines much of a site's visual presentation and page structure.

WordPress content + Theme ↓ Website design

Themes can define typography, colours, layouts, templates, headers, footers and other design elements.

// plugins

Plugins can add functionality

Plugins extend WordPress with additional features.

SEO E-commerce Forms Security Analytics Backups Memberships Automation

This allows a relatively simple WordPress installation to be extended into a much more sophisticated website.

// wordpress software

WordPress is software, not one hosting company

This distinction is important.

WordPress itself is website software that can be installed and hosted by many different hosting providers.

WordPress software ↓ Hosting provider ↓ Website

// wordpress.com vs wordpress.org

WordPress.com and WordPress.org are related but different

WordPress.com	WordPress.org
Hosted WordPress service	Home of the WordPress software project
Hosting is included	Software can be installed with a hosting provider
Infrastructure is managed for you	Hosting arrangements depend on the provider you choose

// wordpress.com

What is WordPress.com?

WordPress.com is a hosted service built around WordPress.

It combines the website software with managed hosting, meaning WordPress.com handles much of the underlying hosting infrastructure.

WordPress + Hosting + Management ↓ WordPress.com

// managed hosting

WordPress.com provides managed hosting

With managed hosting, the hosting provider handles many infrastructure responsibilities.

Hosting Security Backups Caching Updates Infrastructure

// domains

WordPress can use a custom domain

A new WordPress.com site can use a WordPress.com subdomain.

mywebsite.wordpress.com

A site with an appropriate paid WordPress.com plan can instead use a custom domain such as:

mywebsite.com

A domain registered somewhere else can also be connected to WordPress.com on eligible plans.

// domain + hosting

The domain and WordPress website are separate components

Domain name ↓ DNS ↓ WordPress hosting ↓ WordPress website

The domain provides the web address.

The hosting infrastructure runs the website.

WordPress manages the website content and application.

// php

WordPress is built primarily with PHP

WordPress uses PHP extensively on the server side.

Browser request ↓ Web server ↓ PHP ↓ WordPress ↓ Database ↓ Generated response ↓ Browser

PHP code can retrieve content, apply templates and generate the page returned to a visitor.

// database

WordPress stores information in a database

Website information such as posts, pages, settings and user data is typically stored in a database.

WordPress │ ├── Posts ├── Pages ├── Users ├── Settings ├── Comments └── Metadata ↓ Database

WordPress traditionally uses MySQL-compatible database systems for this data.

// web technologies

WordPress still produces ordinary web technologies

Despite the CMS and server-side infrastructure, visitors ultimately interact with familiar web technologies.

HTML

Provides the structure of the rendered page.

CSS

Controls the visual presentation.

JavaScript

Provides interactive browser behaviour.

PHP

Performs substantial server-side WordPress logic.

// cms vs static site

WordPress avoids manually maintaining every HTML file

A simple static website might contain:

index.html about.html contact.html services.html

With WordPress, much of that content can instead be managed through the CMS and generated using reusable templates.

Database content + Theme templates ↓ Generated web pages

// blogging

WordPress is well known for blogging

WordPress began with a strong focus on publishing articles and continues to provide extensive blogging functionality.

Posts Categories Tags Authors Comments Archives

// beyond blogs

WordPress can build much more than blogs

Business Websites Portfolios Blogs Online Stores Membership Sites Documentation News Sites Landing Pages

// ecommerce

WordPress can support online stores

E-commerce functionality can be added to WordPress using systems such as WooCommerce.

WordPress + WooCommerce ↓ Products Orders Payments Customers Storefront

// users

WordPress supports different user roles

Multiple people can work on the same site with different permissions.

Administrator Editor Author Contributor Subscriber

// api

WordPress also has an API

WordPress provides a REST API that can allow other software to interact with WordPress data.

External application ↓ WordPress REST API ↓ WordPress ↓ Posts / Pages / Data

This makes WordPress useful not only as a traditional website CMS but also as a content source for other applications.

// headless wordpress

WordPress can even be used without a traditional theme

In a headless architecture, WordPress can manage the content while another application handles the visible front end.

WordPress CMS ↓ API ↓ JavaScript application ↓ Website

// why wordpress

Why do people use WordPress?

Content Management

Pages and posts can be managed through a CMS.

Themes

Website presentation can be changed and customised.

Plugins

Additional functionality can be added to the site.

Extensibility

Developers can build custom themes, plugins and integrations.

// wordpress.com

WordPress.com removes much of the hosting administration

Running WordPress yourself can involve managing hosting, software updates, backups, security and other infrastructure.

WordPress.com offers managed WordPress hosting, so many of these infrastructure tasks are handled by the platform.

// try wordpress

Interested in building with WordPress?

You can explore WordPress.com, create a website and compare the available options using the Freelance Coder referral link below.

Visit WordPress.com ↗

// referral

WordPress.com referral credit

Under WordPress.com's current Refer a Friend programme, a new customer who follows a valid referral link and purchases an eligible annual WordPress.com plan can receive US$25 in WordPress.com account credit.

The person who referred them can also receive US$25 in WordPress.com account credit.

Monthly plans are not currently eligible for these referral credits. Referral terms can change, so check WordPress.com's current terms before purchasing.

Open Freelance Coder Referral ↗

// official information

WordPress.com information

For current WordPress.com features, hosting information and referral conditions, consult WordPress.com's official documentation.

WordPress.com hosting information ↗

WordPress.com Refer a Friend terms ↗

// summary

Content becomes a website.

WordPress is a content management system used to create and manage websites. It combines content, themes, plugins, databases and web technologies to produce websites ranging from simple blogs to business sites, online stores and larger web applications. WordPress.com provides a managed hosting platform built around the WordPress software.

// referral disclosure Freelance Coder uses a WordPress.com referral link on this page. If you make a qualifying purchase through the link, Freelance Coder may receive WordPress.com account credit. Referral eligibility and benefits are determined by WordPress.com's current terms.