How to read URL before logging in

The address can be long, but you don't have to understand every parameter to detect a failure to meet the expected service. The first step is to read the full host. Examples below use domains for demonstrations.

Separate host from other parts

W https://konto.example.net/profil?tryb=demo#ustawienia protocol is HTTPS, host to konto.example.net, and later parts describe the path, parameters and passage. A familiar name in the path does not change the host.

W https://bank.example@logowanie.example.net/ The host is logowanie.example.net. Some before @ do not assume that the first word after https:// indicates the owner of the website.

Compare Full Name

Address bank.example.net.oszust.example.org is not a subdome example.net. Ends with another domain. Also a typo or similar character can lead to another place.

Do not attempt to determine the owner of each domain by mechanical cutting off the last two drones. There are multi-member endings as well as shared domain services. The simplest test is a comparison with an address saved previously or found independently.

Notice the transformations

The browser parser can normalize address recording. Names with some international characters can be presented as punycode with a member xn--Such a record does not in itself mean fraud. It requires careful checking of the name.

URL Inspector shows the host read by the parser without visiting the page. It does not solve shortened links and does not check where the page later redirects.

HTTPS does not support fairness

HTTPS is used to protect the connection to a given page. The cheater can also use it. The correct address does not protect from the intercepted page or unfair request in the message.

If the message concerns a payment or account problem, open the known application yourself. Do not log in just because the address reading did not show unusual items.