A proposed destination is not a recorded journey
Redirect Parameters and Short Links: What Text Reveals
A URL can mention another URL without sending anyone there. A short address can hide its mapping entirely. These are different reading problems. Local inspection helps you separate the address you were given from possible destinations written inside it, while leaving actual navigation behavior unknown.
The Link Inspector reads a single supplied address without visiting it. Use it to understand visible structure, not to trace a journey. Candidate embedded HTTP(S) URLs in named query fields can be examined locally, but there is no redirect-chain lookup, real-flow reconstruction, or short-link expansion behind the result.
Separate the outer address from a named destination field
Begin by identifying the complete outer URL. In the invented text https://gateway.example/continue?next=https%3A%2F%2Fshop.example%2Foffer, the supplied address belongs to gateway.example. The value associated with next contains a possible shop.example URL after one decoding step. These are two separate observations. Calling the second one the final destination would add a claim that the text cannot establish. The outer application might use that value, reject it, ignore it, or apply conditions that are not written in the address. Keep those possibilities open until there is evidence from an authorized process outside this inspector.
Field names are hints rather than instructions the inspector executes. A name such as next, target, or url can suggest a destination, but a service may use a different name or attach a different meaning to a familiar one. The tool examines candidates in named query fields; it does not promise to uncover every address-like string hidden in arbitrary data. If no candidate is reported, that does not establish that navigation is direct. The application could keep its destination in server-side state, a script, a cookie, or a lookup table that the supplied text does not contain.
State the immediate question before inspecting. You may want to know whether an email wrapper contains an expected page address, whether a query value appears truncated, or whether the outer host differs from the one described in a message. Each question can be answered more carefully than “where does this go?” A useful note identifies the outer hostname and the exact field being discussed, with private values removed. It avoids drawing arrows between addresses unless those arrows are explicitly labeled as relationships in the supplied text rather than observed movements by a browser.
Read one query layer without merging separate values
Paste the complete HTTP(S) address and select Inspect link. Load example lets you practice with public text, and Clear empties the current inspection. The initial result shows host information and findings while keeping private details hidden. Reveal details toggles the normalized address, path, ordered raw and once-decoded query pairs, and fragment. Use the raw and readable views together when assessing an embedded candidate. The readable value helps explain what a field contains; the raw value shows how that content was packaged inside the outer address. Neither view is a visit to the candidate host.
Consider a candidate with its own query, such as https://shop.example/offer?item=7&view=wide. When placed inside an outer field, the inner delimiters need suitable encoding so they remain part of that value. If the outer query instead contains next=https://shop.example/offer?item=7&view=wide, the view field belongs to the outer query structure as written. That may be an authoring mistake, but the inspector cannot infer the intended repair. Ask for a newly issued complete link rather than manually moving fields across boundaries. A readable fragment of a destination is not proof that you recovered the original intended address.
Read every occurrence when a destination-like name is repeated. Two next fields do not prove two redirects, and their order does not establish which one a server would use. Also distinguish next= from a bare next key: the first assigns an empty value and the second has no equals sign. Percent decoding is performed once for display. Plus becomes space under the form-encoding convention, not under a universal server rule. Malformed encoding produces a finding while the raw text stays available. Do not keep decoding until a value resembles the destination you expected to find.
Recognize what an opaque short-link token cannot tell you
A short address such as https://go.example/r8K2 can expose a scheme, hostname, and path token without exposing any destination. The token might identify a record held elsewhere. Reading its letters, changing their case, or guessing that the token contains a date does not recover that record. The Link Inspector does not expand short links. It cannot supply a hidden final hostname, a hop count, or a redirect status when none of that evidence appears in the supplied text. A result with no embedded candidate is therefore an honest limit, not a failed promise to reveal a destination.
Do not treat length as a credibility signal. A short path can be used for an ordinary public campaign, and a long readable path can still describe an unexpected host or contain private access material. The inspector offers neither a safe score nor an unsafe verdict. It does not make a network request to see whether the short address exists. It also cannot report whether a mapping has expired, whether a service is available, or whether the destination changes. Those are questions about external state, while this inspection concerns only the text available at the time you paste it.
When a workflow requires a known destination, request the original full address from an established contact or the approved campaign record. You do not need to open an unknown short link merely to ask for a clearer reference. If the sender supplies a full URL, inspect that new text separately and compare it with the intended task. Do not describe the replacement as a verified expansion unless an authorized source actually established that relationship. A sender giving you another address is useful context, but the local tool still has no evidence that the short token maps to it. If the same token arrives with conflicting descriptions, preserve that discrepancy in the handoff instead of picking the description you prefer. Ask which approved source should control the task. Inspecting either piece of text cannot resolve a disagreement about a mapping held elsewhere.
Keep the outer URL separate
Read the candidate, not an imagined journey
Inspect the supplied hostname and reveal query details only when you are ready to examine possible embedded destinations.
Compare host boundaries without turning them into identity claims
For the supplied URL, the result presents ASCII and Unicode hostname forms, scheme, effective port, and the registrable-domain boundary calculated with the Public Suffix List. That gives you specific text to compare with an expected address. It does not prove the operator, brand relationship, or owner of either the outer host or an embedded candidate. Private PSL entries are included in the boundary calculation and are not ownership records. Keep a full hostname comparison alongside any shorter domain grouping, especially when the task concerns a particular subdomain rather than every name under a shared suffix.
A brand word in a path or query value does not change the outer host. In https://relay.example/known-brand/continue, known-brand is part of the path. Similarly, a destination-looking value after a question mark does not replace relay.example as the host of the supplied address. Avoid deciding based on the first familiar word you see. Read the fields according to their labels in the inspection. If an address uses userinfo before an at sign, that material is not the hostname either. Userinfo can also be sensitive, so do not reproduce it in a public explanation of the host distinction.
Treat scheme and port findings with the same discipline. An effective port describes how the parsed address specifies or defaults its port; it is not a report that a connection succeeded. The presence of HTTPS is not a certificate inspection. There are no TLS, DNS, status-code, reputation, breach, availability, or ownership requests here, and no API supplies a hidden assessment. A familiar registrable domain is not a substitute for those missing checks. Report the narrow finding you can support, such as an unexpected outer hostname, and leave the broader conclusion to the appropriate authorized review.
Document observations without inventing a redirect chain
Use language that makes the evidence level obvious. “The next field contains a candidate HTTPS URL” describes supplied text. “The link redirects to that URL” describes behavior and needs different evidence. “The link eventually reaches the campaign page” makes an even broader claim about a journey. This tool can support the first statement, not the other two. The distinction matters when handing an issue to an editor, developer, or support team: they need to know whether you found a value in a query or observed a live response through a separate process.
Several nested candidates still do not form a measured sequence. An outer query could contain a wrapper URL whose own text contains another candidate. Their nesting describes how strings are packaged, not how many requests a browser makes. Do not label them hop one, hop two, and final hop based only on that packaging. Likewise, a candidate that appears to point back to the outer host does not prove a redirect loop. A visible repeated address can be described as repetition in the text. Whether it causes repeated navigation depends on application behavior that has not been observed here.
A concise handoff can contain the expected host, the actual outer host, the relevant field name, and a sanitized version of the questionable structure. Include whether the concern is an empty field, a duplicated name, an apparent delimiter mistake, or an unknown token. Do not attach a full private URL just to make the note look complete. If you are editing campaign tags rather than investigating a destination claim, move that work to the UTM Campaign Link Builder with an approved public base address. Building labels does not establish how an existing wrapper behaves.
Keep private addresses within a deliberate inspection workflow
The input must start with explicit HTTP(S):// and fit all three limits: 8,192 code points, 32 KiB, and 200 query fields. Backslashes, controls, bidi control characters, and whitespace inside the address are rejected. Leading or trailing ASCII spaces are removed with a finding. These rules deliberately narrow what the panel accepts. Do not delete characters from a signed or private link just to force acceptance. If the source includes a wrapped line or a broken copy, obtain the complete original from its author. An edited approximation may no longer represent the link under discussion.
Private information can sit in userinfo, the path, query values, or the fragment, including inside an embedded candidate. Details start hidden, but the pasted input and anything you explicitly copy still require care. The inspector uses an opaque-origin sandbox, no-store responses, and connect-src none for local inspection. It does not fetch pasted URLs; ordinary WordPress page requests are separate. This boundary does not stop extensions or a hostile parent replacing the panel with a different interface. Avoid turning these limits into a promise of protection against every browser or device threat.
Inspected URLs are displayed as text, never active user-URL anchors. Use Copy hostname when the host alone answers the question, or Copy inspected URL when you intentionally need the complete inspected address. Make that copy before changing tabs: input and derived content are cleared when the page is hidden and on pagehide, pageshow, or freeze. Clear provides a direct reset, too. None of these actions erases clipboard contents or clipboard history. There is no saved history, project storage, PDF, download, or later recovery view, so finish the narrow review and handle any clipboard copy separately.
Questions about Redirect Parameters and Short Links
Can this tool reveal the final page behind any short URL?
No. It does not contact shortening services or follow responses. A short token can refer to a mapping that is absent from the address itself. Ask an established source for the original full URL when the task requires a known destination, and inspect that supplied text separately.
Does an embedded URL prove that a redirect will happen?
No. It is a candidate found in a named query field. The outer application may ignore it, replace it, or use it only under conditions not visible in the text. The inspector cannot turn that candidate into evidence of a redirect chain or an actual navigation flow.
Do two repeated destination fields represent two hops?
No. Repeated fields are ordered pieces of one supplied query string. They do not establish a sequence of network requests or tell you which value the receiving application chooses. Keep both occurrences visible in your review and ask the author to explain the intended structure.
Continue with another link-inspection guide
Inspect a supplied address in the Link Inspector or choose a related task below. Explore more practical utilities in all free tools.
Describe only the evidence you have
Review redirect-looking fields locally
Identify visible URL candidates and opaque tokens without opening them or treating them as a verified redirect chain.