It looks like they have code waiting for a different endpoint for fetching service status, but instead of just disabling it when not using it, they changed the queried endpoint to example.com and still execute it.

loadFutureServiceStatus.ts

export const FUTURE_SERVICE_STATUS_ENDPOINT = 'https://example.com';

....later on...

const serviceStatusFuture: SoapServiceStatus = await fetch(

    FUTURE_SERVICE_STATUS_ENDPOINT,...

Given how unusable the site is in Safari and Firefox on macOS, probably because it was written by someone who should not have been tasked with writing it. :\

I noticed that too, probably just something like a copy-pasted 'how to make a request with this framework' left in accidentally.