0

Block Web3 TLDs

I want to block Web3 TLDs. When I try to add to the block list it tells me to use the TLD blocker, but the TLD blocker is missing some TLDs, like .eth or .crypto with no way to add my own TLDs to the list.

4 replies

null
    • Calvin_Hobbes
    • 1 yr ago
    • Reported - view

    Not sure, but check under the settings tab.  Web3 (beta) when set to off should block those. I haven’t tried it myself 

      • Mike.13
      • 1 yr ago
      • Reported - view

      Thanks, but I guess I'd just feel more comfortable in it being blocked using explicit blocks than simply having that turned off.

      • Calvin_Hobbes
      • 1 yr ago
      • Reported - view

      Mike heck, i can’t figure out how to purposefully resolve a web3 address, never mind blocking one 🤷‍♂️

      do you have an example of a host in one of those TLDs that can be resolved the old fashioned way?

      • Calvin_Hobbes
      • 1 yr ago
      • Reported - view

      I just noticed the setting for Web3 gives an example of "vitalik.eth"     I enabled Web3 and used nslookup to query vitalik.eth.   Received the following results: 

      > vitalik.eth
Server:        127.0.0.1
Address:    127.0.0.1#53  Name:    vitalik.eth
Address: 104.17.64.14
Name:    vitalik.eth
Address: 104.17.96.13

      Then I disabled Web3 and received the following: 

      > vitalik.eth
Server:        127.0.0.1
Address:    127.0.0.1#53  ** server can't find vitalik.eth: NXDOMAIN

      So, it seems like disabling Web3 in the settings  works for this particular example.

Login to reply

Content aside

  • 1 yr agoLast active
  • 4Replies
  • 82Views
  • 2 Following