Read unfamiliar links without opening them

Guide Updated 24 October 2026

Read an unfamiliar link by separating its hostname from its user information, path and query, then consider any warning as dated evidence from a particular source. The URL inspector performs that first step locally and shows structural flags without opening the destination.

This site does not scan URLs.

Start with the question you need answered

If the address is unfamiliar, use Read the actual hostname. A familiar word at the beginning of a long address can be user information or a subdomain rather than the destination you expected. The hostname is a defined field in the browser’s URL parser¹; a recognisable word elsewhere in the address does not replace it.

If the link contains a reset token, invitation, document identifier or private account information, start with URL submission privacy. An online inspection service receives information when you submit it. A local structural check answers a narrower question without requiring that submission. You can also decide that the address should not be shared at all.

If you already have a report, use Read a reputation report. Preserve who produced it, when the observation happened and whether it concerns this exact address, a hostname, a download or something else. A failed check and a completed check with no match are different records.

What the inspector shows

The inspector separates the scheme, hostname, port, path, query parameters and fragment. It shows both ASCII and Unicode hostname representations, then uses a bundled Public Suffix List to identify the suffix boundary and any subdomains. That boundary is useful for reading an address; it does not establish who controls it.²

Structural flags call attention to features worth examining: user information before the host, an IP-address host, mixed scripts, a small set of lookalike characters, percent-encoding and a non-default port. These features can also occur in legitimate addresses. The absence of a flag is simply the absence of that particular match.

Nothing pasted into the inspector becomes a clickable destination. The demo also provides a Clear button that removes the current input and output from the page. It cannot erase clipboard history or control software running elsewhere on your device.

Compare evidence without inventing a verdict

The inspection-policy comparison records what services say about submission visibility, retention and sharing. Unknown fields remain unknown. This helps distinguish an existing-report lookup from a new submission and prevents a label such as private from doing more explanatory work than its documentation supports.

The parser dataset shows another limit: different APIs can preserve or normalize the same string differently. It records forty original fixtures across three declared runtimes. The purpose is to make those differences inspectable, not to rank addresses or recommend navigating to them.

Shortened links need an additional distinction. Reading their visible text does not reveal a destination stored by the shortening service. The short-link guide explains the boundary between parsing and making a request.

If you own the site showing a warning

Use the review-route directory to identify the organisation responsible for the specific warning or report. Keep the warning text and the provider’s category separate from your own account of the problem. A browser warning, mail-provider block and hosting-abuse report may involve different systems and different evidence.

Historical report links do not carry forward their old findings here. There is no inherited record of a particular address’s current contents or reputation. The current tools and articles explain how to read evidence and where to find the responsible source.

Not covered on this page

• Live scanning or a destination’s current contents.
• Ownership investigations or incident-response decisions.
• Instructions for bypassing warnings or filters.