Remove py.sdk CNAME — dangling and exposed to takeover#21
Closed
Remove py.sdk CNAME — dangling and exposed to takeover#21
Conversation
🏠 Remote-Dev: homespace
Contributor
Author
|
Closing — |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
py.sdkCNAME is currently dangling: it resolves to GitHub Pages, serves the GitHub 404 page, andmodelcontextprotocol/python-sdkhascname: nullin its Pages config — i.e. no org repo claims it. This is the identical postureruby.sdk(#18) andgo.sdk(#20) were in when hijacked.Removing the CNAME until proper Pages domain verification is in place.
Note on verification: the
_gh-modelcontextprotocol-o.*TXT records added in #16/#19 are GitHub org-profile domain verification (the "Verified" badge), not GitHub Pages domain verification. Pages takeover protection requires a separate_github-pages-challenge-modelcontextprotocol.*TXT generated from Org Settings → Pages → Add a domain, which currently exists only forblog. A follow-up PR will add the correct records once those codes are generated.