Engineering Glossary · Addressing
The Address Is Where Your Latency Budget Gets Spent
The server benchmarks beautifully and visitors still wait, and nobody has separated the network from the application yet.
The short answer
An IP address is a machine's numeric identity on the network — the real destination behind every hostname. Once DNS has produced one, everything that follows is round trips between the visitor and that address, and the number of them multiplied by the distance is most of what people experience as slowness.
So measure the two halves separately. Connect time is distance and routing; the gap between connect and first byte is your server and your application. Optimising the wrong half is the most common wasted afternoon in web performance.
By the HostingFast team · Reviewed 12 August 2026
0
Entries with no jargon left over
100+
Terms, all cross-linked
Real
Worked examples, not diagrams
Free
To read, permanently
IPv4 addresses are scarce enough that shared hosting puts many sites behind one, with the server distinguishing them by the hostname carried in each request. A dedicated address holds the number for one customer, which matters for a handful of specific reasons and for no general ones.
Reputation attaches to addresses. Mail leaving an address inherits everything that address has done previously, which is why serious senders care a great deal about the company an address keeps.
Splitting the wait into its parts
One curl invocation with the timing fields gives you name lookup, connect, TLS handshake and first byte. Subtract each from the next and you have four numbers instead of one impression, and each of those numbers has a different owner.
A large connect time means distance or routing. A large gap between TLS completion and first byte means your application. If the two are both small and the page still feels slow, the problem is in the browser: render-blocking resources, not the server at all.
Diagnosing the network half
When connect time looks wrong, a hop-by-hop trace between the visitor's network and the address shows where the latency accumulates and whether packets are being lost along the way. Persistent loss at a middle hop is a carrier problem, not something a faster server fixes.
Repeat the measurement from more than one network before you conclude anything. A single bad path from one office says more about that office than about your hosting.
When a dedicated address is genuinely warranted
Rarely for the website itself: SNI ended the one-certificate-per-address era long ago and shared addresses serve sites perfectly. The real cases are a legacy integration that allow-lists by address, a firewall arrangement on somebody else's side, and holding your own mail reputation on a server you send from.
That last one is the common one. Part of what gets a VPS owner's mail delivered is the unblemished record of the address it left from, which is one reason a dedicated IPv4 comes attached to every VPS plan we sell.
Addresses on this platform
Shared accounts sit behind a shared address, with free SSL issued per hostname so certificates are never a reason to need your own number. The account's address is visible in the panel whenever you need it for a DNS record or an allow-list.
VPS plans are KVM virtual servers with root access, a dedicated IPv4, DDoS filtering and one flat monthly price — which is the tier to look at if address reputation or an allow-list is the reason you are reading this page.
Split the number before you spend the afternoon
Most performance work goes wrong at the diagnosis, not the fix. These entries are written to get you to the right half of the problem before you start changing things.
Backups run daily on every plan and restoring a file or a database is one click in the panel rather than a support ticket.
- 100+ entries built around measurement
- Network time and server time kept apart
- Wired into IPv6, A Record and DNS
- Written by the engineers who run the platform
Why HostingFast
Standard on every plan
Four numbers, not one
Lookup, connect, handshake and first byte, each with a different owner and a different fix.
IP Address, as a latency budget
The address is where distance is decided, and this entry treats it that way.
Network faults isolated
Hop-by-hop tracing and packet loss, so a carrier problem is not mistaken for a slow server.
Dedicated addresses, honestly
The three real reasons to want one, and the many reasons you do not.
Mail reputation explained
Why the address a message leaves from matters as much as the message.
Continues into its neighbours
IPv6, A Record and VPS follow directly.
Quick Start
From order to online
- 1
Take all four timings at once
Run curl with the timing format string against your own URL and write down lookup, connect, handshake and first byte.
- 2
Decide which half owns the problem
Big connect time is the network. Big gap to first byte is the application. Do not optimise both at once.
- 3
Trace the path when the network is at fault
Run a hop-by-hop trace from an affected network and look for loss or a latency jump at a specific hop.
- 4
Re-measure from a second network
One bad path proves nothing. Confirm from another connection before you escalate anything to anybody.
Built In
Loaded onto every plan
- Account IP address visible in the panel
- Free SSL per hostname, so no address is needed for certificates
- Dedicated IPv4 included with every VPS plan
- KVM virtualisation with full root access on VPS
- DDoS scrubbing handled out at the network edge
- NVMe SSD storage across every tier
- In-place upgrades from shared through to dedicated
- Human support on duty at any hour
Frequently Asked
What people ask us most often
How do I tell whether my site is slow because of the network or the server?
Take connect time and time to first byte in the same curl run. Connect time is distance and routing; the gap between connect and first byte is your server and application. If both are small and the page still feels slow, the delay is in the browser, and no hosting change will touch it.
Does my website need a dedicated IP address?
Rarely. SNI ended the one-certificate-per-address era, and shared addresses serve websites perfectly well. The genuine cases are a legacy integration that allow-lists by address, a third party's firewall arrangement, and holding your own outbound mail reputation on a server you send from.
Can someone find where I live from my site's address?
No. It identifies the server, which means the datacentre and the host, and your own location appears nowhere in the routing. Whatever contact details you choose to publish on the site are a completely separate decision.
What is the refund position if I change my mind?
Thirty days on shared, business, WordPress and WooCommerce hosting; seven on reseller. VPS and dedicated servers are provisioned to order the moment payment lands, so they sit outside the guarantee — as do domain registrations, where the registry charges the instant the name is secured.
Keep reading
IPv6
The newer addressing scheme, and how to check the second path actually works.
VPS (Virtual Private Server)
A slice of a machine with reserved resources, root access and its own address.
How to Set Up a Catch-All Address
Catching mail to addresses nobody created, without inviting the whole internet in.
VPS Hosting
KVM virtual servers with root access, DDoS filtering and a flat monthly price.
Business Hosting
Shared hosting with the full developer toolbelt: SSH, Node.js, Python and PostgreSQL.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Find out which half is slow.
NVMe, LiteSpeed and free SSL on every plan, engineers who answer at any hour, and a renewal price that matches the day you signed up.
View VPS Hosting plans