We’re doing the SEO for a local Central Oregon business. They’re great clients. We built them a custom WordPress site, with an integrated blog and all the fancy bells and whistles. In their monthly analytics reporting last month, I noticed a substantial traffic drop from the month prior so I looked further to see if there were any issues I could address. I found their domain’s ISP had been blacklisted by two DNSBLs (Domain Name System Blacklists are spam blocking lists that allow administrators to block messages from specific systems that have a history of sending spam). Yikes. Here’s the lowdown, and why you want to avoid it from happening to you.Why Not to Use Your Local Host: Intro to ISP blacklisting

Why Not to Use Your Local Host: Intro to ISP blacklisting
When we setup the hosting for Company M, we’ll call them, they insisted (well, their IT guys did) that their records be pointed back to our small Central Oregon internet service provider (ISP). We’ll call them, Local Dog. We advised against this several times. As of today, at least one of Local Dog’s servers affecting the whole IP range is blacklisted by two DNSBLs. It’s been 3 weeks since we found it, and Local Dog hasn’t gotten themselves de-blacklisted. My hunch is they’re unaware that they’re even on one. Therein lies the problem.

Are they so small that they don’t have the measures in place to realize their servers have been blacklisted and their customers are affected? Will they ever notice? Do they have enough clout to get themselves removed if and when they figure it out?

Read More: https://www.webberboss.com/why-not-to-use-your-local-host-intro-to-isp-blacklisting/