Practical tools for system, network, security, and operations administrators.

SEC-C0063 · Threat Intelligence & IOC Analysis

How to Check if a File, URL or Domain Is Malicious

Check a file, URL, or domain you were sent. These tools do not decide that it is safe, and they do not fetch the URL.

Updated 25 October 2026 · How-To

This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.

What this hour is for

The hash page computes SHA-256 locally and says it does not query a reputation service. Open a lookup you trust yourself. The URL page does not request the URL. The domain page reads public DNS for example.com or the name you type. Age and blocklists are not included. A DNS answer is not a verdict.

You do not download the file, open the URL, or scan a network. You do not paste a secret.

192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. A sample password is replaced. It is not a password you keep.

The change you can finish

Apply nothing while you are writing the note. When the lab window opens, it is one change on the system named in the ticket. Read the draft, then the system, then decide.

Rollback is the file, the record, or the snapshot you saved first. You do not invent a rollback after the only copy is gone.

  1. Hold the hash, the URL text, or the domain.
  2. Read what the tool actually checked.
  3. Write that it is not a verdict.
  4. Do not open it.
  5. Stop.

Mistakes that outlive the statement

How to Check if a File, URL or Domain Is Malicious goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.

Decisions to write down

One decision for How to Check if a File, URL or Domain Is Malicious: Nothing was opened. The limit of the tool is written. And the object is one you were sent.

Checks before you call it done

Confirm this before you call the change done: The object is written. The tool's limit is written. Nothing was opened. Nothing was downloaded. And no network was scanned. If one of those fails, stop.

# Not a verdict. Do not open the URL. Do not download the file.
# 192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. A sample password is replaced. It is not a password you keep.

Before you leave the system

How to Check if a File, URL or Domain Is Malicious ends when the system in the note is the system in the ticket. If it is not, stop.

The draft stays a draft until a person has read the names in it. A generator does not log in, does not scan, and does not send mail.

192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you publish because a draft included them.

prompt-for-this is a reminder that a secret is missing. It is not a password, a key, or a token you save. A sample password is replaced. It is not a password you keep.

One change is the window. If two things move and the result is wrong, you will not know which one did it.

If the same step fails twice, stop for the day. Restore the copy you took first.

A second person reads the scope aloud. If they cannot find it in the ticket, the note is not done.

This page is a planning guide. It is not legal advice, not an audit opinion, not a vendor manual, and not the text of a standard. You do not disable a security control to make a check pass. You do not use the page against a system you do not administer.

Tools for this guide

These tools run in the browser on this site. They do not log into your machines.

More in this cluster

The pillar for this page, and the next published pages filed with it.