Some sites not detected as verified

techmagus

Hi,

I have a couple of questions regarding some identities, even though I have the correct information entered, are not being detected as verified.

The most important one is my domain: youronly.one. It used to work, but I noticed a few days ago that it's no longer being detected. I don't recall changing anything DNS-side, and just to test, I used the same fingerprint for the subdomain im.youronly.one and it works fine.

Here's my keyoxide: https://keyoxide.org/wkd/contact@im.youronly.one

For the second one, there are Discourse sites that are not getting verified even though the profile section is viewable publicly. For example: https://twittercommunity.com/u/techmagus ; https://community.cloudflare.com/u/youronlyone ; and https://forum.gitlab.com/u/techmagus but my Discourse profile for Hugo works fine.

I also tried the [openpgp] format before (I only switched to custom domain format a few days ago) but same thing, having problems with some Discourse forums even though the profile and description are showing publicly.

Lastly, for the Hashi instance of Misskey (fediverse/activitypub software), for some reason it is not getting detected either. I added the URL in my bio, as well as, in a pinned post (both also added as a notation separately).

Is there something causing these 3 cases to fail? And in the DNS issue, it's probably something I can fix on my end? I'm just not sure what's happening during detection to know what to fix. For the others, is it correct to assume that it has to do with their respective servers?

Thank you very much.

~ c.im/@youronlyone | hashi.icu/@youronlyone

yarmo

Hi,

techmagus The most important one is my domain: youronly.one. It used to work, but I noticed a few days ago that it's no longer being detected. I don't recall changing anything DNS-side, and just to test, I used the same fingerprint for the subdomain im.youronly.one and it works fine.

DNS proofs seem to fluctuate for some. Right now, both your DNS proofs work.

techmagus For the second one, there are Discourse sites that are not getting verified even though the profile section is viewable publicly. For example: https://twittercommunity.com/u/techmagus ; https://community.cloudflare.com/u/youronlyone ; and https://forum.gitlab.com/u/techmagus but my Discourse profile for Hugo works fine.

I checked your links and all of them give me a 403 Forbidden when requesting through doip.js, directly in the browser the links work fine. My guess is they are using Cloudflare (confirmed for community.cloudflare.com, not the other two) or something similar and they are rejecting the doip requests. Not sure how to solve Cloudflare blocking my requests.

techmagus Lastly, for the Hashi instance of Misskey (fediverse/activitypub software), for some reason it is not getting detected either. I added the URL in my bio, as well as, in a pinned post (both also added as a notation separately).

This is still a strange issue. Your claim+proof works fine when I run it on my machine's doip.js, but the server's doip.js receives an error message from hashi.icu. I have encountered this before and it usually was caused by some form of rate limiting or blocking by the target server. In this case, Cloudflare is once again the issue blocking the requests :/

In any case, you did the claim+proof correctly, no need to change it.

Still unsure how to deal with Cloudflare. If hashi.icu had CORS headers, it wouldn't be a problem, your browser does the verification and done. Since CORS headers are missing, the proxy needs to do the request and it gets blocked by Cloudflare...

yarmo

Did some testing with FlareSolverr and this fixes (at least some of) your issues! I will try and add support for FlareSolverr as soon as possible in the proxy server, I'll give an update here when it's ready