keybase / keybase/keybase-issues
HTTPS proof on Encrypted DNSSEC services as CloudFlare hosted domains.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Hello Keybase Team.
recently we tried to add the website proof on Keybase, but we got error on proxied DNS websites.
you can check that here: [https://keybase.io/aryaztech](https://keybase.io/aryaztech) and we got [https!](https://keybase.io/aryaztech#_) error.
we tired to deactivate the DNS proxy and under attack services, and it will be okay; but we can not make it long term without protection.
please help us to make the proof on proxied DNS services also the DNSSEC services as cloudflare domain protectors.
thanks in advance.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the HTTPS proof failure from the linked Keybase profile while the domain remains proxied and DNSSEC-enabled. Trace the existing website-proof handling and define the work as complete when a proof succeeds without disabling the domain's protection services.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100