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

remove blogspot.mr and blogspot.td #2100

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

wdhdev
Copy link
Contributor

@wdhdev wdhdev commented Aug 11, 2024

blogspot.mr

I'm not sure where this was originally added in, possibly added pre-GitHub.

Pretty simple reason for removal; the domain name is expired.

When attempting to lookup the domain via WHOIS, the server returns:

$ whois blogspot.mr
Server can't process your request at the moment.

And to clarify, I don't believe this is a server issue as looking up, for example, nic.mr works perfectly fine and returns the WHOIS data.

When attempting to lookup NS records the server returns NXDOMAIN.

blogspot.td

Basically the same issue as blogspot.mr, I don't believe it is registered anymore, however I cannot completely confirm this as attempting a WHOIS lookup does not work.

When attempting to dig the NS records, SERVFAIL is returned. I suspect the TLD operator is having issues, however it does seem to be a very small, mostly unused TLD, as according to Wikipedia there are only 876 domains registered as of July 22, 2017.

@wdhdev wdhdev changed the title remove blogspot.mr remove blogspot.mr and blogspot.td Aug 11, 2024
@groundcat
Copy link
Contributor

groundcat commented Aug 12, 2024

If the domain has expired, then I guess it's safe to remove it, but I'm a little unsure since the WHOIS data for .mr and .td is unavailable. Personally I believe a more efficient approach might be to ask Google for confirmation on whether they need this entire block of ccTLD Blogspot domains, rather than having volunteers check each entry individually—it's a huge block. I selected some samples and ran a quick check

and it appears that all the sampled ccTLD domains are redirecting (301/302) to blogname.blogspot.com domains, so it's likely they have decommissioned the use of ccTLD Blogspot domains altogether, with all redirects going to the main blogspot.com domain.

I think this is when a Google employee last responded regarding the Blogspot domains.

@wdhdev
Copy link
Contributor Author

wdhdev commented Aug 12, 2024

Yeah, I think it's possible they've decommissioned these ccTLDs. @simon-friedberger @dnsguru What do you guys think?

@simon-friedberger
Copy link
Contributor

I asked about this here: #1947 (comment)
@svipul Is there somebody whom you could ping?

@wdhdev
Copy link
Contributor Author

wdhdev commented Aug 24, 2024

Some other reasons worth mentioning for removal:

  • No websites are returned when searching site:blogspot.mr or site:blogspot.td on Google, suggesting the domain is not used at all.
  • No SSLs were found for blogspot.mr: https://crt.sh/?q=blogspot.mr
  • SSLs were found for blogspot.td, however they are all expired and none have been created since 2021-09-24: https://crt.sh/?q=blogspot.td

I think it would be safe to remove these in addition with other reasons mentioned in this PR.

@wdhdev
Copy link
Contributor Author

wdhdev commented Sep 6, 2024

@simon-friedberger I believe these are safe to remove as these 2 domains have expired, and as for the other Blogspot domains listed in the section it might be worth opening an issue and possibly emailing the email address Google has listed for contact.

@groundcat
Copy link
Contributor

I tried to email Public Suffix Editors <public-suffix-editors@google.com> but it was bounced:

We're writing to let you know that the group you tried to contact (public-suffix-editors) may not exist, or you may not have permission to post messages to the group. A few more details on why you weren't able to post:

* You might have spelled or formatted the group name incorrectly.
* The owner of the group may have removed this group.
* You may need to join the group before receiving permission to post.
* This group may not be open to posting.

If you have questions related to this or any other Google Group, visit the Help Center at https://support.google.com/a/google.com/bin/topic.py?topic=25838.

Thanks,

google.com admins

@simon-friedberger
Copy link
Contributor

@krgovind Do you have a suggestion who to reach out to?

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

Successfully merging this pull request may close these issues.

3 participants