[ANDROID] ambigious verification state for https proof

As you can see on my keybase page, my https proof is alive:
https://keybase.io/sebbe_eu

However, the android client shows the https proof as failed.

Is the Android client checking the https proof locally? (Because the server isn't reachable on its public IP adress from inside the network, inside the network it must be accessed using 192.168.x.x address).

Scanned on a couple of pages and bizarrely it shows my certificate as invalid/revoked and I checked with StartCom and it isn't revoked.... In some browsers it come up as invalid and in some browsers it come up as valid.
Its super strange - the certificate was valid when I bought it and theres no revocation at OCSP/CRL.

Start with the Android client's HTTPS proof verification entry point and compare its behavior with the proof at https://keybase.io/sebbe_eu, including access from inside a network using a 192.168.x.x address. Check how certificate validity and revocation are evaluated through OCSP/CRL; done means the client reports the proof and certificate state consistently with the reachable server and certificate checks.