Disavow File Generator.

How to Disavow an Entire IP Address

Sometimes the harmful backlinks pointing to your site don't come from a normal domain name at all — they link straight from a bare IP address, like http://65.2.75.120/some-spam-page. This is common with scraper sites, cloned "siterip" pages, and auto-generated spam hosted directly on a server IP with no domain attached.

The good news: you don't need to list every single spammy URL from that IP one by one. Because the links use the IP itself as the host, the IP behaves exactly like a domain in the disavow file. A single domain: line covers every path on it — including any new ones that appear later.

Format:

# Spam links from IP host 65.2.75.120
domain:65.2.75.120

That one line disavows http://65.2.75.120/page-1, http://65.2.75.120/another-spam-url, and everything else served from that IP.

Important scope note: Disavowing an IP only affects links that actually point via that IP in the href. It does not expand to other domains that happen to be hosted on the same server IP.

https://x.com/methode/status/649613635191480320

This is intentional on Google's part — shared hosting means thousands of unrelated sites can sit on one IP, so Google deliberately keeps the disavow narrow. For your purposes this is exactly what you want: if the spam links use the bare IP, this line catches them cleanly without touching anything else.

A few things to keep in mind:

• These IP links are almost always http://, not https://. If your site is set up as separate URL-prefix properties in Search Console (http vs https), the disavow list applies per property. A Domain property avoids this by covering both at once.
• The links will keep showing in your Links report even after processing — disavow suppresses the ranking signal, it doesn't delete the link.
• A handful of junk links from a single scraper IP is usually something Google already ignores on its own, so treat this as low-risk housekeeping rather than an emergency fix.