They don't typically provide them to the public, or small operators. You'd have to be a large provider to get access to a direct feed.

NANOG

Completely unaware of NANOG, thank you!

https://ipapi.is/ip-to-company.html

Wow, that's exactly what we've built, basically. The problem is finding a reliable source of what CIDR ranges they provide our region without storing and guessing ourselves to make sure it's local. We go through a lot of ARIN data each week to make sure one neighbor isn't banning another because he can't remember his password.

Our next step was refactoring with geo-location, but I figured there has to be feeds from these providers like StarLink does .... oy.

You could ask the NANOG mailing list if any of them track it. I use to that going through unofficial channels like NOGs to get help when getting this kind of odd info.

Something like this? https://ipapi.is/ip-to-company.html

That's why I stick with contoso and fabrikam.

example.net and example.org

.onion or arpa are good ones.

https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml

Apart from example.com are their any documentation only domains?

Credit cards have test numbers, IP addresses have TEST-NET1,2,and 3 for ipv4 and 2001:db8:: for V6.

I guess this is a question of scale, ultimately.

Good point with raising, though

k8s will be a given when your containerizations grow beyond whatever devops git magic you're doing. I would reconsider that, and throw in something like argocd. The rest is just standard.

Without knowing more about your use case, seems fine I guess.

I see you are throwing security out the window by not running rootless containers via podman so when your application gets popped the attackers will have root access.

We're not a FANG company; we should just do what everybody does and call it a day.

But everyone else is trying to be fang so you still need your hyperconverged infrastructure and geo redundant clusters.

Debian is good, but the point of containers is to deal with applications and hosts like cattle not pets so your underlying OS doesn't matter. With Debian specifically you are several major versions behind current releases so you are missing performance gains if you don't add extra repos, with that said Debian will backport security patches.

I wish it would just die already.

I was just surprised to see anyone doing mail in 2026!

Just not vendor locked. Our stack is quite modern.

Is.. is that a time traveller?

Thanks!

Good idea, noted. I will look into this.

Any way you could add propagation insights? I've had some customers with crumby resellers whose DNS propagation consistently failed on a handful of large servers. This would be the last feature I need to make this my all-in-one tool

Noted, thank you!

dmarc is missing the description for reporting and compliance.

Otherwise looks nice

Thanks, of course I know alternativeto. Maybe it isn't clear enough in my post, but what I really want is to read about first-hand experiences with such tools: how easy or difficult is the setup really? Do you really host it yourself or use a VPS and why? What are some potential gotchas? And so on.

Payment processor, or marketplace?

Payment processing is a lot of work with compliance. That’s one reason that it’s centralized.