Security · 58 tools · nothing uploads

Defang / Fang IP

Defang / Fang IP. Defang turns a live indicator into inert text (won't render as a link); fang reverses it. Pure text substitution, on your device.

Input

Options

live

Defang / Fang IP wraps every period in square brackets and treats every colon the same way, so 8.8.8.8 comes back as 8[.]8[.]8[.]8. An IPv6 address goes through the identical pass, and mode fang undoes both. Give it a URL and the scheme colon is bracketed too, which nobody writes.

Questions

How does it defang an address?

It replaces every period with [.] and every colon with [:], which covers IPv4 and IPv6 in one pass. So 8.8.8.8 becomes 8[.]8[.]8[.]8 and 2001:db8::1 becomes 2001[:]db8[:][:]1, neither of which will be picked up as a live address by tools that linkify text.

How do I undo it?

Set mode to fang. Every [.] becomes a period again and every [:] becomes a colon. That is useful for turning an indicator out of a report back into something you can paste into the CIDR calculator or the IOC extractor.

Does it change my whole file?

Yes. Both directions are plain text substitution over the entire input, not a scan for address shaped text. Every period and colon anywhere in the file is affected, timestamps and ordinary sentences included, so give it the indicator list rather than the surrounding narrative if you want a readable result.

Should I use this on a URL?

Use Defang / Fang URL instead. That one rewrites the scheme to hxxp and the :// to [://], which is the convention people expect. Running the IP defanger on a URL turns the scheme colon into [:] and produces something no one else writes.

Does anything get uploaded?

No. It is a text substitution running in a Web Worker in this tab, and the file is never transmitted anywhere. Drop several files and each comes back as its own result. Since indicator lists usually come out of an incident, doing this locally keeps the incident local too.

Compare

ToolRuns on the CLILive as you type
Defang / Fang IPYesYes
IOC extractorYesYes
Defang / Fang URLYesYes
JA3 / JA3S fingerprintYesNo
HASSH fingerprint (SSH)YesNo

Related Security tools

n→nIOC extractorPull URLs, IPs, domains, emails, hashes, MAC addresses, file paths and dates out of text in one pass, understanding defanged forms (hxxp, [.]/(.)/{.}, [://], [:], [@]) as well as live ones. Regex-based pattern matching, not a validator: a matched hash might be any 64 hex characters, not necessarily a real SHA-256 of anything, and "domain" filters out a small blocklist of common file extensions (.php/.exe/.sh/...) rather than knowing real TLDs. Categories can overlap by design (a domain inside a matched URL is listed under both).Runs on each file you dropn→nDefang / Fang URLDefang / Fang URL. Defang turns a live indicator into inert text (won't render as a link); fang reverses it. Pure text substitution.Runs on each file you dropn→nJA3 / JA3S fingerprintCompute the JA3 (ClientHello) or JA3S (ServerHello) TLS fingerprint from a raw captured TLS record. JA4 is not implemented. See the tool source for why. A matching fingerprint means two handshakes look alike, not that either endpoint is safe or malicious.Runs on each file you dropn→nHASSH fingerprint (SSH)Compute the HASSH fingerprint from a raw SSH KEXINIT packet. Best-effort recollection of the published field composition (kex;encryption_c2s;mac_c2s;compression_c2s, MD5), NOT checked against the reference hassh tool's output (no network access to verify). The KEXINIT wire parsing itself is plain RFC 4253. A matching fingerprint means two handshakes announced the same algorithms, nothing about trust.Runs on each file you drop