A SMALL FIELD GUIDE TO THE WEB

Every link has
a journey.

Learn to read the address, understand the detour, and recognise where you actually arrive.

Plain language. Practical examples. A little more clarity.

FIELD NOTE / 001THE LINK JOURNEY
01
THE ADDRESS YOU CLICKexample.com/hello
A request reaches the server
02
A CHANGE OF DIRECTION“This page has moved.”
302
The browser follows a new address
03
WHERE YOU ARRIVEexample.com/welcome

An illustration of a redirect.
Your browser makes each request in turn.

Read the addressFollow the journeyUnderstand the contextKeep asking why

01 / THE HANDS-ON PART

Take a link apart.

Paste a web address to see its parts.
The inspector reads the text in your browser.

This tool doesn’t visit the address or trace its redirects.

THE ADDRESS, EXPLAINEDExample URL
Scheme
https:

How the browser connects.

Hostname
example.com

The host named in this address.

Path
/guide

The resource being requested.

Query
?topic=links

Extra parameters for the request.

Fragment
#basics

A reference handled by the browser.

Parsing an address doesn’t establish who owns it, whether it is safe, or where it ultimately leads.

02 / THE FIELD GUIDE

Three things worth knowing.

A few useful ideas for the next time
a link takes an unexpected turn.

01

THE ADDRESS

Look at the hostname.

A web address contains several parts. The hostname identifies the server being addressed; the path and query come after it. A familiar word inside a path doesn’t make it the name of the host.

https://example.com/a-familiar-nameThe highlighted part is the hostname.

HTTPS encrypts the connection. It doesn’t establish that the organisation or content is trustworthy.

Read MDN’s URL guide
02

THE DETOUR

One click can make
several requests.

A server can respond with a redirect status and a new address in a Location header. The browser then requests that address. Moving a page or shortening a link are ordinary reasons to use a redirect.

301 Permanent move302 Temporary redirect

A page can also navigate using JavaScript or an HTML refresh. The address you first click and the address you eventually see can differ. Inspecting the complete sequence explains the change.

Read MDN’s redirect guide
03

THE CONTEXT

The previous page
may leave a clue.

A request may include a Referer header describing where it came from. Referrer policies limit what is shared: sometimes it’s a full address, sometimes only the origin, and sometimes nothing.

https://example.com/An origin-only referrer leaves out the path and query.

An absent search term doesn’t establish that a search never happened. A referrer is a limited piece of context, rather than a complete browsing history.

Read MDN’s referrer-policy guide

03 / PUT IT INTO PRACTICE

A small pause.
A clearer picture.

When the destination surprises you, record what happened before drawing a conclusion.

  1. 01

    Keep the original address

    The visible label and the underlying link can be different. Record both.

  2. 02

    Note where you arrive

    Check the address bar after the page has finished loading.

  3. 03

    Separate facts from guesses

    A redirect shows a change of destination. Explaining why requires more evidence.

A FEW COMMON QUESTIONS

Good questions.
Short answers.

Does the inspector open the link?

No. It uses your browser’s URL parser to read the text you enter. It doesn’t contact the destination or check whether the page exists.

Can it tell me if a website is safe?

No. The results describe an address’s structure. They aren’t a reputation check or a security verdict.

Why do some addresses have long parameters?

Query parameters can describe searches, preferences, campaign information or other application data. Their exact meaning depends on the service that uses them.

Who makes this site?

Aanlyn Link Lab is an independent educational project published under the name Linkfield Studio. Read about the project.