How the safety check works
Paste an HTTP or HTTPS address to inspect its structure locally. The checker separates the actual hostname from user-information, paths and query parameters, then explains local URL warning signals. It does not contact the destination or consult a reputation feed. Avoid pasting private session links; exports omit the original path, query, fragment and credentials.
What the result signals mean
A suspicious-looking URL deserves review, but a structural signal does not prove malicious intent. A normal-looking URL can still serve harmful content. The output lists evidence and unperformed checks separately, so a reviewer can decide what further evidence is needed.
Worked examples
example.com is a reserved example hostname with no local structural warning in the sample. In [email protected], the actual destination hostname is untrusted.example. The text before @ does not turn it into a bank website. Neither example is a live threat or a promise of safety.
Next steps and FAQ
Find the organisation’s official address independently, compare hostnames, and respect browser warnings. Does HTTPS prove legitimacy? No. Does this checker inspect page content or certificates? No. Can an unflagged result approve a payment or login? No; verify the transaction through an independent channel.