[bswinnerton]

> Having a simple paragraph about RIPE, BGP and ARIN would be helpful (at least for me).

That's a great idea. I'll add a tooltip over some of the less obvious fields describing what they are.

> Is there any way at all to do this for IPv6?

Indeed! It's supported natively, so if you have an IPv6 address you should see it automatically. Here's an example <https://ip.guide/2600::>

> If the IP is associated with hostnames that would be nice to know.

I dig that idea, I'll have to think of the best way to pull that data while keeping the app stateless and fast.

[baby_souffle]

> I dig that idea, I'll have to think of the best way to pull that data while keeping the app stateless and fast.

Reverse DNS lookups are usually pretty quick:

```shell

  > time dig +short -x 2600:dead::beef
  customer.my-isp.net.
  dig +short -x 2600:dead::beef  0.00s user 0.01s system 1% cpu 0.882 total

```

[teh_klev]

This might be useful to review:

https://news.ycombinator.com/formatdoc

"Text after a blank line that is indented by two or more spaces is reproduced verbatim. (This is intended for code.)"

[baby_souffle]

Thanks.

I spend all day writing markdown and fenced blocks with type-hint is muscle memory at this point

[spacehunt]

Reverse DNS does not give you all the hostnames that can point to a particular IP address though.

[necovek]

Other than brute forcing, I don't think anything does — that's the beauty and the curse of a proper federated system :)

[jedberg]

In fact, it might not even give you any names that point to an IP address, since it might be out of sync with the forward system, especially if the records are built by hand.