Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for private/reserved/custom TLDs #154

Open
carton-of-mice opened this issue Nov 10, 2023 · 0 comments
Open

Support for private/reserved/custom TLDs #154

carton-of-mice opened this issue Nov 10, 2023 · 0 comments

Comments

@carton-of-mice
Copy link

carton-of-mice commented Nov 10, 2023

URLExtract pulls in the list of TLDs in the root zone, but there are a number of reserved, test or otherwise special use TLDs that are still valid in URLs in at least some contexts.
I'm looking at rfc6761, rfc6762 and rfc7686, for which I think there should be an extract_private property, but a more generic solution like allowing callers to define their own supplementary(or replacement) set of custom TLDs would be sufficient as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant