I'm asking because it seems to run an old njump version?

I think it's some reverse proxy routing magic that detects if the path is a "/nevent", "/npub" etc and uses the njump server, otherwise uses the landing page. It could be changed to detect email-like or domain-like URL paths too, and "/p/..." and "/e/..." paths that njump supports. Or njump.to could do that work and not redirect to nostr.com when the path is a NIP-05.

Yes that's us. Thanks for spot. We will have a look today, fix the proxying

I think we only use /whatever for njump on the site. So we could just pass all those and let njump handle? We do also have that caching issue again, seems like it slowed.