#Fediverse
I checked 4160 fediverse instances for their connectivity.

- A / AAAA record persent
- Reachabliltiy over #IPv6 if AAAA present.

107 Instances announce AAAA records but have broken inbound IPv6

1909 are #LegacyIP #IPv4only

2141 are #DualStack and have working inbound #IPv6

Way to go.

@goetz great idea !
Will you share that list somehow ?
Also did you think to look at the assets servers too?
(Like pictures and videos of mastodon instance ) since some may use some S3 service without IPv6 support 🥴

@benjamin I got the list from fedidb.com.

No, so far I only checked the server domain.
But I want to further analyse with webres6.dev.sap

The tricky part is outbound IPv6.

@goetz @benjamin @internet_nl also checks for IPv6 support, and provides tooling for testing multiple domains: https://en.internet.nl/faqs/batch-and-dashboard/
Batch API and web-based dashboard

Test for modern Internet Standards IPv6, DNSSEC, HTTPS, HSTS, DMARC, DKIM, SPF, STARTTLS, DANE, RPKI and security.txt

@rickvanrooijen @goetz @benjamin @internet_nl

Interesting thread! Note that the Internet.nl test is only checking inbound and not ountbound IPv6 support. Outbound support indeed can have its own issues. For example mastodon.social does support inbound IPv6 but not outbound due to a limitiation of the Kubernetes management software that they use. See : https://mastodon.social/@rickvanrooijen/116024625573654978

Let's keep testing and asking for improvement :)

@bartknubben @rickvanrooijen @benjamin @internet_nl

Not only Mastodon.social, also Wordpress (software) is limited in this regard.
The ActivityPub Plugin, which enables Federation support, only works with IPv4 enabled ActivityPub receipents. Due to the fact that core functionality of Wordpress is currently limited/developed with IPv4 focus.