Check known FDSN web services. This uses the FDSN Registry, so only services registered there will be tested. The previous version of this system that used a manually maintained list is available here, but will not be updated: http://www.seis.sc.edu/fdsnServiceCheck.old/serviceCheck.html.
FDSN web service specification.
This runs tests against FDSN web serices from within the browser. This means that we are making fetch requests in the browser itself via javascript that is loaded from our web server to the web server hosting the web service. If that server is not configured to allow queries from pages loaded from other sites, the request will fail. This is true even if the URL is accessible and working when directly entered into the browser. We believe that FDSN web services should in general be available in this manner. See the Wikipedia article and Mozilla and W3C for more information.
Be aware that IF this page is loaded via HTTPS, then all requests to the FDSN web services will also be via HTTPS as the browser will prevent an HTTPS loaded web page from attempting insecure HTTP queries. But if the web server under test only supports HTTP, then all tests will fail after a somewhat lengthy timeout period. We would like to see all of these web services support both HTTP and HTTPS.
In the case of failures, it is often helpful to look at the javascript console as additional debugging information can appear there. In particular, CORS errors are logged to the console, but the javascript does not receive them. Tests stop on the first failure within each type. Green tests are passes, red tests are failure and yellow are just my opinion.
Warning, because the data the remote service has access to is not encoded in these test, there is a reasonable chance of false positives and false negatives. Different browsers can also give different results, so it is worth checking multiple browsers and operating systems. These tests also represent my reading of the FDSN Web Service Specification, and hence reflect my biases. And there is always the chance of bugs in the javascript that runs the tests. Comments are welcome, you can email me (Philip Crotwell) at crotwell at seis.sc.edu.
Source code is at GitHub and uses seisplotjs
Click RUN to run tests on a data center, results will appear below. You can also run a single test against multiple data centers.
...loading known data centers.
Javascript must be enabled to view the results.