It would replace the Cloudflare to server network hop with a cloudflare PoP to R2 hop. That covers approximately the same geographical distance and results in similar latency.
(I'm the author btw)
1,187 karma · joined October 14, 2016
[ my public key: https://keybase.io/ruurtjan; my proof: https://keybase.io/ruurtjan/sigs/xboZ7fzACzFSzPjfaAEW3S4efJbiL2jkwdIcf1P-bOU ]
(I'm the author btw)
I think most people search for domains they own, which doesn't correlate with Tranco popularity ranking. Treating 'popularity' not as a function of visitors, but as a function of number of known domain names with that prefix could work, though.
Yes, it will autocomplete the most popular domains first, then known registered domains, and then fall back to appending popular TLDs.
The reason is that it's impossible to enumerate all domains. gTLDs (like .com, .info) mostly publish their zone files, but ccTLDs (like .cn, .de) usually don't.
But maybe you're right. After reading these comments, it's clearly confusing to people.
Ruurtjan here, founder of Wirewiki.com. I recently tried to get autocomplete as fast as I could. I'll be checking in here the rest of the day to answer any questions.
Also happy to hear any suggestions for Wirewiki.
A browsable map of internet infrastructure. Not just a collection of lookup tools, but it also interlinks results, so you can navigate linked assets as well. Think: DNS lookup -> SPF record -> mail provider's SPF record -> IP address details.
A browsable map of internet infrastructure.
Currently, it only hosts DNS-related data and tools, but I'm looking to add ASN, IP, registrar, CDN and hosting provider data.
The main thing I bring to the table with Wirewiki is UX, and I don't feel like I could do that well in a CLI.
> 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.
> Authoritative drift.
This is why I query all authoritative name servers (as well as delegating name servers when querying NS records) in the DNS propagation tool. I haven't seen any other site do this. This feels like such an obvious thing to me, but somehow I'm the only one.
Internet infrastructure data is inherently open. I'm just presenting it in a more useful way. So any motivated actor can access it regradless.
In any case, exposing your IP during these lookups is bad operational security for them. So I would assume they'd prefer not to use Wirewiki.
All that to say: I don't feel conflicted about making these tools.
> 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!
I like the idea of evolution (diversity + selection) applied here. Many people building it differently and letting the market decide what's most useful.
My take on this space is making it a browsable graph instead of 'just' a collection of lookup tools. The internet _is_ a graph, and it often makes sense to inspect linked resources (Domain name -> name server -> IP address, for example).
As for the longer-term vision, I'd like to make this graph as complete as possible. It now only has DNS-related tools, but adding ASNs, BGP data, hosting providers, etc. would make the existing tools more useful with every addition.
Depends on how you prefer to learn, but here are a few suggestions.
I've heard good things about the Computer Networks book by Tanenbaum and Wetherall, but I haven't read it myself. Very broad and comprehensive. The most hardcore way would be to make reading RFCs your hobby. It can be tough to get through, but if you regularly take half an hour to do it, you'll learn so much. I've recently started a course at https://classes.pracnet.net/, which is good too.
Then run a program that listens to UDP/53 and TCP/53. Have it respond with a DNS packet that's only dynamic in the LOC record and message ID. Not fully compliant with the DNS spec, but good enough for this use case.
You could cache API response to combat rate limiting.
Beta is open at https://beta.nslookup.io (registration wall for now, but I'll remove it at launch).
I also have two accounts btw. Didn't raise any flags. But their ad platform is buggy, so it might just be a coincidence.
I don't recall onboarding being an issue for me. What are they telling you?
I'm checking in the next couple of days, so feel free to ask me anything if you're thinking about setting up X ads yourself :)
See https://www.nslookup.io/learning/dmarc-a-practical-guide/
Here they are for the example OP gave: https://www.nslookup.io/domains/stripe.com/dns-records/
Looks like I need to rerun the script and add some logos (: