A web tool that checks and displays the online/offline status of public IPFS gateways with security warnings.
IPFS Public Gateway Checker is a web-based tool that monitors and displays the real-time online/offline status of public IPFS gateways. It helps users and developers quickly identify which gateways are available for accessing IPFS content and provides important security warnings about gateway configurations. The tool is community-maintained and includes both regular and Tor onion gateways.
IPFS users, developers, and administrators who need to access or share content via public IPFS gateways and want to ensure gateway availability and security.
It offers a centralized view of gateway health with critical security annotations, helping users avoid insecure gateways and promoting safer practices in the decentralized web ecosystem.
Checks which public gateways are online or not
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Continuously checks and displays online/offline status of public IPFS gateways, enabling quick identification of available options via the GitHub Pages site.
Highlights gateways lacking origin isolation with ⚠️ symbols, warning about shared localStorage and cookie risks based on documented security issues.
Promotes and identifies subdomain gateways for improved security, encouraging safer configurations as per IPFS documentation.
Includes a separate list of .onion gateways accessible via Tor Browser, catering to privacy-focused users without extra setup.
Provides clear instructions for running the checker locally with npm, aiding development and testing without external dependencies.
The list is community-maintained with no central authority, leading to potential inconsistencies or delays compared to IPFS Foundation's official gateways.
It's a static web interface without an API, making it unsuitable for integrating gateway checks into automated workflows or monitoring systems.
Only monitors status and provides warnings; it doesn't mitigate risks, requiring users to self-host for critical apps like wallets as advised in the README.
Local testing with Tor Browser requires manual configuration changes in about:config (e.g., proxy settings), which is error-prone and must be reset after use.