---
title: Blacklist monitors check IPv6 addresses
description: A blacklist monitor on an IPv6 address failed with "IPv4 only", and one on a host name with IPv6 often failed the same way. Monitors now check IPv6 addresses…
canonical: https://watchfor.io/changelog/2026-11-17-blacklist-ipv6
---

[All updates](/changelog/page/3#2026-11-17-blacklist-ipv6) ⚡ Improved Email IPv6 Nov 17, 2026 · v 12.3.4

# Blacklist monitors check IPv6 addresses

A blacklist monitor on an IPv6 address failed with "IPv4 only", and one on a host name with IPv6 often failed the same way. Monitors now check IPv6 addresses on the lists that publish IPv6 data (Spamhaus ZEN), and a host name is checked on its IPv4 and IPv6 addresses. Lists that publish IPv4 data only, such as SpamCop and Barracuda, show N/A for an IPv6 address instead of an error. The free Blacklist Checker works the same way.

## What changed

- IPv6 targets. An IPv6 address is looked up in the reversed-nibble form of RFC 5782.

- Host names. Up to two IPv4 and two IPv6 addresses are checked. The monitor counts as listed if any of them is, and the providers table shows which address a list flagged.

- Lists without IPv6 data. SpamCop, Barracuda and any list we don't know to publish IPv6 data show N/A for an IPv6 address. That's neither clean nor a failed lookup, so it never opens an incident.

## IPv6 checks from a location without IPv6

One of our locations has no IPv6 connectivity. An IPv6 check that runs there now goes over IPv4 instead of failing with "network is unreachable". The check's result says Checked over IPv4 — this location has no IPv6 , and the error of a failed check ends with the same note. For a strict IPv6 check, pick dual-stack locations.

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-11-17-blacklist-ipv6 · Site guide: https://watchfor.io/llms.txt
