Show HN: Browse Internet Infrastructure

Those are really useful suggestions, thanks!

> 1) Include a link to dnsviz.net to check on the DNSSEC status of domains.

I use DNSViz all the time. They've done a great job of displaying the entire trail and helping debug DNSSEC issues. But it's a bit too detailed for my liking. I'm thinking about how I would add this to Wirewiki. What to show and hide by default, how to format it, etc. Adding something similar is pretty high on my list for Wirewiki.

> 2) Shared fate [...]

I do already show ASNs for A/AAAA records, but adding those to NS and MX addresses as well would be useful. I'm a bit hesitant to add more data to the overview, but a separate page that shows an analysis of shared name server resources could be useful indeed. I've added it to the list.

> 3) displaying whether a domain exists on popular block lists would be awesome.

Absolutely. Already on the list :)

> You could spend the rest of your life building this and never actually completing it, be careful!

Haha, I've already spent 5 years, and I don't mind to keep going as long as it's interesting and sustainable!

Nice website, but I feel like calling it "wire wiki" is quite ambitious. Currently, it's a (beautiful) DNS lookup tool, but that's about it. I expected something like RIPE Stat [0], or something like the undersea cable map [1] (based on the "wire" in the name). Also, if you're doing DNS, take a look at resolve.rs [2], they have some nice DNS tools, though not as pretty as yours :)

And since you mentioned scanning the IPv4 address space for DNS servers - I did that as well at a some point for a product I've built (and even have a patent on). The list of servers you're going to get with a naive scanning approach is not what you want. It won't include the servers you probably want (such as the customer-facing DNS servers of ISPs) and will include an insane amount of junk like home routers or weird IoT devices that expose their port 53. Hit me up via the email in my profile if you want to chat.

[0]: https://stat.ripe.net/

[1]: https://www.submarinecablemap.com/

[2]: https://resolve.rs/

Nicely done. I poke at DNS a bit over at StackFox (https://stackfox.co/site/wirewiki.com), and anyone who’s spent time looking at DNS knows how much work goes into this.

A couple thoughts:

1) Nameserver “redundancy” that isn’t. All the ns1/ns2 setups that collapse onto the same provider or ASN once you follow the trail.

2) Authoritative drift. One server quietly serving an older serial or odd TTL for a while — invisible until something breaks. With global data, quirks like that become obvious.

Anyway, inspiring job. Wirewiki already feels like something that should have existed but somehow didn’t.

You're right that it doesn't do the name Wirewiki justice yet. I've got so many things planned to add at some point, much more than just DNS. Check again in 2 years' time ;)

> The list of servers you're going to get with a naive scanning approach is not what you want.

Absolutely right. I'm doing uptime monitoring and a handful of checks (udp/tcp, nxdomain, dnssec, dns filtering) before listing them, but I feel like it could definitely be improved. Would love to talk! I'll send you an email.

It’s a wiki (loosely defined as an authoritative browsable graph / index) of everything that goes over the wire.