DNS4EU Blocks Blog.fefe.de

koehr · 2025-12-21T16:13:59.000Z

I filed a request, maybe it is a mistake, but that it ended up on the block list is suspicious.

KomoD 147 days ago |

What is blog.fefe.de? Doesn't seem to have any content.

koehr 146 days ago | |

Historically, it was a rather famous page. It's a watchblog by the German security expert Felix Von Leitner. It exists since 2005, but since May this year, he didn't write anything until one new entry that you can see here: http://blog.fefe.de/?mon=202512

mschuster91 140 days ago | | |

He suffers from a stroke but is recovering.

koehr 147 days ago |

Looks like https://temp.sh/ is blocked as well.

kevin061 147 days ago |

I am using a blocklist from OISD and it is also blocked, I don't know if that is the reason.

koehr 147 days ago | |

Interesting, I just downloaded the big list and couldn't find it there.

Bender 147 days ago |

Have they replied yet? Could it be that one of the links to conspiracy sites had something that triggered a recursive block?

koehr 146 days ago | |

They replied in the meantime and removed the domain from their threat database.

Bender 146 days ago | | |

Groovy. Hopefully they put a safeguard in place to prevent that from occurring again.

immibis 147 days ago |

Did you write something about Israel on your blog? That could be why.

betaby 147 days ago |

NDS4EU should not be used. There is no reason for that.

kevin061 147 days ago | |

Why?

betaby 147 days ago | | |

Because it blocks domain. The opposite of what a resolver should do. It's a second time in ~2 months DNS4EU is reported on HN of not resolving domains.

KomoD 147 days ago | | |

It blocks domains if you choose a resolver that specifically offers it as a service.

Protective 86.54.11.1

Protective + Child Protection 86.54.11.12

Protective + Ad Blocking 86.54.11.13

Protective + Child Protection + Ad Blocking 86.54.11.11

They have unfiltered resolver that works fine. 86.54.11.100