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 n4t.co, now-dns.top, 001www.com #2178

Closed
wants to merge 2 commits into from

Conversation

groundcat
Copy link
Contributor

@groundcat groundcat commented Sep 18, 2024

This PR is to remove n4t.co and now-dns.top to rollback commit #257

n4t.co Evidence:

  • Attempts to contact the admin via email (listed at https://now-dns.com > Contact) have been unsuccessful for over 3 months.
  • The Google search and Bing search show 1 results for the domain n4t.co but the subdomain is dead.
  • Certificate Transparency reveals no active SSL certificates in use.
  • Running dig +short TXT _psl.n4t.co no longer returns the required record value. (EDIT: TXT record preservation was not required at the time.)
  • No subdomains were found by third-party tools [1] [2] (no resolvable subdomains).

now-dns.top Evidence:

  • Attempts to contact the admin via email (listed at https://now-dns.com > Contact) have been unsuccessful for over 3 months.
  • It has been in serverHold status for a long time. Domain Status: serverHold https://icann.org/epp#serverHold
  • The Google search and Bing search show no results for the domain now-dns.top.
  • Certificate Transparency reveals no active SSL certificates in use.
  • Running dig +short TXT _psl.now-dns.top no longer returns the required record value. (EDIT: TXT record preservation was not required at the time.)
  • No subdomains were found by third-party tools [1] [2] (no resolvable subdomains).

001www.com Evidence:

  • Attempts to contact the admin via email (listed at https://now-dns.com > Contact) have been unsuccessful for over 3 months.
  • It has been in clientHold status for a long time. Domain Status: clientHold https://icann.org/epp#clientHold
  • The Google search and Bing search show some results for the domain 001www.com but none of them are accessible websites.
  • Certificate Transparency reveals no active SSL certificates in use.
  • Running dig +short TXT _psl.001www.com no longer returns the required record value. (EDIT: TXT record preservation was not required at the time.)
  • No subdomains were found by third-party tools [1] [2] (no resolvable subdomains).

Additional Information:

  • The service at https://now-dns.com is still running, but the status of their operation is uncertain. It is likely a dead/zombie project and there has been a lack of moderation, leading to abuse of existing domains that are alive.
  • Multiple domains were in clienthold or serverhold status set by the registrar or TLD registry.
  • The admin has been unresponsive for several months despite multiple attempts to reach them via email. An example is chore: remove 3 domains from Now-DNS section #2113.

@groundcat groundcat changed the title Remove n4t.co and now-dns.top Remove n4t.co, now-dns.top, 001www.com Sep 18, 2024
@danderson
Copy link
Contributor

Other evidence of defunct service: https://now-dns.com/?p=services links to their related services:

  • 301.li, a URL shortener. Domain still registered, but no DNS records and therefore no service.
  • ihatespam.net, a disposable email service. Seems to point at an unrelated server because all it serves is a TLS verification error.
  • Last evidence of activity on now-dns.com is 2017, the blog and copyright footer stopped at that time. Expanding even further, the last evidence of any activity at all I can find is the registration of ihatespam.net in 2020. Since then, afaict all events I can find are just registrar automation making small adjustments to whois occasionally.
  • There has been no activity on the github account since the PSL entries were added.

Note, for n4t.co: I'm not sure a _psl record was required in 2018, when the entry was added. So, it's possible its absence is expected. However, the domain is still defunct because DNS is hard down (timeouts), and has been for >1 month.

@wdhdev
Copy link
Contributor

wdhdev commented Sep 18, 2024

It seems a lot of their domains are lapsing as noted in my PR removing 3 entries from this same section: #2113 (comment)

@groundcat
Copy link
Contributor Author

groundcat commented Sep 19, 2024

Email response received from Now-DNS Free DDNS <[email protected]> (the address I discovered from the patch info of the requestor's commit):

thank you for your email, yes the service is running still, but needs some attention. We are looking to tidy things up over the next few months

@simon-friedberger
Copy link
Contributor

Should we close this then? @groundcat

@groundcat
Copy link
Contributor Author

groundcat commented Oct 1, 2024

I am closing this PR, assuming the initial submitter is working on changes and will submit a PR directly.

Over the past 2 weeks, it seems that Now-DNS has removed some domains from their DDNS service and updated the website with new domains (listed below), but they have not yet submitted a PR here to update the PSL to align with their service domains.

@Now-DNS Could you please submit a new PR here once you have completed the cleanups?

.2mydns.net
.ddns.cam
.dnsapi.info
.dnsdyn.net
.dnsget.org
.dnslive.net
.dnsup.net
.dtdns.org
.dynip.org
.dynserv.org
.forumz.info
.freeddns.uk
.freeddns.us
.hicam.net
.myddns.biz
.myiphost.com
.mypi.co
.now-dns.net
.now-dns.org
.now-dns.top
.nowddns.com
.ntdll.top
.ownip.net
.soundcast.me
.tcp4.me
.tftpd.net
.vpndns.net
.wifizone.org
.x443.pw

I have written an email to them, inviting them to directly submit a new PR here to update their block.

@groundcat
Copy link
Contributor Author

Hello @Now-DNS,

We noticed that 001www.com and now-dns.top have been in clientHold and serverHold status respectively for an extended period. Additionally, we observed that 001www.com does not appear to be listed on your website (https://now-dns.com/), suggesting it may no longer be in use.

Would you be agreeable to having these two domains removed from the Public Suffix List? If you resolve the hold status in the future, you are welcome to submit them for inclusion again.

Please let us know your thoughts on this matter. If we do not hear back from you within 30 days, we will proceed to remove these domains from the Public Suffix List.

CC @wdhdev

@wdhdev
Copy link
Contributor

wdhdev commented Dec 11, 2024

The PR regarding removal is #2324.

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.

4 participants