Title: Cock.li domain cannot be added for email verification, impacting GPG key management

[8e8m]

Select Topic Area

Product Feedback

GitHub Feature Area

Enterprise

Body

I've encountered an issue where the cock.li domain cannot be added as a verified email address, even when using existing external verification methods. This creates a significant problem for users who rely on multiple email addresses for their GPG keys.

Impact:

GPG keys that have UIDs (User IDs) associated with cock.li email addresses cannot be properly verified or managed through platforms that require email verification

Users are unable to prove ownership of these email addresses through standard verification flows

This limitation affects key signing and the web of trust, as cock.li email addresses effectively become second-class citizens in the GPG ecosystem

Suggested Discussion Points:

Is there a technical reason why cock.li is being blocked from verification?

Could there be alternative verification methods for domains that are problematic for standard flows?

Should we consider this a bug or a deliberate restriction?

I'd like to open this for discussion to understand if this is an intentional limitation or something that could potentially be addressed to support users who have legitimate needs for multiple email addresses on their GPG keys.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐