Hosting Wiki
A technical knowledge base for hosting, domains, and supporting web infrastructure.
A technical knowledge base for hosting, domains, and supporting web infrastructure.
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.
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.
Protocol for sending and retrieving files from the hosting server. SFTP is the secure version recommended for use today.
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.
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.
Linux file metadata: each file or folder uses one inode. On shared hosting the inode cap can fill while disk space still looks free.
A free certificate authority that issues trusted SSL/TLS certificates for HTTPS, often with auto-renew on hosting panels.
Relational databases where CMS platforms store content, users, and settings — separate from theme files in the document root.