Hosting Wiki
A technical knowledge base for hosting, domains, and supporting web infrastructure.
A technical knowledge base for hosting, domains, and supporting web infrastructure.
Linux file metadata: each file or folder uses one inode. On shared hosting the inode cap can fill while disk space still looks free.
Apache per-folder config for redirects, rewrites, protection, and forcing HTTPS — one bad edit can cause HTTP 500.
How two systems request and exchange data. In hosting, APIs power panel automation, DNS, deploys, and integrations without manual clicks every time.
Extra domains on the same hosting account. One plan, multiple sites — with separate document roots, email options, and shared resource limits to understand.
Copies of files and databases for recovery after breakage or bad updates. Frequency, offsite storage, and tested restores beat brochure labels.
How much data moves between your site and visitors over a period — usually per month. Different from load speed, even though people mix the two up.
A global server network that speeds up websites by serving content from locations closest to your visitors.
DNS proxy + CDN + security in front of origin. Free plans often suffice; SSL and cache settings still need care.
Scheduled server tasks for backups, queues, and maintenance. Bad timing can hammer resources at peak hours.
Cryptographic email signatures so receivers can verify mail from your domain was not altered in transit.
A DNS policy for what receivers should do when SPF or DKIM fails, plus aggregate reports to watch spoofing.
The system that turns domain names into IP addresses. In hosting, DNS points your domain at the right server — separate from the site files themselves.
DNS instruction rows (A, AAAA, CNAME, MX, TXT, …) that point names to IPs, mail, and verification services.
DNS security extensions that sign zone data so resolvers can detect forged or altered answers in transit.
An IP address used only by your account. Not required for modern SEO, but useful for legacy apps, allowlists, or some mail cases.
The public folder where the web server looks for your site index — often public_html. Wrong root means uploads still 404.
"Domain privacy (WHOIS privacy) hides the registrant's name, email, and phone from public lookups. Understand how it works, its limits, and when it is worth it."
The process of propagating DNS changes to all servers in the world after you change nameservers or update domain records.
A concurrent PHP process limit on shared hosting. Often behind Error 508 — not a daily visitor cap.
Error 429 Too Many Requests appears when a server limits how many requests are allowed in a short window. Understand the mechanism and fixes.
A 500 Internal Server Error means the server failed for an unspecified reason. Here are the usual suspects, how to read the logs, and what to avoid.
A 503 Service Unavailable means the server received your request but can't handle it right now. Here's what triggers it and how to respond without SEO damage.
File transfer to your hosting server demystified: what FTP and SFTP each do, the encryption difference, and what you need to connect.
HTTP transfers web pages; HTTPS adds SSL/TLS encryption. Why HTTPS is the default and how to migrate safely.
Moving files, databases, mail, and DNS to a new host with a plan that keeps downtime and errors low.
Hotlinking happens when another website loads your files directly from your server URL. Your bandwidth pays the bill. Here is how to prevent it.
A unique address that identifies servers and devices on the internet. Learn the difference between shared vs dedicated IPs and when you need to upgrade.
"IPv6 is the replacement for IPv4, offering an effectively endless supply of IP addresses. Learn how it works and when it actually matters for your hosting."
A free certificate authority that issues trusted SSL/TLS certificates for HTTPS, often with auto-renew on hosting panels.
A load balancer distributes incoming requests across a group of servers. Understand the mechanics, the algorithms, and when a website truly needs one.
Website malware slips in through outdated plugins, weak logins, or uploads. Learn the warning signs and the right first steps to clean an infection.
Relational databases where CMS platforms store content, users, and settings — separate from theme files in the document root.
Authoritative DNS servers that answer where your domain points. Wrong nameservers mean A/MX edits elsewhere never go public.
OPcache keeps compiled PHP bytecode in server memory, so requests skip the parsing step. Here's how it works, when it helps, and what to watch out for.
An object cache keeps database query results in memory so the same query doesn't run over and over. Here's how it works and when WordPress needs one.
The server-side language behind WordPress and many CMS platforms. PHP version affects security, speed, and plugin compatibility.
PHP-FPM executes PHP through a pool of workers ready to serve requests. Here's how the pool works, what worker limits mean, and how they hit performance.
"A PTR record is the reverse of an A record: it maps an IP address back to a hostname. Learn why it drives email deliverability and how to verify yours."
A parked domain mirrors your primary site instead of running its own. Understand its real uses and the difference from addon domains and subdomains.
"RAM is the short-term memory a server uses to run PHP, MySQL, and every live process. Learn how it works and how to size it for your hosting plan."
"A domain registrar is the ICANN-accredited company authorized to register names. Learn what it actually controls and which fees to check before buying."
A reverse proxy stands in front of your web server: it receives requests, forwards them, and returns responses. Here are its functions and hosting impact.
The standard protocol that a server uses to send email. It's important to make sure your business emails are delivered and don't end up in the spam folder.
A DNS record that lists which servers may send email for your domain — a core anti-spoofing control with DKIM and DMARC.
Encrypted terminal access to a server for Git, CLI, and repairs — deeper than FTP alone.
The technology behind HTTPS that encrypts data between browser and server — foundation for trust, forms, and online transactions.
A copy of your site environment for testing before production — usually on a subdomain with separate files and database.
A domain branch like blog.example.com — useful for staging, apps, or site sections without buying another domain.
DNS Time To Live: how long resolvers may cache an answer before asking again. A key lever for propagation speed.
2FA requires a password plus a second code to log in. A practical guide for site owners: turning it on in cPanel, WordPress, and domain accounts.
The percentage of time the server runs normally without interruption. This number determines how reliable your hosting is in keeping your website accessible.
A web application firewall filters dangerous HTTP requests before they hit the app — it complements updates and backups.
Domain registration records: registrar, expiry, status, and contacts (often redacted). Useful for availability and renewal checks.
WP-CLI runs WordPress from the terminal: core updates, search-replace, cron, and database exports. A practical guide for VPS users and developers.
Storing expensive work (HTML, queries, assets) so the next request is faster and cheaper on server resources.
HTTP software on the server — Apache, Nginx, or LiteSpeed — that serves files and hands work to PHP.
"A wildcard SSL certificate protects *.yourdomain.com — the main domain plus all its subdomains — without issuing a separate certificate for each one."
A web-based control panel that allows you to manage hosting, email, domains and databases without the need for technical expertise.
A web UI for MySQL/MariaDB: export, import, and emergency SQL. An admin tool — always back up before changing data.
"A vCPU is the virtual processor core you rent on a VPS or cloud plan. Understand how it is allocated and what the number really means for performance."