demarcush
demarcush
Can be closed with: https://github.com/738/awesome-url-shortener/pull/29
can be closed with: https://github.com/738/awesome-url-shortener/pull/29
Can be closed with: https://github.com/738/awesome-url-shortener/pull/29
> I think that `git.io` is deprecated and can be removed. It is indeed, and it's only added to the "deprecated" list.
When using caddy as a reverse proxy for something like [dns-over-https](https://github.com/m13253/dns-over-https), having support for h3 makes software like `dnscrypt-proxy` and others do a DNS-over-HTTP/3 query.
Govts and ISP's infrastructure is heavily built upon the usage of email. Doing so would really be a shot in their own legs. [Delta Chat](https://delta.chat/en/) was built considering this. As...
@emranovin: You already can in two ways (that can be combined): Either use the [HOSTS](https://github.com/MasterKia/PersianBlocker/blob/main/PersianBlockerHosts.txt) file and append it your server's `/etc/hosts` and configure your server (v2ray-core, xray-core, clash, etc.)...
can be closed with https://github.com/738/awesome-url-shortener/pull/29
Does the current workflow tests if the stamp is advertising the resolver as DNSSEC-enabled but we couldn't get the response for `example.com` with `DNSSEC signed : yes`?
@c3d1c06c-bf26-477e-b0eb-c50ef4477ba6 > How to get the correct result? Manually I'd use this to verify resolver's functionality ``` $ dnslookup go.dnscheck.tools [stamp] ``` and ``` $ dnslookup badsig.go.dnscheck.tools [stamp] ``` to...